Tool flow management method, device, equipment, medium and program product

Abstract

The application is suitable for the technical field of flow control, and provides a tool flow control method, device, equipment, medium and program product. Tool flow requirements of each line body are acquired, the tool flow requirements are dynamically grouped, a plurality of aggregated groups are obtained, time counting of an aggregated group to which a first tool flow requirement is added is started, and quantity counting of tool flow requirement quantity in the aggregated group is set. It is judged in real time whether the quantity counting reaches a preset quantity threshold or whether the time counting reaches a preset time threshold. If any condition is met, an automated guided vehicle transportation task is generated for the aggregated group, and the quantity counting and the time counting of the aggregated group are reset. The problem that it is difficult to achieve a good balance between transportation efficiency and demand response timeliness is solved.

Description

Technical Field

[0001] This invention relates to the field of flow control technology, and in particular to a tool flow control method, device, equipment, medium, and program product. Background Technology

[0002] As the manufacturing industry evolves towards greater flexibility and automation, automated machining lines composed of multiple CNC machine tools have been widely used in the mass production of automotive parts, precision molds, 3C electronics, and other products. To ensure continuous processing of multiple lines and processes, a central tool magazine is usually configured to centrally store and manage tools. The delivery and retrieval of tools are carried out between the central tool magazine and each line through mobile transport equipment such as automated guided vehicles.

[0003] In existing tool scheduling methods, common approaches include on-demand immediate response and fixed-cycle inspection. In the first approach, whenever a processing line generates a tool demand, the system immediately generates an independent transport task and assigns an automated guided vehicle (AGV) to perform point-to-point delivery. While this approach offers rapid response, it is prone to fragmentation of transport tasks in scenarios with concurrent requests from multiple lines. AGVs frequently travel back and forth, resulting in low loading rates. This not only increases the energy consumption and mechanical wear of transport equipment but may also lead to congestion in logistics channels, hindering overall scheduling efficiency. In the second approach, the system processes tool demands from the production line in batches at fixed time intervals or shifts. While this approach can increase the loading capacity of a single transport, its fixed triggering cycle cannot adapt to real-time changes in production demand. During periods of high demand, excessively long tool waiting times may cause line downtime due to material shortages; conversely, during periods of low demand, forced order consolidation may cause unnecessary delays. Summary of the Invention

[0004] This invention provides a tool process control method, device, equipment, medium, and program product to solve the problem of achieving a good balance between transportation efficiency and timely response to demand.

[0005] In a first aspect, embodiments of this application provide a tool flow control method, including: Obtain the tool flow requirements for each production line; wherein, the tool flow requirements include at least the production line identifier and the tool holder type; The tool flow requirements are dynamically grouped to obtain several aggregate groups; each aggregate group corresponds to a line body identifier and a tool holder type. Set a timer for the start time of the aggregation group added to the first tool transfer request, and set a count to record the number of tool transfer requests within the aggregation group; In real time, it is determined whether the quantity count has reached a preset quantity threshold or whether the time count has reached a preset time threshold. If either condition is met, an automated guided vehicle transportation task is generated for the aggregation group, and the quantity count and time count of the aggregation group are reset.

[0006] Secondly, embodiments of this application provide a tool flow control device, comprising: The acquisition module is used to acquire the tool flow requirements of each production line; wherein, the tool flow requirements include at least the production line identifier and the tool holder type; The grouping module is used to dynamically group the tool flow requirements to obtain several aggregate groups; each aggregate group corresponds to a line body identifier and a tool holder type. The counting module is used to time the start time of the aggregation group added to the first tool flow request, and to set the count of the number of tool flow requests in the aggregation group. The task module is used to determine in real time whether the quantity count has reached a preset quantity threshold or the time count has reached a preset time threshold. If either condition is met, an automated guided vehicle transportation task is generated for the aggregation group, and the quantity count and time count of the aggregation group are reset.

[0007] Thirdly, embodiments of this application provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described tool flow control method.

[0008] Fourthly, embodiments of this application provide a readable storage medium storing a computer program that, when executed by a processor, implements the steps of the aforementioned tool flow control method.

[0009] Fifthly, embodiments of this application provide a computer program product, which includes a computer program that, when executed by a processor, can implement the steps of the above-described tool flow control method.

[0010] In one solution provided by the aforementioned tool flow control methods, devices, equipment, media, and program products, tool flow requirements are dynamically grouped based on line identification and tool holder type. A dual-condition triggering mechanism of quantity counting and time timing is employed. An automated guided vehicle (AGV) transport task is only generated when the accumulated demand within the aggregation group reaches a preset quantity or the waiting time reaches a preset time. This method effectively overcomes the problems of fragmented transport tasks and high AGV empty load rates caused by the immediate response mode, significantly improving the loading rate of a single transport, reducing transport trips and energy consumption, and lowering logistics costs. Simultaneously, the time threshold ensures timely response under low demand density, preventing line downtime due to excessive aggregation. This achieves an adaptive balance between transport efficiency and demand timeliness. After a task is generated, the counting and timing of the aggregation group are reset and the next aggregation round begins, enabling the scheduling system to automatically adjust the dispatch rhythm according to real-time demand density, enhancing the flexibility and operational stability of production line logistics. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a schematic diagram of a tool flow control method according to an embodiment of the present invention; Figure 2 yes Figure 1 A schematic diagram of the implementation process of step S20; Figure 3 This is a schematic diagram of a tool flow control device according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0013] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or collections thereof. It should also be understood that, as used in this specification and the appended claims, the term "and / or" refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0015] Furthermore, in the description of this invention and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0016] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of the invention include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0017] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0018] To illustrate the technical solution of the present invention, specific embodiments are described below.

[0019] In one embodiment, such as Figure 1 As shown, a tool flow control method is provided, including the following steps: S10: Obtain the tool flow requirements for each production line; wherein, the tool flow requirements include at least the production line identifier and the tool holder type; S20: Dynamically group the tool flow requirements to obtain several aggregate groups; each aggregate group corresponds to a line body identifier and tool holder type. S30: Sets the start timer for the aggregation group added to the first tool transfer request, and sets a count to record the number of tool transfer requests within the aggregation group; S40: In real time, determine whether the quantity count has reached a preset quantity threshold or whether the time count has reached a preset time threshold. If either condition is met, generate an automated guided vehicle transportation task for the aggregation group and reset the quantity count and time count of the aggregation group.

[0020] In this embodiment, in an actual automated machining workshop, there are multiple independently operating machining lines (such as milling lines, turning lines, etc.). Each line will continuously generate tool turnover requirements based on its production plan, tool life warning, or manual instructions. These requirements are sent to the central tool magazine management system in real time through the manufacturing execution system or line controller.

[0021] The tooling flow requirements include at least two key attributes: line identifier and tool holder type. The line identifier uniquely identifies which machining line requires tooling services, serving as the basis for subsequent targeted tool delivery and serialized task scheduling. The tool holder type indicates the interface specification of the tool involved in this requirement, such as BT40 or HSK63. Since tools of different tool holder types are stored in separate areas in the central tool magazine, and an automated guided vehicle (AGV) can typically only accommodate tool holders with a single interface in a single transport, this information must be used as the basic dimension of the requirement.

[0022] It is understandable that this requirement may also imply directional attributes, such as tool preparation requirements (from the central tool magazine to the production line) or tool return requirements (from the production line back to the magazine). These two types of requirements will be processed independently, ensuring that all tool service requests from the production line are collected in real time and completely, providing a data foundation for subsequent intelligent aggregation and scheduling.

[0023] In the traditional model, tool transportation tasks are often carried out in a round trip or by scheduled inspections, which can easily lead to high empty load rates and long waiting times for transport vehicles. To solve this problem, this invention introduces a dynamic aggregation mechanism, which organizes all discrete demands that arrive in real time into several aggregation groups online based on the two dimensions of demand line identification and tool holder type.

[0024] In practice, this dynamic grouping process can be further expanded to mean that when a new requirement arrives, the system searches the list of existing aggregation groups. Each aggregation group is defined by a unique combination of line body identifier and tool holder type. If an aggregation group already exists whose line body identifier and tool holder type are completely consistent with the new requirement, it means that the requirement can be merged with existing requirements of the same type. At this time, the system directly classifies this requirement into the aggregation group and increments the number of requirements recorded in the aggregation group, i.e., the quantity count, by 1.

[0025] If no matching aggregation group exists, it indicates that this is a completely new requirement category. The system immediately creates a new aggregation group, using the line body identifier and tool holder type of the requirement as identifiers, initializes the quantity count of this aggregation group to 1, and starts its timer.

[0026] Through this real-time matching and grouping, discrete tool flow needs are systematically aggregated into their respective groups, creating conditions for batch transportation. This is similar to creating a virtual waiting queue for each pair of destination-interface specifications, minimizing the number of transportation trips.

[0027] When an aggregation group is created due to the first demand, a timer immediately starts running, recording the continuous waiting time of the group since its creation. This timer is continuous and does not reset with the addition of subsequent demands, ensuring that the aggregation group does not wait indefinitely and guaranteeing the timeliness of tool service. A counter is used to accumulate the number of merged demands within the aggregation group. The counter increments as new demands are matched, serving as a direct indicator of the transport batch size. These two variables constitute the dual basis for triggering a transport task. It should be noted that for any aggregation group, these two metrics are parallel and updated in real time, jointly representing the urgency and full capacity of the group's demands.

[0028] The system continuously monitors each active aggregation group and executes a real-time judgment logic. Condition 1: The quantity count reaches a preset quantity threshold (e.g., the quantity threshold is set to 5). When the cumulative number of demands gathered in an aggregation group reaches 5, it means that a sufficient batch has been accumulated, and it is worthwhile to dispatch an automated guided vehicle for centralized transportation. Condition 2: The time count reaches a preset time threshold (e.g., the time threshold is set to 10 minutes). When the waiting time for the first demand in an aggregation group has reached 10 minutes, even if the number of demands in the group has not reached the preset quantity threshold, it indicates that the demand cannot be delayed any longer and must be responded to immediately to ensure the production cycle of the line.

[0029] Once any of the above conditions are met, the scheduling module immediately generates an automated guided vehicle (AGV) transport task for the aggregation group. This task will transport all the physical tools corresponding to the tool flow requirements within the aggregation group from the central tool magazine to the target production line in one go. At the same time as the task is generated, the system resets the quantity count of the aggregation group to zero and the timer to zero. This reset does not delete the aggregation group, but rather returns it to its initial empty state, so that it can start accepting new requirements of the same type and start the next aggregation cycle.

[0030] This mechanism cleverly balances the contradiction between transportation efficiency and timely response. The quantity threshold ensures the loading rate of transportation tasks, reducing the empty runs and frequency of automated guided vehicles (AGVs); the time threshold prevents infinite waiting caused by sparse demand, providing a guarantee for response to low-density demands. The combination of the two enables adaptive, economical, and timely scheduling of tool flow.

[0031] In one embodiment, the automated guided vehicle (AGV) transport task is constrained to transport only tools of the same tool holder type per task. When multiple aggregate groups with the same line identifier trigger tasks one after another, the corresponding AGV transport tasks are added to the task queue according to the order of triggering time, and the next AGV transport task is dispatched after the previous AGV transport task is completed.

[0032] In this embodiment, the present invention explicitly restricts the automated guided vehicle (AGV) transportation task to transport only tools of the same handle type per task. This restriction is not merely due to the inherent homogeneity of handle types within the aggregate group, but rather a mandatory safety and compatibility guarantee mechanism.

[0033] Specifically, the technical meaning of this constraint is that regardless of which aggregation group triggers the transportation task, the tool holder interface specifications of all tools in the physical tool loading list corresponding to the task must be strictly consistent, such as all being BT40 or all being HSK-A63. In the automated picking and loading process of the central tool magazine, the scheduling system will verify the tool holder type of the tools to be loaded according to this constraint to ensure that there is no mixed loading.

[0034] The main purpose of imposing this constraint is to eliminate the risk of loading mismatch. Automated guided vehicles (AGVs) are usually equipped with tool trays or clamping mechanisms adapted to specific toolholder interfaces. Mixing different types of toolholders can easily lead to tools not being securely fixed during transportation, causing tools to slip, collide, or the interface to be damaged, seriously affecting transportation safety and tool accuracy. It also ensures the accurate gripping of automated tool changers on the production line side. Each processing line is usually equipped with an automated tool changer corresponding to its own spindle interface. If multiple types of toolholders are received at once, it will not only increase the risk of identification and incorrect gripping by the robot, but may also prevent the tool changer from completing the operation due to interface incompatibility, forcing the production line to stop. Through this constraint, any set of tools delivered to the production line has the same interface specification, which greatly simplifies the automated operation on the production line side and improves the smoothness of the process.

[0035] When multiple aggregation groups exist for the same line identifier (i.e., the same machining line corresponds to tool flow requirements of different tool holder types), these aggregation groups may trigger the generation of transportation tasks sequentially based on their respective quantity counts and time timings. In this case, the present invention introduces a task queue and serial dispatch mechanism based on the task triggering time order. The specific implementation of this mechanism is as follows: the system maintains a first-in-first-out task queue for the line identifier. When a new automated guided vehicle (AGV) transportation task is generated because the triggering conditions are met, regardless of its tool holder type, the system records the task. The task is precisely triggered at the specified time and pushed to the end of the task queue identified by the line according to the order of trigger time. Then, the dispatch logic strictly follows the serialization principle, that is: only the first task in the queue is checked. If the task has not yet been dispatched, or is being executed by an automated guided vehicle after dispatch, the system remains in a listening state. Only when a feedback signal indicating that the task has been completed is received (e.g., the automated guided vehicle has returned, the tool has been unloaded to the line and confirmed to have received it), will the dispatch logic dequeue the next task in the queue and send a dispatch instruction to the scheduling system to assign an available automated guided vehicle to execute the new transportation task.

[0036] In one embodiment, such as Figure 2 As shown, step S20 involves dynamically grouping the tool flow requirements to obtain several aggregate groups, specifically including the following steps: S21: Based on the existing aggregation group, perform line identification and tool holder type matching processing on the tool flow requirements; S22: If the matching result shows that it exists, the tool flow requirement is classified into the matching aggregation group, and the number of aggregation groups is counted. S23: If the matching result shows that it does not exist, a new aggregation group is constructed according to the tool flow requirements, and the quantity counting and time timing of the aggregation group are started.

[0037] In this embodiment, when a new tool transfer request is obtained, the system does not immediately generate a transport task for it. Instead, it first puts it into the grouping logic for matching, and performs a search and matching operation on all currently active aggregation groups. The matching process uses the line identifier and tool holder type carried in the request as a composite matching key. The operation is essentially to determine whether there is already an aggregation group in the system whose target is the line and whose tool holder specifications are completely consistent with the request.

[0038] This matching process is strict and precise. For example, if a requirement is line body A and BT40 tool holder, then the matching result will only be displayed if there is a group in the existing aggregation group whose line body identifier is also line body A and the tool holder type is also BT40. Aggregation groups of any other line body (even if they are also BT40) or other tool holder types (even if they are also line body A) will not constitute a match.

[0039] If a match is found, it means that the destination and tool holder specifications of the request are exactly the same as some other pending requests, and the conditions for merging and transporting are met. In this case, the tool transfer request is assigned to the successfully matched aggregation group. This classification can be logical, that is, the ID of the request is recorded in the request list of the aggregation group so that all the aggregated pending tool information can be retrieved when a transport task is generated later.

[0040] The aggregation group already maintains a counter representing the quantity of demand within the group. When a new demand is added, the system increments the quantity count of the aggregation group by 1 (or other preset increments). Through this lookup-merge-accumulation mechanism, discretely arriving tool demands are continuously aggregated into the same container, and the size of the aggregation group is constantly increasing, getting closer and closer to the quantity threshold for batch transportation. This step significantly improves the adaptability to demand fluctuations: during peak processing periods with dense requests, the count rises rapidly, quickly accumulating a sufficient batch; while during periods of sparse demand, although the demand is small, it can still be properly included in the corresponding group and protected by time-based timing.

[0041] If the matching result is non-existent, it means that there are no waiting similar requirements in the system for this line body—this tool holder type. This is the starting point of a brand new requirement flow. At this time, the creation process of an aggregation group is initiated: First, a new aggregation group is constructed. The system uses the line body identifier and tool holder type of the current requirement as the unique identifier of the aggregation group. A new empty aggregation group entity is created in the group pool. The quantity count and timer of the aggregation group are started. The quantity count is initialized to 1, indicating that the group has included the first requirement. At the same time, the timer is started for the aggregation group added to the first requirement according to the rules. The timer starts counting continuously from zero and is used to record the waiting time of the aggregation group since the arrival of the first requirement.

[0042] This step ensures that any new demand type can immediately obtain its own dedicated waiting queue and begin to be measured for timeliness. It enables the grouping logic to be fully adaptive: instead of pre-setting groups for every possible combination (line body, tool holder type), it dynamically and on demand creates groups according to the natural arrival of demand, while consuming very few resources. The corresponding timing and management overhead only occurs when the demand actually occurs. When an aggregate group is finally triggered for transport and reset, its structure may be left empty to accommodate subsequent demand reactivation, or it may be destroyed after the idle timeout according to the strategy to save resources. These are all flexible extensions of dynamic grouping.

[0043] In one embodiment, the tool flow requirements also include tool preparation requirements and tool retraction requirements, which are executed independently of the dynamic grouping and subsequent scheduling logic.

[0044] To address these two needs, the system executes the dynamic grouping and subsequent scheduling logic independently. Specifically, this means that the entire scheduling mechanism described in steps S20 to S40, such as dynamic grouping and dual-condition triggering task generation, is instantiated within the system as two parallel, non-interfering logical links. One link is dedicated to handling all tool preparation needs, and the other link is dedicated to handling all tool return needs.

[0045] This design avoids mutual waiting and interference between forward and reverse logistics. Tool preparation needs serve production and are highly time-sensitive; while tool return needs typically do not have the same level of urgency, allowing for longer aggregation waiting times to improve the full load rate of return transport. If both are mixed in the same aggregation group, urgently needed tool preparation may be hampered by less urgent tool return, or returned tools may return empty due to frequent triggering, resulting in reduced efficiency for both. Independent scheduling allows setting different preset quantity thresholds and preset time thresholds for tool preparation and return (e.g., a tool preparation threshold of 3 and a time threshold of 8 minutes; a tool return threshold of 10 and a time threshold of 30 minutes), enabling scheduling parameters to precisely match the timeliness and economic requirements of each business.

[0046] It simplifies the management of automated guided vehicle (AGV) transportation tasks. Since the physical tool flow of tool preparation and tool return is opposite, if they are mixed in the same task, the AGV will have to handle loading and unloading at the same time in one transportation, making path planning complicated and prone to errors. Independent scheduling makes the direction of each transportation task singular and clear, either a pure delivery task or a pure recovery task, which greatly improves the smoothness and accuracy of the operation.

[0047] In one embodiment, tool detection is performed on the recovered tool corresponding to the tool retraction requirement, and a grading process is performed based on the detection results. The specific steps include: S51: Monitor the flank wear condition of the recovered tool to obtain the flank wear amount of the recovered tool; S52: When the wear of the back face is less than 0.1mm, and at the same time the cutting edge is free of chipping, the dimensional deviation is within the preset range, and the predicted remaining life is greater than the preset ratio, the tool is determined to be in life adjustment state, and its remaining life parameters are corrected before returning to the production line for continued use. S53: When the wear of the back face is between 0.1mm and 0.3mm, and the edge chipping is repairable and the cumulative number of regrindings is less than the maximum allowable value, the tool is determined to be in a grinding state, a grinding task is generated and transferred to the regrinding station; S54: When the wear of the back face is greater than or equal to 0.3mm, or when any one of the following conditions is met: the chipping of the cutting edge exceeds the limit, the cumulative number of regrindings reaches the maximum allowable value, or the substrate is damaged, the tool is determined to be scrapped, marked as scrapped, and transferred to the scrap storage area.

[0048] For cutting tools that are returned to the warehouse due to the need for tool removal, this invention does not simply put them directly into the tool magazine or discard them. Instead, it establishes a graded processing procedure based on wear detection to maximize the utilization value of the cutting tools.

[0049] Once the recovered cutting tool arrives at the inspection area of ​​the central tool magazine, wear condition monitoring is performed first. This invention preferably employs a non-contact machine vision inspection method, using a high-resolution industrial camera to capture images of the tool's flank face. Image processing algorithms are then used to extract the geometric features of the wear band, thereby calculating the precise flank face wear amount (usually represented by the VB value). This wear amount is the primary quantitative basis for subsequent grading. Simultaneously, the inspection system can also perform auxiliary inspections such as cutting edge integrity checks and critical dimension measurements, providing data support for subsequent comprehensive judgment.

[0050] When the obtained detection data meets all of the following conditions, the tool is determined to be in the life adjustment state: the flank wear is less than 0.1mm; there is no chipping on the cutting edge; the dimensional deviation is within the preset range; the predicted remaining life is greater than the preset ratio. This set of conditions indicates that the tool has only very slight wear, is in excellent physical condition, and still has reliable cutting ability. At this time, the system will not perform physical re-grinding on the tool, but will perform software-level correction of the remaining life parameter. Since the actual wear is less than expected, the system updates the remaining cutting life parameter of the tool to a more accurate value re-estimated based on the actual wear data, and then directly returns the tool to the production line for continued use. This processing method avoids unnecessary grinding, maximizes the effective use time after a single sharpening, and reduces tool consumption and grinding costs.

[0051] When the obtained detection data meets all of the following conditions, the tool is determined to be in a sharpening state: the flank wear is between 0.1mm and 0.3mm; the chipping of the cutting edge is repairable; the cumulative number of regrinding times is less than the maximum allowable value. This set of conditions indicates that the tool has undergone significant wear, the sharpness of the cutting edge has decreased, but the degree of wear is still within the repairable range, and the tool body structure can still withstand re-grinding. After the system makes the determination, it immediately generates a sharpening task, adds the tool to the grinding queue, and dispatches an automatic guided vehicle or internal transfer mechanism to transfer it to the regrinding station, where it is re-grinded by an automated grinding machine or manually to restore its cutting performance. After regrinding is completed, the cumulative number of regrinding times of the tool is incremented by 1, the wear parameters are reset, and it can be put back into the warehouse for standby.

[0052] The scrapping determination adopts an OR logic, meaning that a tool is deemed scrapped if it meets any of the following conditions: flank wear greater than or equal to 0.3mm; edge chipping exceeding the limit; cumulative regrinding count reaching the maximum allowable value; or damage to the tool body. This set of conditions covers various situations where the tool's physical lifespan has ended: excessive wear rendering it unusable for regrinding, edge damage beyond repair, having undergone all allowed regrinding counts, or structural damage such as cracks in the tool body itself. Once determined to be scrapped, the system marks it as scrapped and schedules its transfer to the scrap collection area for unified recycling and processing, preventing it from re-entering the machining cycle to ensure machining quality and safety.

[0053] In one embodiment, a digital profile is created for each uniquely identified tool, recording its wear data, actual cutting time, processed material, and working condition parameters at each life adjustment. A machine learning algorithm is used to build a wear trend prediction model for the tool based on the digital profile to predict the effective cutting life that can be achieved after the next regrinding. When the predicted effective cutting life after the next regrinding is lower than a preset economic threshold, even if the cumulative number of regrindings has not reached the default maximum allowable value, the current maximum allowable value of the tool is dynamically set to the current number of regrindings, and it is directly determined to enter the scrap state.

[0054] This method first requires assigning an unalterable and unique identifier to each physical tool entering the control system, such as a laser-etched QR code or RFID chip. Around this unique identifier, the system builds a digital profile bound to it in a central database. This digital profile is not a static ledger, but a dynamic data set that grows continuously as the tool is used. Whenever the tool experiences a life adjustment event, the system will append the multi-dimensional data recorded in that event to its digital profile.

[0055] These data specifically include: wear data, such as the amount of flank wear and the wear morphology parameters of the rake face obtained in this test; actual cutting time, the cumulative time the tool has been in actual cutting processing from the last life adjustment or regrinding to this recycling; the material being processed, such as the workpiece material grade, hardness, and other information; and operating parameters, such as the main cutting speed, feed rate, depth of cut, and other process parameters during this service period.

[0056] Once sufficient historical data points have been accumulated for a particular cutting tool in the digital archive, the system will initiate the training process of a machine learning algorithm to establish a wear trend prediction model specific to that tool. In this embodiment, a regression-type machine learning algorithm, such as support vector regression, gradient boosting tree, or deep learning time series prediction network, is preferred. The input feature vector of the model consists of the actual cutting time, the material being processed, and the working parameters recorded in the aforementioned archive. The output target is the amount of flank wear or the reduction ratio of the effective cutting life after this use.

[0057] The core capability of the model lies in learning the implicit mapping relationship between wear rate and usage intensity under a specific tool-material-working condition combination. After training, the predictive model can be used to infer: if the tool is put into a similar machining task again after being regrinded, what is the expected effective cutting life? Here, the effective cutting life after the next regrinding refers to the predicted time or number of workpieces that the regrinded tool can stably process from the start of cutting with a brand new cutting edge until it reaches the wear threshold that needs to be recycled again (such as 0.3mm of flank wear).

[0058] To incorporate economic considerations into scrapping decisions, this invention establishes a preset economic threshold. This threshold is defined as the minimum effective cutting life that a regrinding tool must provide after regrinding, considering the combined cost of completing a regrinding operation (including grinding consumables, labor time, equipment depreciation, etc.) and the remaining physical value of the tool itself. For example, the economic threshold can be set as the cutting time for completing 10 standard workpieces. If a tool cannot even guarantee this minimum output after regrinding, then performing regrinding is not economically worthwhile.

[0059] Before the tool reaches the sharpening threshold each time, or before generating a sharpening task for it, the system calls the tool's wear trend prediction model, inputs the expected subsequent machining parameters, calculates the predicted effective cutting life that can be achieved after the next regrinding, and then compares the predicted value with the economic threshold: if the predicted life is greater than or equal to the economic threshold, it indicates that there is still considerable economic benefit after regrinding, then the regular sharpening process continues, the cumulative number of regrindings is incremented by 1, and the tool returns to the loop.

[0060] If the predicted lifespan is lower than the economic threshold, a dynamic scrapping mechanism is triggered. At this time, even if the cumulative number of regrindings of the tool has not yet reached its default maximum allowable value (for example, it may be physically allowed to be regrinded 10 times, but it has only been regrinded 6 times so far), the system will forcibly set the current maximum allowable value of the tool to the current number of times, and immediately bypass the tool sharpening judgment, directly judge it as scrapped, mark it and transfer it to the scrapping storage area.

[0061] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0062] In one embodiment, the preset time threshold has a dynamic adjustment mechanism, the specific steps of which include: Obtain the historical tool flow demand arrival rate, average response time of automated guided vehicles (AGVs), AGV idle rate, and line downtime losses due to tool shortages for each production line. Based on the historical tool turnover demand arrival rate of each production line, the average response time of the automated guided vehicle (AGV), the AGV empty load rate, and the line downtime waiting losses caused by tool shortage, the tool waiting cost function and the AGV transportation cost function of the aggregate group are established respectively. With the goal of minimizing the sum of the tool waiting cost function and the automated guided vehicle transportation cost function of the aggregation group, the preset time threshold of the aggregation group corresponding to the same line identifier and tool holder type is optimized online; When the utilization rate of the automated guided vehicle is lower than the first preset value, or the inventory of the production line tools is higher than the first inventory threshold, the preset time threshold is extended. When the utilization rate of the automated guided vehicle is higher than the second preset value, or the inventory of cutting tools on the production line is lower than the second inventory threshold, the preset time threshold is shortened.

[0063] Obtain historical tool flow demand arrival rate, average response time of automated guided vehicles (AGVs), AGV idle rate, and line downtime losses due to tool shortages for each production line.

[0064] In this embodiment, the historical tooling demand arrival rate, average response time of automated guided vehicles (AGVs), AGV idle rate, and downtime losses due to tool shortages are obtained for each production line. The historical tooling demand arrival rate refers to the number of tooling demand requests generated per unit time within a preset historical period, which can be obtained by statistically analyzing demand records in the production line management system. The average response time of the AGVs refers to the average time from receiving a transport task instruction to arriving at the designated production line, which can be calculated from the task dispatch time and arrival confirmation time recorded by the scheduling system. The AGV idle rate refers to the proportion of idle travel time or distance during the execution of a transport task to the total travel time or distance, which can be obtained through AGV operation log analysis. The downtime losses due to tool shortages refer to the unit time downtime cost caused by the lack of required tools, which can be calculated based on the production line cycle time, product output value, and historical downtime duration due to tool shortages. The above parameters can be collected in real time or updated at certain intervals (e.g., every 5 minutes, every 15 minutes, or per shift) for subsequent online optimization calculations.

[0065] Specifically, the tool waiting cost function for aggregate groups is used to characterize the cost arising from changes in the waiting time of aggregate groups, and it is positively correlated with a preset time threshold. The larger the preset time threshold, the longer the time it takes for the aggregate group to wait from creation to triggering the transport task, the more the tool stays on the online body side, and the higher the tool waiting cost.

[0066] The AGV transportation cost function characterizes the cost arising from changes in the frequency of transportation task triggering, and it is negatively correlated with a preset time threshold. A larger preset time threshold results in fewer transportation tasks triggered per unit time, leading to a lower total AGV transportation cost. To minimize the sum of the tool waiting cost function and the AGV transportation cost function, the preset time threshold for aggregation groups corresponding to the same line identifier and tool holder type is optimized online.

[0067] After obtaining the preset time threshold through the above online optimization, further adjustments are made based on real-time operating status to address sudden or unsteady operating conditions not fully covered by the optimization model. Specifically: when the utilization rate of the automated guided vehicle (AGV) is lower than the first preset value, or the line tool inventory is higher than the first inventory threshold, it indicates that the current transportation resources are relatively idle or the line tool reserves are sufficient. The preset time threshold can be appropriately extended to further reduce transportation frequency and increase the loading rate of a single transportation. When the utilization rate of the AGV is higher than the second preset value, or the line tool inventory is lower than the second inventory threshold, it indicates that the current transportation resources are tight or the line tool reserves are insufficient, posing a risk of tool shortage and line stoppage. In this case, the preset time threshold should be shortened to accelerate the tool flow response speed and ensure production continuity.

[0068] The above correction steps can be used as supplementary rules to the online optimization results and executed after each optimization cycle; or they can be triggered immediately when a significant change is detected in the utilization rate of the automated guided vehicle or the inventory of cutting tools on the production line, thereby achieving rapid dynamic adjustment of the preset time threshold.

[0069] Through the above dynamic adjustment mechanism, this embodiment can optimize the preset time threshold in real time according to the actual tool demand intensity of each production line, AGV operating efficiency and production line downtime risk, so that tool flow scheduling can automatically find the optimal balance between tool waiting cost and automated guided vehicle transportation cost, avoiding the waste of transportation resources or untimely tool supply caused by fixed thresholds, and improving the economy and reliability of tool flow management.

[0070] In one embodiment, when there are multiple aggregate groups with different tool holder types under the same line identifier, and they are triggered sequentially or simultaneously within a preset time window, if the sum of the number of tools corresponding to each aggregate group does not exceed the single transport capacity of the automated guided vehicle, then each aggregate group is combined into a joint transport task.

[0071] In one embodiment, in the joint transportation task, tools of different handle types are respectively loaded into independent closed tool boxes or partitioned material boxes. Each independent closed tool box or partitioned material box can only hold the same type of tool handle and is set with a corresponding tool handle type identifier. After the automated guided vehicle completes the transportation, the line receives the tools according to the tool handle type identifier in the partitioned area. The quantity count and timer of each aggregated group are reset at the same time.

[0072] In this embodiment, the tool flow control method, based on dynamic grouping and trigger scheduling, further provides a joint transportation mechanism to address the situation where multiple aggregate groups of different tool holder types may exist simultaneously under the same line identifier. This mechanism is used to reduce the number of low-load transports by the automated guided vehicle (AGV) while ensuring that tools of different tool holder types are not mixed, thereby improving transportation efficiency and tool flow response speed.

[0073] Specifically, when there are multiple aggregation groups with different tool holder types under the same line identifier, and they are triggered sequentially or simultaneously within a preset time window, if the sum of the number of tools corresponding to each aggregation group does not exceed the single transport capacity of the automated guided vehicle, then each aggregation group will be combined into a joint transport task.

[0074] The preset time window refers to the time range within which trigger times of different aggregation groups can be merged. The length of this time window can be preset or dynamically adjusted based on factors such as the scheduling cycle of the automated guided vehicle (AGV), the urgency of the production line's tooling needs, the length of the transport path, and the average response time of the AGV. For example, when the AGV utilization rate is low or the production line's tooling inventory is sufficient, the preset time window can be appropriately extended to merge more triggering tasks; when tooling needs are urgent or transport resources are tight, the preset time window can be shortened to ensure timely tooling delivery.

[0075] The single transport capacity of the automated guided vehicle (AGV) refers to the total number or weight of tools that the AGV can safely carry in one trip. Its specific value can be determined by factors such as the AGV's rated load capacity, hopper size, and toolbox specifications. When determining whether to merge groups, it is necessary to ensure that the sum of the number of tools corresponding to each merge group does not exceed this capacity to avoid overloading or the need for additional transport.

[0076] In combined transport operations, tools with different handle types are placed in separate, enclosed toolboxes or partitioned bins. Each enclosed toolbox or partitioned bin holds only one type of tool handle and is labeled accordingly. The enclosed toolboxes can be dedicated tool containers with sealed lids to prevent tools from colliding, contaminating, or being damaged during transport. The partitioned bins can be multiple independent compartments within a single bin, each designated for one type of tool handle. Tool handle type identification can be in the form of QR codes, RFID tags, color markings, or text labels to facilitate rapid identification and differentiation during automated guided vehicle (AGV) transport and line receiving.

[0077] After the automated guided vehicle completes transportation, the production line receives tools according to the tool holder type identification. This means tools of different tool holder types are sent to their corresponding storage areas or directly to their respective processing equipment, avoiding errors in retrieval or chaotic tool management due to mixed loading. The production line can be equipped with identification devices corresponding to the tool holder type identification, such as barcode scanners or RFID readers, which automatically identify and allocate tools to the appropriate areas upon receipt.

[0078] The quantity counts and timers for each merged aggregation group are simultaneously reset. That is, each merged aggregation group is considered to have completed one transport trigger, its accumulated tool flow demand count is reset to zero, and the timer restarts to prepare for the next round of aggregation and triggering. In this way, subsequent tool flow demands for each aggregation group can be dynamically regrouped and trigger conditions re-evaluated without being affected by this joint transport.

[0079] Through the aforementioned combined transport mechanism, this embodiment can aggregate and transport multiple tool holder types of different types on the same production line while maintaining the separation of tool holder types. This fully utilizes the single-trip transport capacity of the automated guided vehicle (AGV), reduces the number of transport tasks, and lowers the AGV's idle rate and operating costs. Simultaneously, since the triggering conditions for each aggregated group remain independent, combined transport does not disrupt the original dynamic grouping and scheduling logic, improving the economy and flexibility of tool flow management.

[0080] In one embodiment, a tool flow control device is provided, which corresponds one-to-one with the tool flow control method described in the above embodiments. For example... Figure 3 As shown, the detailed descriptions of each functional module of this tool flow control device are as follows: The acquisition module is used to acquire the tool flow requirements of each production line; wherein, the tool flow requirements include at least the production line identifier and the tool holder type; The grouping module is used to dynamically group the tool flow requirements to obtain several aggregate groups; each aggregate group corresponds to a line body identifier and a tool holder type. The counting module is used to time the start time of the aggregation group added to the first tool flow request, and to set the count of the number of tool flow requests in the aggregation group. The task module is used to determine in real time whether the quantity count has reached a preset quantity threshold or the time count has reached a preset time threshold. If either condition is met, an automated guided vehicle (AGV) transportation task is generated for the aggregation group, and the quantity count and time count of the aggregation group are reset. It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. Their specific functions and technical effects can be found in the method embodiments section, and will not be repeated here.

[0081] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0082] This application also provides a computer device, such as... Figure 4 As shown, the computer device includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor. When the processor executes the computer program, it implements the steps in any of the above method embodiments, or when the processor executes the computer program, it implements the functions of each module / unit in the above device embodiments.

[0083] For example, the computer program may be divided into one or more modules / units, which are stored in the memory and executed by the processor to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the computer device.

[0084] Those skilled in the art will understand that Figure 4The computer device described is merely an example and does not constitute a limitation on the computer device. It may include more or fewer components than shown, or combine certain components, or different components. For example, the computer device may also include input / output devices, network access devices, buses, etc.

[0085] The aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or field-programmable gate arrays (FPGAs). Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0086] The memory can be an internal storage unit of the computer device, such as a hard drive or RAM. The memory can also be an external storage device of the computer device, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. Furthermore, the memory can include both internal and external storage units of the computer device.

[0087] This application also provides a readable storage medium storing a computer program, which, when executed by a processor, is used to implement the steps in the above-described method embodiments.

[0088] This application provides a computer program product that, when run on an electronic device, causes the electronic device to execute the steps described in the various method embodiments above.

[0089] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0090] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0091] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0092] In the embodiments provided in this application, it should be understood that the disclosed apparatus / devices and methods can be implemented in other ways. For example, the apparatus / device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0093] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0094] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A tooling process control method, characterized in that, include: Obtain the tool flow requirements for each production line; wherein, the tool flow requirements include at least the production line identifier and the tool holder type; The tool flow requirements are dynamically grouped to obtain several aggregate groups; each aggregate group corresponds to a line body identifier and a tool holder type. Set a timer for the start time of the aggregation group added to the first tool transfer request, and set a count to record the number of tool transfer requests within the aggregation group; In real time, it is determined whether the quantity count has reached a preset quantity threshold or whether the time count has reached a preset time threshold. If either condition is met, an automated guided vehicle transportation task is generated for the aggregation group, and the quantity count and time count of the aggregation group are reset. The steps of dynamically grouping the tool flow requirements to obtain several aggregate groups include: Based on the existing aggregation group, the tool flow requirements are matched with line identification and tool holder type; If a matching result is found, the tool flow requirement is categorized into the matching aggregation group, and the number of aggregation groups is counted. If the matching result shows that it does not exist, a new aggregation group is constructed according to the tool flow requirements, and the quantity counting and time timing of the aggregation group are started.

2. The tool flow control method as described in claim 1, characterized in that, The automated guided vehicle (AGV) transport task is constrained to transport only the same type of tool holder per task. When multiple aggregate groups with the same line identifier trigger tasks one after another, the corresponding AGV transport tasks are added to the task queue according to the order of triggering time. After the previous AGV transport task is completed, the next AGV transport task is dispatched.

3. The tool flow control method as described in claim 1, characterized in that, The tool flow requirements also include tool preparation requirements and tool retraction requirements, which are executed independently of the dynamic grouping and subsequent scheduling logic.

4. The tool flow control method as described in claim 1, characterized in that, For the tool recovery required by the tool retraction requirement, tool inspection is performed, and grading is carried out based on the inspection results. The specific steps include: The wear condition of the flank face of the recovered tool is monitored to obtain the amount of flank face wear of the recovered tool; When the wear on the back face is less than 0.1mm, and simultaneously the following conditions are met: no chipping on the cutting edge, dimensional deviation within a preset range, and predicted remaining life greater than a preset ratio, the tool is determined to be in life adjustment state. After correcting its remaining life parameters, it is returned to the production line for continued use. When the wear on the back face is between 0.1mm and 0.3mm, and the cutting edge chipping is repairable and the cumulative number of regrinding times is less than the maximum allowable value, the tool is determined to be in a grinding state, a grinding task is generated and transferred to the regrinding station; When the wear on the back face is greater than or equal to 0.3mm, or when any one of the following conditions is met: the chipping of the cutting edge exceeds the limit, the cumulative number of regrindings reaches the maximum allowable value, or there is damage to the substrate, the tool is determined to be scrapped, marked as scrapped, and transferred to the scrap storage area.

5. The tool flow control method as described in claim 4, characterized in that, A digital profile is created for each uniquely identified cutting tool, recording its wear data, actual cutting time, processed material, and working condition parameters for each life adjustment. A machine learning algorithm is used to build a wear trend prediction model for the tool based on the digital profile to predict the effective cutting life that can be achieved after the next regrinding. When the predicted effective cutting life after the next regrinding is lower than a preset economic threshold, even if the cumulative number of regrinding has not reached the default maximum allowable value, the current maximum allowable value of the tool is dynamically set to the current number of regrindings, and the tool is directly determined to be scrapped.

6. The tool flow control method as described in claim 1, characterized in that, The preset time threshold has a dynamic adjustment mechanism, the specific steps of which include: Obtain the historical tool flow demand arrival rate, average response time of automated guided vehicles (AGVs), AGV idle rate, and line downtime losses due to tool shortages for each production line. Based on the historical tool turnover demand arrival rate of each production line, the average response time of the automated guided vehicle (AGV), the AGV empty load rate, and the line downtime waiting losses caused by tool shortage, the tool waiting cost function and the AGV transportation cost function of the aggregate group are established respectively. With the goal of minimizing the sum of the tool waiting cost function and the automated guided vehicle transportation cost function of the aggregation group, the preset time threshold of the aggregation group corresponding to the same line identifier and tool holder type is optimized online; When the utilization rate of the automated guided vehicle is lower than the first preset value, or the inventory of the production line tools is higher than the first inventory threshold, the preset time threshold is extended. When the utilization rate of the automated guided vehicle is higher than the second preset value, or the inventory of cutting tools on the production line is lower than the second inventory threshold, the preset time threshold is shortened.

7. The tool flow control method as described in claim 1, characterized in that, When multiple aggregation groups with different tool holder types exist under the same line identifier, and they are triggered sequentially or simultaneously within a preset time window, if the sum of the number of tools corresponding to each aggregation group does not exceed the single transport capacity of the automated guided vehicle, then each aggregation group will be combined into a joint transport task.

8. The tool flow control method as described in claim 7, characterized in that, In the joint transportation task, tools of different handle types are loaded into independent closed tool boxes or partitioned material boxes. Each independent closed tool box or partitioned material box can only hold the same type of tool handle and is set with a corresponding tool handle type label. After the automated guided vehicle completes the transportation, the line receives the tools according to the tool handle type label in the partitioned area. The quantity count and timer of each aggregated group are reset at the same time.

9. A tool flow control device, characterized in that, To implement the tool flow control method according to any one of claims 1-8, comprising: The acquisition module is used to acquire the tool flow requirements of each production line; wherein, the tool flow requirements include at least the production line identifier and the tool holder type; The grouping module is used to dynamically group the tool flow requirements to obtain several aggregate groups; each aggregate group corresponds to a line body identifier and a tool holder type. The counting module is used to time the start time of the aggregation group added to the first tool flow request, and to set the count of the number of tool flow requests in the aggregation group. The task module is used to determine in real time whether the quantity count has reached a preset quantity threshold or the time count has reached a preset time threshold. If either condition is met, an automated guided vehicle transportation task is generated for the aggregation group, and the quantity count and time count of the aggregation group are reset.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the tool flow control method as described in any one of claims 1 to 8.

11. A readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the tool flow control method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, enables the implementation of the steps of the tool flow control method as described in any one of claims 1 to 8.

Images