Electrostatic sensitive semiconductor material grading warehouse management method and system

Abstract

The present application relates to warehouse management and inventory state control technical field, especially to a kind of electrostatic sensitive semiconductor material grading warehouse management method and system.The method includes: receiving the bar code information or outer package label information of goods semiconductor material, identifying package type, humidity level MSL, sealing mark, package integrity and humidity indication state, generate target library area sub-domain code;Based on target library area sub-domain code, storage location state data, batch expiration information or workshop life state, calculate recommended storage location number and generate upper shelf instruction;Establish batch storage location binding record;Based on environmental monitoring sensor reading and environmental threshold, generate environmental abnormality early warning label, priority picking state or overdue locking state;When receiving the delivery picking task, generate picking verification result and anti-static operation item list.The present application makes library area distribution, batch early warning and delivery verification form continuous record relationship, effectively improves the consistency of semiconductor material warehouse state control.

Description

Technical Field

[0001] This invention relates to the field of warehouse management and inventory status control technology, and in particular to a graded warehouse management method and system for electrostatic sensitive semiconductor materials. Background Technology

[0002] In the field of warehouse management and inventory status control technology, existing solutions for electrostatic-sensitive semiconductor materials typically use barcode readers, warehouse management systems, shelves, storage compartments, environmental monitoring sensors, and anti-static protection devices to record and manage material information, batch information, location information, and temperature and humidity status. While these solutions can complete inbound registration, storage location recording, environmental reading collection, and outbound operations in typical scenarios, they are prone to limitations when semiconductor materials arrive in mixed quantities and exhibit differences in packaging type, moisture sensitivity level (MSL), and packaging status. These limitations include inconsistent warehouse allocation criteria, discontinuous batch status recording, and insufficient coordination in the outbound verification process.

[0003] Existing solutions often rely on part numbers, material categories, manually set storage areas, or fixed first-in-first-out (FIFO) rules for processing. When packaging type, moisture sensitivity level (MSL), seal markings, packaging integrity, humidity indication status, or workshop lifespan changes, there is a lack of stable coordination between inbound identification, storage location allocation, environmental monitoring, and outbound picking. This can easily lead to a mismatch between the target storage area and the material's sensitivity attributes, and make it difficult to correlate abnormal environmental readings with specific batch storage location records.

[0004] For the joint processing of package type, moisture level (MSL), batch storage location binding records, environmental monitoring sensor readings, and outbound picking tasks, existing technologies still suffer from common shortcomings, such as insufficient coordination between warehouse sub-domain allocation, batch warning status generation, and outbound verification records. Therefore, it is necessary to address the issues of coordinating warehouse sub-domain allocation, batch warnings, and outbound verification based on package type, MSL, and batch storage location binding records, specifically for scenarios involving mixed arrivals of electrostatically sensitive semiconductor materials. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a method for graded storage and management of electrostatic sensitive semiconductor materials, comprising:

[0006] S100: Upon receiving the barcode information or outer packaging label information of the semiconductor material, identify the part number, batch information, package type, humidity sensitivity level MSL, sealing mark, packaging integrity and humidity indication status, determine the electrostatic sensitivity level according to the package type, and generate the target warehouse area subdomain code by matching the level mapping configuration table.

[0007] S200: Based on the target storage area subdomain code, obtain the list of available storage locations and storage location status data, calculate the recommended storage location number according to the correspondence between batch expiration information or workshop life status and the ease of access to storage locations, and generate a shelf placement instruction.

[0008] S300. Based on the put-away instruction and put-away feedback, establish a batch storage location binding record, recording the storage location number, humidity sensitivity level MSL, opening mark and workshop lifespan end time.

[0009] S400. Based on the batch storage location binding record, compare the environmental monitoring sensor readings with the environmental threshold corresponding to the target storage area subdomain code, and query the batch storage location binding record within the same storage area subdomain to generate an environmental anomaly warning label, priority picking status, or overdue lock status.

[0010] S500: When receiving an outbound picking task, determine the route area based on the storage location sequence, and generate picking verification results and an anti-static operation item list according to the electrostatic sensitivity attributes corresponding to the route area.

[0011] Furthermore, the electrostatic sensitivity classification is determined according to the package type, including: classifying exposed solder ball packages as high electrostatic sensitivity, tape and lead packages as medium electrostatic sensitivity, and through-hole packages as low electrostatic sensitivity.

[0012] Furthermore, the graded mapping configuration table includes an electrostatic sensitivity grade field, a humidity sensitivity level MSL field, a seal identification field, a packaging integrity field, a humidity indication status field, and a target storage area subdomain code field; the electrostatic sensitivity grade, the humidity sensitivity level MSL, the seal identification, the packaging integrity, and the humidity indication status are matched with the fields in the graded mapping configuration table to obtain the target storage area subdomain code.

[0013] Furthermore, generating the target warehouse area subdomain code includes: when the packaging integrity indicates packaging damage, the humidity indication status indicates abnormal humidity, the barcode information is incomplete, or the humidity sensitivity level MSL is missing, generating isolation inspection information and writing the isolation inspection information into the inventory data table record.

[0014] Further, calculating the recommended storage location number includes: screening candidate storage locations based on the target storage area subdomain code; determining adjacent candidate storage locations from the candidate storage locations based on existing storage locations with the same material number or batch; and sorting the adjacent candidate storage locations according to the ease of access to the storage location, the batch expiration information, and the workshop life status to obtain the recommended storage location number.

[0015] Furthermore, establishing the batch storage location binding record includes: writing the batch information, the target storage area subdomain code, the recommended storage location number, the storage time, the humidity sensitivity level MSL, the opening identifier, and the workshop lifespan expiration time into the inventory data table; when the opening identifier indicates that it has been opened, the workshop lifespan expiration time is calculated according to the opening timestamp and the workshop lifespan rule corresponding to the humidity sensitivity level MSL.

[0016] Furthermore, generating the environmental anomaly warning label includes: calling an environmental threshold based on the storage area subdomain code corresponding to the environmental monitoring sensor reading; comparing the temperature or humidity with the environmental threshold; when the temperature or humidity exceeds the environmental threshold, querying the batch storage location binding record within the same storage area subdomain, and updating the environmental anomaly warning label on the queried batch storage location binding record.

[0017] Furthermore, generating the priority picking state or the overdue lock state includes: comparing the current time with the workshop lifespan deadline; generating the priority picking state when the remaining workshop lifespan reaches the workshop lifespan checkpoint; generating the overdue lock state when the current time exceeds the workshop lifespan deadline, and outputting a transfer baking work order or a return inspection work order.

[0018] Furthermore, upon receiving a request to re-enter returned or transferred materials, the packaging integrity and humidity indication status of the returned or transferred materials are reread; when the packaging integrity indicates packaging damage or the humidity indication status indicates abnormal humidity, isolation inspection information is generated, and the returned or transferred materials are prevented from returning to the normal storage location.

[0019] Furthermore, a graded storage management system for electrostatic sensitive semiconductor materials includes: an attribute identification and graded mapping module, a storage location allocation module, a batch binding module, an early warning status generation module, and an outbound verification module; the system is used to implement the method described in any of the above embodiments.

[0020] The key innovations of this invention include:

[0021] (1) The package type, humidity sensitivity level (MSL), sealing mark, packaging integrity and humidity indication status of the delivered semiconductor materials are included in the same hierarchical mapping configuration table, and the electrostatic sensitivity level corresponding to the package type is matched with the humidity sensitivity level (MSL) to generate the target library area subdomain code.

[0022] (2) The target storage area subdomain code is used as the input for the storage location candidate range. Combined with the list of available storage locations, storage location status data, batch expiration information or workshop life status and the correspondence between storage location accessibility, the recommended storage location number is calculated, and a batch storage location binding record is established based on the shelving instruction and shelving feedback.

[0023] (3) Using the batch storage location binding record as a common index for environmental monitoring and outbound verification, compare the environmental monitoring sensor readings with the environmental threshold corresponding to the target storage area subdomain code, generate an environmental anomaly warning label, priority picking status or overdue lock status, and generate picking verification results and anti-static operation item list based on the storage location sequence of the outbound picking task.

[0024] The following are its main beneficial effects:

[0025] (1) To address the issue of inconsistent allocation criteria in existing solutions, a hierarchical mapping configuration table is used to convert packaging type, moisture sensitivity level (MSL), and packaging status into target warehouse subdomain codes, forming a field-based matching result from material attributes to warehouse subdomains, thus ensuring that warehouse allocation records have a unified data basis.

[0026] (2) To address the problem of insufficient connection between storage location allocation and batch expiration date or workshop life status in the existing scheme, candidate storage locations are limited by the target storage area subdomain code, and recommended storage location numbers are generated according to the correspondence between batch expiration date information or workshop life status and the ease of access of storage locations, so that a continuous record relationship is formed between the shelving instruction, storage location number and batch storage location binding record.

[0027] (3) To address the problem of insufficient connection between environmental readings, batch status and outbound verification records in the existing scheme, the target warehouse area subdomain code, environmental threshold, workshop lifespan expiration time and storage location sequence are associated through batch storage location binding records, so that environmental anomaly warning labels, priority picking status, overdue lock status, picking verification results and anti-static operation item list correspond to specific batches and storage locations. Attached Figure Description

[0028] Figure 1 A flowchart illustrating a graded storage management method for electrostatic sensitive semiconductor materials provided in this application embodiment;

[0029] Figure 2 This is a structural block diagram of a graded storage and management system for electrostatic sensitive semiconductor materials provided in an embodiment of this application. Detailed Implementation

[0030] Example 1: Refer to Figure 1 This is a flowchart illustrating a graded storage management method for electrostatic sensitive semiconductor materials provided in an embodiment of the present invention. The process may include at least steps S100-S500:

[0031] S100: Upon receiving the barcode information or outer packaging label information of the semiconductor material, identify the part number, batch information, package type, humidity sensitivity level MSL, sealing mark, packaging integrity and humidity indication status, determine the electrostatic sensitivity classification according to the package type, and generate the target warehouse area subdomain code by matching the classification mapping configuration table.

[0032] S200: Based on the target storage area subdomain code, obtain the list of available storage locations and storage location status data, calculate the recommended storage location number according to the correspondence between batch expiration information or workshop life status and the ease of access to storage locations, and generate a shelf placement instruction.

[0033] S300. Based on the put-away instruction and put-away feedback, establish a batch storage location binding record, recording the storage location number, humidity sensitivity level MSL, opening mark and workshop lifespan end time.

[0034] S400. Based on the batch storage location binding record, compare the environmental monitoring sensor readings with the environmental threshold corresponding to the target storage area subdomain code, and query the batch storage location binding record within the same storage area subdomain to generate an environmental anomaly warning label, priority picking status, or overdue lock status.

[0035] S500: When receiving an outbound picking task, determine the route area based on the storage location sequence, and generate picking verification results and an anti-static operation item list according to the electrostatic sensitivity attributes corresponding to the route area.

[0036] S100: Receive barcode information or outer packaging label information of the semiconductor material, identify part number, batch information, package type, humidity sensitivity level (MSL), sealing mark, packaging integrity and humidity indication status, determine electrostatic sensitivity classification according to the package type, and generate target warehouse area subdomain code by matching the classification mapping configuration table.

[0037] In this embodiment, S100 is executed by the attribute recognition module and the hierarchical mapping module in the warehouse management system. The attribute recognition module is connected to a receiving terminal, a barcode reader, an image recognition device, or a manual input interface; when the arriving semiconductor materials enter the receiving station, the receiving terminal receives the barcode information or the outer packaging label information. The barcode information includes the encoded content in a one-dimensional barcode, a two-dimensional barcode, or a supplier label; the outer packaging label information includes the part number, batch information, package type, moisture sensitivity level (MSL), sealing mark, and packaging date. MSL stands for Moisture Sensitivity Level, representing the moisture sensitivity level of the semiconductor material.

[0038] The delivered semiconductor materials may be integrated circuit chips, packaged devices, wafer-related materials, or electronic components. The packaging integrity refers to the condition of the outer packaging during receiving inspection, including recorded values ​​such as normal, damaged packaging, abnormal sealing, and vacuum failure. The humidity indication status technical feature refers to the humidity status inside the packaging, indicated by a humidity indicator card, humidity label on the outer packaging, or receiving inspection record, including both normal and abnormal humidity recorded values. The sealing mark is used to record whether the original packaging remains sealed, including both sealed and opened states.

[0039] After receiving the barcode information or the outer packaging label information, the attribute recognition module first extracts the part number and batch information; then, it calls the material master data according to the part number and reads the packaging type and humidity sensitivity level MSL associated with the part number; when the packaging type or humidity sensitivity level MSL in the outer packaging label information has different values ​​from the material master data, the attribute recognition module retains both the outer packaging label information and the material master data values ​​and generates a field conflict flag. The field conflict flag is written to the inventory data table record and enters the manual review queue; after the review is completed, the review result is used as the input of the hierarchical mapping module.

[0040] The grading mapping module determines the ESD sensitivity grade based on the package type. In one embodiment, exposed solder ball packages are classified as high ESD sensitive, tape and pin packages as medium ESD sensitive, and through-hole packages as low ESD sensitive. Exposed solder ball packages include BGA and QFN packages; tape and pin packages include SOP and SOIC packages; and through-hole packages include DIP packages. The above package type is only one field classification method. In another embodiment, the warehouse management system maintains the correspondence between package type and ESD sensitivity grade through a package type configuration table, and the grading mapping module generates the ESD sensitivity grade according to the package type configuration table.

[0041] The hierarchical mapping configuration table is maintained by the warehouse management system. This table includes fields for electrostatic sensitivity rating, humidity sensitivity level (MSL), seal identification, packaging integrity, humidity indication status, and target storage area subdomain code. The target storage area subdomain code represents a storage area code in the warehouse management system, categorized by storage conditions, anti-static requirements, or isolation status. In one embodiment, the target storage area subdomain code corresponds to a regular shelf subdomain, a standard drying cabinet subdomain, a reinforced drying cabinet subdomain, and an isolated inspection subdomain. The hierarchical mapping module matches the electrostatic sensitivity rating, humidity sensitivity level (MSL), seal identification, packaging integrity, and humidity indication status with the fields in the hierarchical mapping configuration table to obtain the target storage area subdomain code.

[0042] During the field matching process, the hierarchical mapping module first processes abnormal fields, then processes normal hierarchical fields. When the packaging integrity indicates packaging damage, the humidity indication status indicates abnormal humidity, the barcode information is incomplete, or the humidity sensitivity level MSL is missing, the hierarchical mapping module generates isolation inspection information and writes it into the inventory data table record. At this time, the isolation inspection information serves as the matching basis for the target warehouse area subdomain code, and the arrived semiconductor material enters the candidate range of the isolation inspection subdomain. For arrived semiconductor materials without abnormal fields, the hierarchical mapping module then performs target warehouse area subdomain code matching based on electrostatic sensitivity classification, humidity sensitivity level MSL, and sealing label.

[0043] In one implementation of a semiconductor trading warehouse, a single receiving task comprises three batches of arriving semiconductor materials. The first batch consists of BGA packages with a moisture sensitivity level (MSL) of 3, a sealed label, normal packaging integrity, and a normal humidity indication. The grading and mapping module generates a high electrostatic discharge (ESD) sensitivity based on the BGA package and matches it with the MSL of 3 and the sealed label to generate a target warehouse subdomain code corresponding to the enhanced desiccant subdomain. The second batch consists of SOIC packages with an MSL of 2 and a sealed label. The grading and mapping module generates a medium ESD sensitivity and generates a target warehouse subdomain code corresponding to the standard desiccant subdomain. The third batch has an abnormal humidity indication. The grading and mapping module generates isolation inspection information and generates a target warehouse subdomain code corresponding to the isolation inspection subdomain.

[0044] The target storage area subdomain code generated in S100, along with the part number, batch information, electrostatic sensitivity classification, humidity sensitivity level (MSL), sealing label, packaging integrity, and humidity indication status, are written into the temporary storage record. This temporary storage record is then entered into S200 as input for filtering the list of available storage locations and storage location status data. If S100 generates isolation inspection information, S200 only performs storage location calculations in the list of available storage locations corresponding to the isolation inspection subdomain.

[0045] In one specific embodiment:

[0046] S100 is executed by the attribute recognition module and hierarchical mapping module in the warehouse management system. The attribute recognition module connects to the receiving terminal, barcode reader, image recognition device, or manual input interface; the receiving terminal receives barcode information or outer packaging label information when the arriving semiconductor materials enter the receiving station. The barcode information includes the encoded content in the 1D barcode, 2D barcode, or supplier label; the outer packaging label information includes part number, batch information, package type, humidity sensitivity level (MSL), seal mark, and packaging date. The arriving semiconductor materials are integrated circuit chips, packaged devices, wafer-related materials, or electronic components. Packaging integrity indicates the status of the outer packaging during receiving inspection, including four recorded values: normal, damaged packaging, abnormal seal, and vacuum failure; humidity indication status refers to the humidity status inside the packaging as indicated by a humidity indicator card, outer packaging humidity label, or receiving inspection record, including two recorded values: normal and abnormal humidity; the seal mark is used to record whether the original packaging remains sealed, including two states: sealed and opened. After receiving barcode or outer packaging label information, the attribute recognition module first extracts the part number and batch information. Then, it retrieves the material master data according to the part number, reading the packaging type and humidity sensitivity level MSL associated with the part number. When the packaging type or humidity sensitivity level MSL in the outer packaging label information differs from the material master data, the attribute recognition module retains both sets of values ​​from the outer packaging label information and the material master data, and generates a field conflict flag. This field conflict flag is written to the inventory data table record and enters the manual review queue. To address the issue of how to quantify the degree of conflict and form a conflict flag vector that can be input into the subsequent matching engine in the above multi-source data conflict scenario, this step constructs the following field conflict detection and flag generation mechanism.

[0047] Formula ① concatenates the discrete code of the packaging type with the numerical code of the MSL (Material Standard Level) to form an attribute vector, and uses the weighted Euclidean deviation between the outer packaging label information vector and the material master data vector as the conflict intensity index; Formula ② thresholds this conflict intensity index to generate a composite conflict marker vector containing conflict type code and conflict level code. Formula ① is:

[0048]

[0049] in, : Field conflict intensity index, a non-negative real number calculated by formula ①, is used to quantify the overall degree of deviation between the outer packaging label information and the material master data in the two dimensions of packaging type and moisture sensitivity level MSL. The value range is non-negative real number.

[0050] : The summation index variable, representing the ordinal number of the attribute dimension currently participating in conflict detection, with a value range of 1. ;

[0051] The total number of attribute dimensions involved in conflict detection; a fixed value. The comparison dimensions are determined by the encapsulation type and the moisture sensitivity level (MSL) in this step.

[0052] : No. The conflict detection weight coefficients for dimensional attributes are preset and provided by the strategy configuration table of the warehouse management system. , This is used to adjust the contribution ratio of different attribute dimensions in the conflict intensity calculation;

[0053] The first item extracted from the outer packaging label information Dimensional attribute values, where The integer encoding value is obtained by mapping the encapsulation type according to the preset encapsulation encoding table. This is an integer value representing the moisture sensitivity level (MSL), derived from the parsing results of barcode information or outer packaging label information.

[0054] The first data read from the material master data Dimensional attribute values, where This refers to the integer code value obtained by mapping the packaging type in the material master data according to the same preset packaging code table. This is an integer value representing the moisture sensitivity level (MSL) in the material master data, sourced from the material master database of the warehouse management system.

[0055] The data source mapping relationship is as follows: Extracted from the packaging type field of the outer packaging label information and denoted as... Extract and record the moisture sensitivity rating (MSL) from the moisture sensitivity rating field on the outer packaging label information. Extract and record from the encapsulation type field of the material master data as Extract and record the moisture sensitivity level (MSL) from the material master data. ; , , , Together they form the formula ① .

[0056] Formula ① addresses the practical problem of converting qualitative differences into calculable quantitative deviation indicators when the outer packaging label and the material master data are inconsistent in terms of packaging type or MSL, providing a numerical basis for determining whether to generate field conflict markers and the level of conflict markers.

[0057] A simple numerical example is as follows: The outer packaging label of a certain batch of semiconductor materials indicates that the package type is BGA (encoded mapping value). MSL is 3 ( The material master data records that the package type corresponding to this part number is QFN (code mapping value). MSL is 2 ( ),but This field is a conflict intensity index. This indicates a moderate level of field conflict.

[0058] Formula ② is:

[0059]

[0060] in, : Field conflict marker vector, a binary structure calculated by formula ②, is used as the write value of the field conflict marker field in the inventory data table, encoded by the conflict type. and conflict level coding It consists of two components;

[0061] : Collision type encoding, an integer value obtained by the sign function, with a range of values. ,in This indicates that there are no field conflicts. This indicates a field conflict.

[0062] : Conflict level code, a non-negative integer value obtained by rounding down, with a range of non-negative integers, used to represent the number of conflict levels relative to a preset quantization step size;

[0063] : Sign function, determines the sign of the difference within parentheses; if the difference is greater than 1, it indicates a positive sign. Time return When the difference is less than or equal to Time return ;

[0064] The threshold for enabling conflict detection is preset by the policy configuration table of the warehouse management system and is a fixed value. This is used to determine if there are any conflicts in the fields that need to be recorded;

[0065] : The floor function rounds down the ratio of real numbers within parentheses and returns the largest integer not exceeding that real number;

[0066] The conflict level quantification step size is a fixed value preset by the strategy configuration table of the warehouse management system. It is used to discretize continuous conflict intensity indicators into level codes.

[0067] The data source mapping relationship is obtained from formula ①. Directly used as input to formula ②; threshold , Provided by the strategy configuration table of the warehouse management system. The practical problem solved by formula ② is: to discretize the continuous conflict intensity index calculated by formula ① into a structured conflict marker, so that the subsequent hierarchical mapping module can directly read the marker when performing field matching and decide whether to use the manual review result as an alternative input.

[0068] The hierarchical mapping module receives the part number, batch information, packaging type, humidity sensitivity level (MSL), seal mark, packaging integrity, humidity indication status, and field conflict marker vector output by the attribute recognition module. The matching calculation of the target library subdomain code begins. The hierarchical mapping module first determines the electrostatic sensitivity level based on the encapsulation type.

[0069] In one embodiment, exposed solder ball packages are defined as highly ESD sensitive, including BGA and QFN packages; tape and pin packages are defined as moderately ESD sensitive, including SOP and SOIC packages; and through-hole packages are defined as low ESD sensitive, including DIP packages.

[0070] In another implementation, the warehouse management system maintains the correspondence between packaging types and electrostatic sensitivity levels through a packaging type configuration table. The level mapping module generates electrostatic sensitivity levels according to the packaging type configuration table. The level mapping configuration table is maintained by the warehouse management system and includes fields for electrostatic sensitivity level, humidity sensitivity level (MSL), seal identification, packaging integrity, humidity indication status, and target storage area subdomain code. The target storage area subdomain code represents the storage area code in the warehouse management system, divided according to storage conditions, anti-static requirements, or isolation status, specifically corresponding to the regular shelf subdomain, the standard drying cabinet subdomain, the reinforced drying cabinet subdomain, and the isolated inspection subdomain.

[0071] During the field matching process, the hierarchical mapping module first processes abnormal fields, and then processes normal hierarchical fields. When packaging integrity indicates packaging damage, humidity indication status indicates abnormal humidity, barcode information is incomplete, or the humidity sensitivity level MSL is missing, the hierarchical mapping module generates isolation inspection information and writes this isolation inspection information into the inventory data table record. At this time, the isolation inspection information serves as the matching basis for the sub-domain code of the target warehouse area, and the arriving semiconductor materials enter the candidate range of the isolation inspection sub-domain.

[0072] For incoming semiconductor materials without any abnormal fields, the grading mapping module then performs target warehouse area subdomain code matching based on electrostatic sensitivity grading, humidity sensitivity level MSL, and sealing mark.

[0073] To address the issue of calculating the comprehensive matching degree of each candidate target library subdomain code when matching fields between multi-dimensional discrete attributes and hierarchical mapping configuration tables, this step constructs the following weighted matching score and abnormal short-circuit judgment mechanism.

[0074] Formula ③ calculates the comprehensive matching score of each candidate target library subdomain code; Formula ④ generates a short-circuit judgment signal based on the anomaly field detection results. This short-circuit judgment signal pre-filters the candidate subdomain set before ranking the comprehensive matching scores. Formula ③ is:

[0075]

[0076] in, : No. The comprehensive matching score of the candidate target library subdomain codes, calculated by formula ③, is a real number with a range of values. A higher score indicates a greater degree of match between the attribute combination of the currently delivered semiconductor material and the candidate subdomain.

[0077] : Index number of the candidate target library subdomain code, with a value range of These correspond to the regular shelf sub-domain, the standard drying cabinet sub-domain, the reinforced drying cabinet sub-domain, and the isolated inspection sub-domain, respectively.

[0078] The electrostatic sensitivity grading matching weight is determined by the field priority settings in the grading mapping configuration table, and the value is fixed. ;

[0079] : Category matching indicator function, performs equality determination on two discrete categorical input variables, and returns a value when they are equal. Otherwise return ;

[0080] The first item in the hierarchical mapping configuration table The electrostatic sensitivity grading field values ​​corresponding to each candidate subdomain are discrete categorical variables with a range of values. This information originates from the hierarchical mapping configuration table.

[0081] The grading mapping module classifies the electrostatic sensitivity of the semiconductor materials arriving in this batch based on the package type. This is a discrete categorical variable with a value range similar to... The same result is derived from the encapsulation type determination result of the hierarchical mapping module;

[0082] The humidity sensitivity level MSL matching weight is determined by the field priority settings in the hierarchical mapping configuration table, and is a fixed value. ;

[0083] MSL rating matching function, defined as Returns a real number, with a range of 1000. Dimensionless, used to calculate the degree of matching of humidity sensitivity level MSL;

[0084] The first item in the hierarchical mapping configuration table The humidity sensitivity level (MSL) field value corresponding to each candidate subdomain is an integer variable with a range of values. This information originates from the hierarchical mapping configuration table.

[0085] : The moisture sensitivity level (MSL) value of the semiconductor materials arriving in this batch, an integer variable, with a range of values. When field conflict marker vector of In case of conflict, the results of manual review shall be used first; otherwise, the MSL value in the outer packaging label information shall be used first, which is derived from the conflict-resolved outer packaging label information or the results of manual review.

[0086] : Maximum value function, takes the larger of the two real numbers within the parentheses;

[0087] The absolute value operator takes the absolute value of the value within the parentheses.

[0088] The matching weight of the seal identifier is determined by the field priority setting in the hierarchical mapping configuration table, and is a fixed value. ;

[0089] : Seal identifier matching function, defined as when It is valid if it is valid, otherwise Returns a boolean or integer value. This is used to determine whether the sealing status of the material meets the requirements of the candidate subdomain.

[0090] The first item in the hierarchical mapping configuration table The sealing identifier field value corresponding to each candidate subdomain is a Boolean variable. This indicates that the material in this subdomain must be in a sealed state. This indicates that the subdomain has no requirements for the sealing state, which is derived from the hierarchical mapping configuration table;

[0091] : The sealing label value of this batch of semiconductor materials, a Boolean variable. This indicates that it has been sealed. This indicates that the package has been opened, based on information from the outer packaging label.

[0092] The data source mapping relationship is as follows: read the first data source from the hierarchical mapping configuration table. The electrostatic sensitivity grading field corresponding to each candidate subdomain is denoted as follows: The humidity sensitivity level MSL field is denoted as The seal identifier field is denoted as The electrostatic sensitivity classification determined by the hierarchical mapping module based on the package type is denoted as follows: The moisture sensitivity level (MSL) is read from the outer packaging label information and recorded as follows: (Field conflicts are corrected after manual review); the sealing mark is read from the outer packaging label information and recorded as... .

[0093] Formula ③ addresses the practical problem of comparing the three dimensions of electrostatic sensitivity grading, humidity sensitivity level (MSL), and sealing mark with the corresponding fields of each candidate subdomain in the grading mapping configuration table, and obtaining a quantitative comprehensive matching score through weighted summation, thus providing a numerical basis for the optimal selection of subdomain codes in the subsequent target library area.

[0094] Formula ④ is:

[0095]

[0096] in, The abnormal short-circuit detection signal is a Boolean variable calculated by formula ④, and its value range is... , This indicates the presence of an abnormal field that requires short-circuiting, and the material will be directly redirected to an isolated subfield awaiting inspection. This indicates that there are no abnormal fields and the process can proceed to the normal hierarchical matching process.

[0097] The logical OR operator performs a logical OR operation on all the conditions within the parentheses. The overall result is true if any one of the conditions is true. Otherwise ;

[0098] : Packaging integrity field value read from outer packaging label information, a discrete categorical variable, with a value range of . The information comes from the packaging integrity record on the outer packaging label.

[0099] The baseline value for determining packaging damage is a categorical constant "packaging damage," which also includes sealing abnormalities and vacuum failures as a subset of abnormalities, used to differentiate between packaging damage and other packaging damage assessment criteria. Compare the samples to determine if the packaging is abnormal;

[0100] The humidity indication status field value is read from the outer packaging label information or receiving inspection record. It is a discrete categorical variable with a value range of [value range missing]. The information comes from humidity indicator cards, humidity labels on outer packaging, or receiving inspection records.

[0101] The baseline value for determining humidity anomalies is a categorical constant "humidity anomaly," used to distinguish it from other humidity anomalies. Compare the data to determine if the humidity level is abnormal;

[0102] Barcode information integrity flag, a Boolean variable. This indicates that the barcode information is complete and readable. This indicates that the barcode information is incomplete or that reading has failed, and is a reading status feedback from the barcode reader or image recognition device.

[0103] :exist In the expression, This is an integer constant representing the threshold value for determining whether a message is "incomplete" or "failed to read".

[0104] : The empty set symbol, in The expression indicates that the humidity sensitivity level MSL field is missing or has not been read as a valid value, which serves as the basis for determining the missing value.

[0105] The data source mapping relationship is as follows: Extracted from the packaging integrity field of the outer packaging label information and denoted as... Extract the humidity indicator status from the humidity indicator card or receiving inspection record and record it as follows: Extract the barcode information integrity flag from the reading results of the barcode reader or image recognition device and record it as... Read the moisture sensitivity level MSL from the outer packaging label information or material master data and record it as follows: .

[0106] Formula ④ addresses the practical problem of quickly pre-inspecting the physical condition and information integrity of the packaging of arriving semiconductor materials before entering the normal comprehensive matching and scoring process. Once any abnormality is detected, such as damaged packaging, abnormal humidity, incomplete barcode, or missing MSL, a short-circuit judgment signal is generated, and the materials are directly guided to the isolated inspection sub-domain to avoid abnormal materials entering the normal storage location allocation process, which would cause waste of warehousing resources and subsequent management chaos.

[0107] The hierarchical mapping module calculates the comprehensive matching score of each candidate subdomain based on formula ③. And the abnormal short-circuit determination signal obtained from formula ④ The final target library subdomain code decision and output are then executed. At that time, the hierarchical mapping module no longer depends on The sorting results directly generate isolation inspection information, which serves as the matching basis for the subdomain code of the target warehouse area, and classifies the arrived semiconductor materials into the candidate range of isolation inspection subdomains.

[0108] when At that time, the hierarchical mapping module in all The subdomain with the highest comprehensive matching score among the valid candidate subdomains is selected as the target warehouse area subdomain code; if multiple candidate subdomains have the same score and all are the highest value, the hierarchical mapping module makes a secondary decision according to the subdomain priority order preset in the hierarchical mapping configuration table (the enhanced subdomain of the drying cabinet takes priority over the standard subdomain of the drying cabinet, and the standard subdomain of the drying cabinet takes priority over the regular shelf subdomain).

[0109] To address the issues of how to uniformly encode the highest-scoring selection result and the isolated inspection information into the target database subdomain code output field during the decision-making process, and how to write all key fields of the matching process into the temporary database record, this step constructs the following decision output and record writing mechanism. Formula ⑤ is:

[0110]

[0111] in, The final output target library subdomain code field value is a discrete categorical variable calculated using formula ⑤, with a value range of [value range missing]. These correspond to the standard shelf subdomain code, the standard drying cabinet subdomain code, the reinforced drying cabinet subdomain code, and the isolated inspection subdomain code, respectively. Each code value is a string or an integer identifier and is uniformly maintained by the warehouse area subdomain coding table of the warehouse management system.

[0112] : The fixed code value corresponding to the isolated subdomain to be inspected is a discrete category constant, which comes from the warehouse area subdomain coding table of the warehouse management system;

[0113] Index number The corresponding target warehouse area subdomain code value is a discrete categorical variable, derived from the warehouse area subdomain coding table of the warehouse management system. Code field for each subdomain;

[0114] :exist The index number of the candidate subdomain with the highest comprehensive matching score under the given conditions is an integer variable with a value range of 1. ,Depend on The calculation yielded the result;

[0115] : Maximize the argument operator, return the value that makes the target function... Index variable that gets the maximum value .

[0116] The data source mapping relationship is calculated using formula ③. As input to formula ⑤, formula ④ calculates... It also serves as the input for formula ⑤; and All data is read from the warehouse area subdomain coding table of the warehouse management system.

[0117] Formula ⑤ addresses the practical problem of determining abnormal short circuit signals. Overall matching score The optimal selection result is uniformly converted into a standardized target storage area subdomain code output value, ensuring that regardless of whether an abnormal short circuit is triggered, S100 can output a storage area subdomain code field with a consistent structure for use by the storage location allocation module of S200.

[0118] A simple numerical example is as follows: A batch of semiconductor materials arriving is judged by formula ④ Formula ③ yields the result. (Regular shelving sub-area) (Standard sub-domain of drying cabinet) (Desiccant Enhanced Sub-domain) (Isolate the subdomain to be tested, but because) (Although this subdomain is included in the scoring, it should not normally be selected.) , To enhance the subdomain code for the drying cabinet, assume the value of the enhanced subdomain code for the drying cabinet in the warehouse subdomain coding table is... ,but Formula ⑥ is:

[0119]

[0120] in, : The complete data record vector written to the temporary record of the warehouse entry is constructed by formula ⑥. It is a structured data object containing six fields: part number, batch information, electrostatic sensitivity classification, humidity sensitivity level MSL, isolation inspection mark and target warehouse area subdomain code. It is derived from the aggregation of output fields of each stage of the S100 process.

[0121] The part number field is a string variable, derived from the part number identifier extracted from the outer packaging label information or material master data;

[0122] The batch information field is a string variable, derived from the batch information identifier extracted from the outer packaging label information;

[0123] The electrostatic sensitivity grading field is a discrete categorical variable with a value range of [value range missing]. This is derived from the electrostatic sensitivity classification result determined by the classification mapping module based on the packaging type;

[0124] The humidity sensitivity level (MSL) field is an integer variable with a range of values. It originates from the MSL value after field conflict handling. of If manual verification is required, the MSL value from the outer packaging label information will be used; otherwise, the MSL value will be used.

[0125] The isolated inspection flag field is a Boolean variable with a range of values. , This indicates that the batch is currently in a quarantine pending inspection state. This indicates that the person is not currently in quarantine and awaiting testing.

[0126] Indicator function: evaluates the logical proposition within parentheses, returning a value if the proposition is true. Return when the proposition is false. .

[0127] The data source mapping relationship is as follows: extract the part number from the outer packaging label information or material master data and record it as... Extract batch information from the outer packaging label and record it as follows: The electrostatic sensitivity classification result from the classification mapping module is recorded as follows: The MSL value after field conflict handling is denoted as... From formula ④ Generate isolation inspection mark From formula ⑤ It is directly used as the last field of the record vector.

[0128] Formula ⑥ addresses the practical problem of aggregating and structuring all key fields generated throughout the S100 process—including original identification fields, hierarchical judgment fields, anomaly judgment fields, and decision output fields—into a complete temporary inbound record. This ensures that the subsequent S200 storage location allocation module can read the required input using a unified field structure. Simultaneously, if... If the isolated inspection information is generated, S200 will only perform storage space calculation in the list of free storage spaces corresponding to the isolated inspection subdomain.

[0129] The technical effects of this section are as follows: The conflict detection and marking link composed of formulas ① and ② can convert qualitative field differences into quantitative conflict level codes and synchronously write them into the inventory data table. The parallel decision structure composed of formulas ③ and ④ can simultaneously handle two logical paths: normal attribute matching and abnormal field short-circuiting, and share the same output interface. The decision output chain formed by formulas ⑤ and ⑥ ensures that regardless of Regardless of the value, S100 outputs a uniformly structured temporary record for data entry. The data can be directly read by the S200 storage location allocation module. This data conversion and recording method is different from the ordinary barcode recognition system that only outputs material identification.

[0130] S200: Based on the target storage area subdomain code, obtain the list of available storage locations and storage location status data, calculate the recommended storage location number according to the correspondence between batch expiration information or workshop life status and the ease of access to storage locations, and generate a shelf placement instruction.

[0131] In this embodiment, S200 is executed by the storage location allocation module. The storage location allocation module receives the target storage area subdomain code, material number, batch information, humidity sensitivity level (MSL), sealing identifier, and isolation inspection information generated in S100; simultaneously, it reads the list of available storage locations and storage location status data from the inventory data table. The list of available storage locations includes multiple storage location numbers and their occupancy status corresponding to the target storage area subdomain code; the storage location status data includes the storage location number, storage area subdomain code, storage location level, storage location depth, distance from the outlet, adjacent storage location numbers, and storage location accessibility.

[0132] The ease of access to storage locations is a sorting field configured by the warehouse management system for storage location numbers, indicating the order in which storage locations within the same sub-domain are accessed by retrieval and placement operations. In one implementation, the ease of access is calculated based on the storage location depth, distance from the exit gate, and storage location level; storage locations with a deeper depth, shorter distance from the exit gate, and closer to the operation level have a higher ease of access ranking. In another implementation, the ease of access is pre-maintained in the storage location status data by the warehouse management system, and the storage location allocation module directly reads this field.

[0133] The storage location allocation module filters candidate storage locations based on the target storage area subdomain code. Specifically, the storage location allocation module matches the storage area subdomain codes in the list of available storage locations with the target storage area subdomain codes generated in S100. Storage location numbers that match and are in an available occupancy status are added to the candidate storage location set. When S100 generates isolation inspection information, the storage location allocation module only retains the available storage location numbers in the isolation inspection subdomain. If the candidate storage location set is empty, the storage location allocation module generates allocation information and writes the allocation information into the temporary storage record. The arrived semiconductor materials enter the allocation queue, waiting for the available storage location list to be updated before re-executing S200.

[0134] After the candidate storage location set is formed, the storage location allocation module reads existing storage locations with the same material number or batch. These existing storage locations with the same material number or batch come from the batch storage location binding records in the inventory data table that have not yet been shipped. The storage location allocation module retrieves existing storage location numbers based on the material number and batch information, and then determines adjacent candidate storage locations based on the adjacent storage location numbers in the storage location status data. When adjacent candidate storage locations exist, the storage location allocation module prioritizes sorting among them; when no adjacent candidate storage locations exist, the storage location allocation module sorts the candidate storage location set and writes the case of no adjacent candidate storage locations into the put-away instruction remarks field.

[0135] The batch expiration information can be derived from the expiration field of the outer packaging label information, supplier incoming material data, or inventory data table; the workshop life status indicates whether the batch currently has an opening timestamp, whether a workshop life expiration time has been generated, and the remaining workshop life status range. In stage S200, when the arrived semiconductor material is already in an opened state and has an opening timestamp, the storage location allocation module can first form a temporary workshop life status according to the workshop life rules corresponding to the humidity sensitivity level MSL; this temporary workshop life status participates in the recommended storage location number sorting, and in S300 it is then written into the formal batch storage location binding record.

[0136] The storage location allocation module calculates recommended storage location numbers based on the correspondence between batch expiration information or workshop life status and storage location accessibility. Specifically, for multiple candidate storage locations under the same target storage area subdomain code, the module assigns batches with earlier expiration dates or shorter remaining workshop life to storage location numbers ranked higher in accessibility; for unopened batches with later expiration dates, the module assigns them to storage location numbers ranked lower in accessibility. If multiple batches exist in the same warehousing task, the module sorts the batches according to their expiration dates or temporary workshop life status, then sorts the storage locations according to their accessibility, and generates recommended storage location numbers based on the sorted positions.

[0137] In one implementation, the storage location allocation module also reads the environmental monitoring sensor coverage relationship from the storage location status data. If an environmental anomaly warning tag exists in the sub-domain of a candidate storage location, the storage location allocation module excludes that candidate storage location from the current candidate storage location set and generates an environmental anomaly storage location exclusion record. If the remaining candidate storage locations in the same target sub-domain are insufficient to complete the current storage task, the storage location allocation module generates allocation information and retains the calculated recommended storage location numbers.

[0138] In one implementation of the semiconductor inventory warehouse, the target storage area subdomain code output by S100 corresponds to the drying cabinet reinforcement subdomain. The storage location allocation module reads the available storage locations A01, A02, A05, and A06 in this subdomain. Among them, A01 and A02 are closer to the outlet and are ranked higher in terms of ease of access. If the expiration date of the arriving batch B-01 is earlier than that of batch B-02, the storage location allocation module assigns B-01 to A01 and B-02 to A02. If there is a batch B-00 with the same part number in the inventory data table located in A03, and A02 and A03 are adjacent storage locations, the storage location allocation module lists A02 as a priority candidate storage location and generates a recommended storage location number that includes A02.

[0139] The put-away instruction output by S200 includes the part number, batch information, target storage area subdomain code, recommended storage location number, storage location accessibility ranking value, adjacent descriptions of the same part number or batch, and information to be allocated. The put-away instruction is sent to the warehouse terminal or control module. Upon receiving the instruction, the warehouse terminal generates a put-away task. After the put-away task is completed, the warehouse terminal returns put-away feedback, which is then input into S300 as the input for establishing a batch storage location binding record.

[0140] S300. Based on the put-away instruction and put-away feedback, establish a batch storage location binding record, recording the storage location number, humidity sensitivity level (MSL), opening mark, and workshop lifespan end time.

[0141] In this embodiment, S300 is executed by the batch binding module. The batch binding module receives the put-away instruction output by S200 and the put-away feedback returned by the warehouse terminal. The put-away feedback includes the actual put-away storage location number, put-away time, executor identifier or equipment identifier, and put-away completion status; when the warehouse terminal finds that the recommended storage location number is inconsistent with the actual put-away storage location number, the put-away feedback also includes a deviation reason field. The batch binding module matches the put-away instruction with the put-away feedback, and the matching fields include the material number, batch information, target warehouse area subdomain code, and recommended storage location number.

[0142] The batch storage location binding record is a record in the inventory data table indexed by both batch information and storage location number. The batch storage location binding record includes batch information, target storage area subdomain code, recommended storage location number, actual shelving storage location number, warehousing time, moisture sensitivity level (MSL), sealing identifier, opening identifier, opening timestamp, workshop lifespan expiration time, and warning status. If the recommended storage location number matches the actual shelving storage location number, the batch binding module writes the recommended storage location number as the storage location number into the batch storage location binding record; if they do not match, the batch binding module writes the actual shelving storage location number into the storage location number field and writes the recommended storage location number and deviation reason field into the data update record.

[0143] The batch binding module generates a workshop lifespan expiration time based on the opening identifier. When the opening identifier indicates that the package has been opened, the batch binding module reads the opening timestamp and the workshop lifespan rule corresponding to the moisture sensitivity level (MSL), and calculates the workshop lifespan expiration time. This workshop lifespan rule can be stored in a workshop lifespan rule table within the warehouse management system. The workshop lifespan rule table is indexed by the moisture sensitivity level (MSL) and records the corresponding workshop lifespan duration and workshop lifespan checkpoints. When the opening identifier indicates that the package has not been opened, the batch binding module records a sealing identifier in the batch storage location binding record and sets the workshop lifespan expiration time field to null or an inactive state.

[0144] In one implementation, the opening timestamp originates from the receiving terminal, outer packaging label information, or return records. If an opening identifier indicates that the package has been opened but the opening timestamp is missing, the batch binding module does not calculate the workshop lifespan expiration time, but instead generates an opening timestamp missing marker. This missing timestamp marker is written into the batch storage location binding record, and the batch is added to the manual review queue. After review, the batch binding module recalculates the workshop lifespan expiration time based on the reviewed opening timestamp and updates the batch storage location binding record.

[0145] The batch binding module also performs consistency checks on the storage location number based on the target storage area subdomain code. Specifically, the batch binding module reads the storage area subdomain code corresponding to the storage location number in the storage location status data and compares it with the target storage area subdomain code in the putaway instruction. When they match, the batch binding module writes the record to the formal inventory data table; when they do not match, the batch binding module generates a storage location subdomain inconsistency flag and sets the batch storage location binding record to a pending review status. Batches in the pending review status do not enter the candidate batch range for outbound picking tasks.

[0146] In one implementation, the batch binding module synchronously updates the storage location status data based on the batch storage location binding record. The occupancy status in the storage location status data is updated from idle to occupied; the material number and batch information in the storage location status data are written to the corresponding fields; if the batch has an environmental anomaly warning tag or an overdue lock status, the storage location status data also records the corresponding status reference. This status reference is invoked during S400 when updating the environmental anomaly warning tag and overdue lock status.

[0147] In one implementation of a semiconductor incoming material warehouse, the recommended storage location number in the shelving instruction is D-03. The shelving feedback returned by the warehouse terminal shows that the material has been shelved to D-03 at 10:30 AM on June 24, 2026. The batch binding module reads that the moisture sensitivity level MSL for this batch is 3, the opening identifier is "opened," and the opening timestamp is 9:00 AM on June 24, 2026. The batch binding module reads the workshop lifespan corresponding to MSL3 from the workshop lifespan rule table, generates the workshop lifespan expiration time, and writes it to the inventory data table. If the opening timestamp of the same batch is changed after manual review, the batch binding module recalculates the workshop lifespan expiration time and retains the record time before the change and the field value after the change.

[0148] The batch storage location binding record generated in S300 is entered into S400. S400 queries multiple batch storage location binding records within the same storage area subdomain using the target storage area subdomain code; compares the current time using the workshop lifespan expiration time; and locates the storage location sequence involved in the outbound picking task using the storage location number. The batch storage location binding record serves as a common index in the subsequent generation of environmental anomaly warning tags, priority picking status, and overdue lockout status.

[0149] S400. Based on the batch storage location binding record, compare the environmental monitoring sensor readings with the environmental threshold corresponding to the target storage area subdomain code, and query the batch storage location binding record within the same storage area subdomain to generate an environmental anomaly warning label, priority picking status, or overdue lock status.

[0150] In this embodiment, S400 is executed by the environmental monitoring module and the timing and early warning module. The environmental monitoring module receives readings uploaded by the environmental monitoring sensors; the environmental monitoring sensor readings include temperature, humidity, acquisition time, and sensor identification. The environmental monitoring module queries the warehouse area subdomain code to which the sensor belongs based on the sensor identification, and then calls the environmental threshold corresponding to that warehouse area subdomain code. The environmental threshold is maintained by the warehouse management system and includes an upper temperature limit, a lower temperature limit, an upper humidity limit, and a valid reading time.

[0151] The environmental monitoring module compares temperature or humidity with environmental thresholds. When temperature or humidity exceeds the environmental threshold, the module queries the inventory data table for batch storage location binding records within the same storage area, using the sensor's storage area subdomain code as the query condition. These batch storage location binding records within the same storage area subdomain include batches that have not been shipped out, moved, or are not in a return inspection state. The environmental monitoring module updates the environmental anomaly warning label for the retrieved batch storage location binding records and records the reading value, acquisition time, sensor identifier, and environmental threshold version.

[0152] In one implementation, the environmental monitoring module verifies the validity of environmental monitoring sensor readings. If the same sensor fails to upload readings for multiple consecutive acquisition cycles, the environmental monitoring module generates a sensor reading missing marker and writes this marker into the reservoir sub-domain status record. If the temperature or humidity reading exceeds the sensor's range, the environmental monitoring module generates a reading anomaly marker and retains the original reading field. For reservoir sub-domains with reading missing or anomaly markers, the environmental monitoring module does not generate an environmental anomaly warning label but instead generates environmental data verification information. After verification, the environmental monitoring module updates the reservoir sub-domain status record based on the verification results.

[0153] The timing warning module generates a priority picking status or an overdue lock status based on the workshop lifespan expiration time in the batch storage location binding record. Specifically, the timing warning module reads batch storage location binding records in the inventory data table where the workshop lifespan expiration time is not empty according to a preset inspection cycle; it compares the current time with the workshop lifespan expiration time; when the remaining workshop lifespan reaches the workshop lifespan inspection point, the timing warning module generates a priority picking status and writes it to the batch storage location binding record; when the current time exceeds the workshop lifespan expiration time, the timing warning module generates an overdue lock status and outputs a transfer baking work order or a return inspection work order.

[0154] The workshop life checkpoints can be configured using a workshop life rule table. In one implementation, the workshop life checkpoint is represented by the remaining duration; in another implementation, it is represented by the remaining percentage. When the timing warning module calls the workshop life rule table, it reads the workshop life checkpoint corresponding to the humidity sensitivity level MSL and compares it with the opening timestamp and workshop life expiration time in the batch storage location binding record. If the workshop life rule table is updated, the timing warning module writes the rule version number into the batch storage location binding record, and subsequent comparisons are performed according to the recorded rule version number.

[0155] When the same batch simultaneously has both an environmental anomaly warning tag and a priority picking status, the timing warning module writes both statuses into the status field of the batch storage location binding record. When the same batch is already in an overdue lockout state, the environmental monitoring module can still update the environmental anomaly warning tag, but when the outbound picking task reads this batch, the overdue lockout status is used as the input for the picking verification result. If the batch is in the return inspection work order execution state, the timing warning module will not generate a new priority picking status, but will instead write the current time comparison result into the data update record.

[0156] In one implementation of semiconductor warehousing, the upper limit of humidity in the environmental threshold corresponding to the enhanced sub-domain of the drying cabinet is a preset value. Environmental monitoring sensors upload humidity readings during the acquisition period, and the environmental monitoring module compares these readings with the upper limit. When the reading exceeds the upper limit, the environmental monitoring module queries the batch storage location binding record of the target storage area sub-domain code corresponding to the enhanced sub-domain of the drying cabinet, and writes environmental anomaly warning tags to multiple batches obtained from the query. Simultaneously, the timing warning module reads the workshop lifespan expiration time of one of the opened batches. If the remaining workshop lifespan reaches the workshop lifespan checkpoint, the timing warning module writes a priority picking status; if the current time exceeds the workshop lifespan expiration time, the timing warning module writes an overdue lock status and outputs a transfer baking work order.

[0157] The environmental anomaly warning tag, priority picking status, overdue lock status, transfer baking work order, and return inspection work order generated by S400 are all associated with the batch storage location binding record. When the outbound verification module receives the outbound picking task in S500, it reads the status field from the batch storage location binding record; when the batch is in an overdue lock status, the outbound verification module records the lock status in the picking verification result; when the batch is in a priority picking status, the outbound verification module records the priority picking status in the picking verification result. The environmental anomaly warning tag is also included in the picking verification result as a status field in the outbound picking task.

[0158] In one specific embodiment:

[0159] S400 is executed by the environmental monitoring module and the timing early warning module. It inherits the batch storage location binding records, target storage area subdomain codes, and environmental threshold and workshop life rule tables maintained in the warehouse management system generated by S300. The environmental monitoring module receives readings uploaded by environmental monitoring sensors, which include temperature, humidity, acquisition time, and sensor identification. The environmental monitoring module queries the storage area subdomain code to which the sensor belongs based on the sensor identification, and then calls the environmental threshold corresponding to that storage area subdomain code. The environmental threshold includes the upper limit of temperature, the lower limit of temperature, the upper limit of humidity, and the effective time of the reading.

[0160] The environmental monitoring module compares temperature or humidity with environmental thresholds. When the temperature or humidity exceeds the environmental threshold, it is necessary to associate the environmental anomaly reflected by the sensor reading with all valid batch storage location binding records within the same storage area sub-domain.

[0161] In order to quantify the multidimensional deviation between sensor readings and environmental thresholds into an environmental anomaly intensity index that can be uniformly used in subsequent batch status determinations, this step constructs the following environmental reading deviation measurement and threshold severity scoring mechanism.

[0162] Formula ⑦ combines temperature and humidity deviations according to their respective normalized scales to form an environmental anomaly intensity index. This index comprehensively reflects the overall deviation of the current sensor readings from the environmental threshold of the reservoir sub-region. Formula ⑧, based on this, introduces a time decay factor to calculate the severity score of the current reading exceeding the threshold, giving higher weight to recently occurring environmental anomalies. Formula ⑦ is:

[0163]

[0164] in, The environmental anomaly intensity index is a non-negative real number calculated by formula ⑦. It is used to comprehensively reflect the overall deviation of the current environmental monitoring sensor readings from the environmental threshold of the reservoir sub-area in three dimensions: high temperature, low temperature, and high humidity. The value range is non-negative real numbers.

[0165] The temperature readings currently uploaded by the environmental monitoring sensors originate from the temperature measurement channel of the sensors, and the range of values ​​is determined by the sensor's measurement range.

[0166] The upper limit of the temperature in the environmental threshold corresponding to the warehouse sub-domain to which the sensor belongs is derived from the environmental threshold table maintained by the warehouse management system, and the value range is real numbers;

[0167] The normalized tolerance width for the upper temperature limit is provided by the environmental threshold configuration parameter of the warehouse management system, and is a fixed value. ;

[0168] Indicator function: evaluates the logical proposition within parentheses, returning a value if the proposition is true. Return when the proposition is false. ;

[0169] The lower limit of the environmental threshold value corresponding to the sub-domain of the reservoir to which the sensor belongs is derived from the environmental threshold table, and the value range is real numbers;

[0170] The normalized tolerance width of the temperature limit is provided by the environmental threshold configuration parameter and is a fixed value. This is used to make the temperature deviation dimensionless;

[0171] The humidity readings currently uploaded by the environmental monitoring sensors originate from the humidity measurement channel of the sensors, and the value range is determined by the sensor's measurement range.

[0172] The upper limit of humidity in the environmental threshold corresponding to the sub-domain of the reservoir to which the sensor belongs is derived from the environmental threshold table, and the value range is real numbers;

[0173] : Normalized tolerance width of the upper limit of humidity.

[0174] The data source mapping relationship is as follows: temperature readings extracted from environmental monitoring sensors and recorded as... The humidity readings from the environmental monitoring sensors are extracted and recorded as... The upper temperature limit is read from the environmental threshold table. Lower limit of temperature , upper limit of humidity Read from environmental threshold configuration parameters , , The above items together form the formula in ⑦. .

[0175] Formula ⑦ addresses the practical problem of mapping the deviations of three different physical quantities—higher temperature, lower temperature, and higher humidity—to the same numerical scale, enabling subsequent steps to determine whether the current environmental reading needs to trigger a batch-level status update based on a single indicator.

[0176] Formula ⑧ is:

[0177]

[0178] in, The severity score for exceeding the threshold is a non-negative real number calculated by formula ⑧, representing the effective severity of the current environmental reading anomaly after time decay, and its value range is non-negative real numbers;

[0179] : Natural exponential function, with natural constant Exponential operations with base 0;

[0180] The time decay coefficient is a fixed value provided by the environmental event decay parameter configuration of the warehouse management system. This is used to control the decay rate of the impact of earlier environmental anomalies on the current state determination;

[0181] The current timestamp of the system executing the current judgment is derived from the system clock of the warehouse management system, and its value range is positive integer;

[0182] The acquisition time of the environmental monitoring sensor readings comes from the acquisition time field uploaded by the sensor, and the value range is positive integer;

[0183] Time difference: This refers to the time elapsed from the moment the sensor reading is collected to the current determination time.

[0184] The data source mapping relationship is obtained from formula ⑦. As input to formula ⑧, the acquisition time is extracted from the sensor readings. The current time is obtained from the system clock. Read from the environmental event decay parameter configuration Together they form the formula in ⑧ .

[0185] Formula ⑧ addresses the practical problem of introducing a time decay factor to gradually reduce the impact of earlier environmental anomalies on the current state determination over time, thus avoiding unnecessary warnings during subsequent outbound verifications caused by the sensor readings retaining the same severity score for an extended period after returning to normal.

[0186] when and Greater than the preset environmental event trigger threshold When the environmental monitoring module determines that a valid environmental anomaly event exists, it proceeds to the subsequent batch status update process; the environmental anomaly intensity index obtained from formula ⑦... As the first-level basis for the environmental monitoring module to determine whether an environmental anomaly exists, the severity score of exceeding the threshold obtained from Formula ⑧ is used. As the second layer of evidence used by the environmental monitoring module to determine whether environmental anomalies are still timely, the two together control the conditions for generating environmental anomaly warning labels.

[0187] After the environmental monitoring module determines that there is a valid environmental anomaly, it uses the subdomain code of the storage area to which the sensor belongs as the query condition to query the batch storage location binding records in the inventory data table within the same storage area subdomain. The batch storage location binding records within the same storage area subdomain include batch records that have not been shipped out, have not been moved, and are not in the return inspection state.

[0188] The environmental monitoring module performs validity checks when reading sensor readings. If the same sensor fails to upload readings for multiple consecutive acquisition cycles, the environmental monitoring module generates a sensor reading missing marker and writes this marker into the reservoir sub-domain status record. If the temperature or humidity reading exceeds the sensor's range, the environmental monitoring module generates a reading anomaly marker and retains the original reading field. For reservoir sub-domains with reading missing or anomaly markers, the environmental monitoring module does not generate an environmental anomaly warning label but instead generates environmental data verification information. After verification, the environmental monitoring module updates the reservoir sub-domain status record based on the verification results.

[0189] In order to aggregate the environmental anomaly intensity index and the severity score of exceeding the threshold into a status field value that can be uniformly written to each batch record when multiple valid environmental anomalies simultaneously affect multiple batch storage location binding records in the same storage area subdomain, and to introduce status priority coding to handle the situation where multiple anomaly states may exist simultaneously in the same batch, this step constructs the following batch status batch update and status superposition arbitration mechanism.

[0190] Formula 9 weights and fuses the severity scores of exceeding the threshold corresponding to all valid sensor readings within the same reservoir sub-domain according to sensor identifiers to generate a current environmental anomaly aggregate score for that sub-domain; Formula 10 generates a composite state vector containing environmental anomaly warning labels and state priority codes based on this aggregate score and a preset state threshold range. Formula 9 is:

[0191]

[0192] in The current query is for the subdomain code index of the library area, with a value range of 1. These correspond to the regular shelf sub-domain, the standard drying cabinet sub-domain, the reinforced drying cabinet sub-domain, and the isolated inspection sub-domain, respectively.

[0193] : No. The aggregated environmental anomaly score for each reservoir sub-domain is a non-negative real number calculated by formula ⑨, representing the comprehensive degree of environmental anomaly of all valid sensor readings within that sub-domain, and its value range is non-negative real numbers.

[0194] : No. The total number of sensors currently uploading valid readings within each reservoir sub-domain is derived from the statistical results obtained by the environmental monitoring module after querying the reservoir sub-domain code to which the sensor belongs based on the sensor identifier, and the value range is positive integer;

[0195] : The summation index variable, representing the index of the first index. The sensor serial number within each reservoir sub-domain, with a value range of [value range missing]. ;

[0196] : No. The confidence weights of each sensor are given by the formula. The calculated range is: This is used to adjust the contribution of the sensor's readings to the aggregate score based on the sensor's historical drift.

[0197] : No. The historical drift coefficient of each sensor is derived from the historical calibration records of the sensor recorded by the environmental monitoring module. The value range is non-negative real number. The larger the value, the greater the degree to which the historical measurement value of the sensor deviates from the standard reference value.

[0198] : No. The severity score of exceeding the threshold for the current reading of each sensor is calculated by formula ⑧, and the value range is non-negative real numbers.

[0199] The data source mapping relationship is as follows: the environmental monitoring module statistically analyzes the data of the [number]th [item]. The number of sensors that upload valid readings within each subdomain is denoted as The severity score of each sensor exceeding the threshold is calculated using formula ⑧ and recorded as follows: The historical drift coefficients of each sensor are read from the historical calibration records and recorded as follows: .

[0200] Formula 9 addresses the practical problem that when multiple environmental monitoring sensors are installed within the same sub-region of a reservoir, the readings of different sensors may differ. By weighting and averaging the readings of each sensor according to its historical drift coefficient, a unified environmental anomaly aggregate score for the sub-region can be obtained, thus avoiding frequent erroneous updates to the batch status caused by fluctuations in the readings of a single sensor.

[0201] Formula 10 is:

[0202]

[0203] in, : No. The batch status update vector for each subdomain of the storage area is calculated using formula ⑩, and is derived from the environmental anomaly warning label component. and state priority coding components composition;

[0204] : Environmental anomaly warning label, Boolean variable, range of values ​​is , This indicates that there is currently an environmental anomaly within the subdomain of this storage area, and an environmental anomaly warning tag needs to be written to all batch storage location binding records obtained from the query. This indicates that there are no environmental anomalies;

[0205] The environmental anomaly warning trigger threshold is provided by the environmental event policy table of the warehouse management system and is a fixed value. It is used to determine whether the aggregated score of environmental anomalies has reached the level that requires triggering an early warning;

[0206] : Status priority code, a non-negative integer calculated by formula ⑩, represents the level and urgency of the current environmental anomaly in this subdomain, and is used for status priority determination during subsequent outbound verification;

[0207] The floor function rounds down the real number in parentheses and returns the largest integer not exceeding that real number.

[0208] The threshold for locking out events after the expiration date is provided by the environmental event policy table and is a fixed value. It is used to determine whether the aggregated score of environmental anomalies has reached the level that requires associated overdue lockout status processing;

[0209] Prioritize the selection of related thresholds, which are provided by the environmental event policy table and are fixed values. It is used to determine whether the aggregated score of environmental anomalies has reached the level that requires associated priority picking status processing;

[0210] The bitwise XOR operator performs a bitwise XOR operation on the binary representations of two integers. In this expression, it is used to... and Two integer values ​​are combined to form a single state priority code.

[0211] The data source mapping relationship is obtained from formula ⑨. It can be directly used as input for formula 10; , , Read from the environment event policy table.

[0212] Formula 10 addresses the practical problem of discretizing the aggregated score of continuous environmental anomalies into a structured status field, and generating a single priority code by bitwise XOR encoding of different threshold trigger states, so that the subsequent outbound verification module can read and adjudicate the batch status in a unified manner.

[0213] The timing warning module executes concurrently with the environmental monitoring module, generating either a priority picking status or an overdue lock status based on the workshop lifespan expiration time in the batch storage location binding record. The timing warning module reads batch storage location binding records in the inventory data table where the workshop lifespan expiration time is not empty according to a preset inspection cycle, and compares the current time with the workshop lifespan expiration time.

[0214] The workshop lifespan rule table is indexed by the humidity sensitivity level (MSL) and records the corresponding workshop lifespan duration and checkpoints. Workshop lifespan checkpoints are represented by remaining duration or remaining percentage and are maintained by the warehouse management system. To convert the difference between the current time and the workshop lifespan expiration time into a unified workshop lifespan status determination result, and to support a freezing mechanism that allows different batches to retain their respective record version numbers after a workshop lifespan rule table version change, this step constructs the following workshop lifespan status determination and rule version freezing mechanism.

[0215] Formula 11 calculates the remaining workshop life ratio and remaining workshop life duration of the current batch and determines its checkpoint status; Formula 12 encapsulates the determination result and rule version number into a workshop life status record, which is used to write back the batch storage location binding record. Formula 11 is:

[0216]

[0217] in, : The index number of the currently determined batch storage location binding record, with a value range of . ,in The total number of batch storage locations bound to records where the workshop lifespan expiration time is not empty;

[0218] : No. The remaining workshop life ratio for each batch is calculated using formula ⑪, taking values ​​that are real numbers and greater than 100%. This indicates that the workshop's lifespan has not yet expired, and is less than or equal to... This indicates that the workshop's lifespan has been exhausted;

[0219] : No. The workshop lifespan expiration time for each batch is derived from the workshop lifespan expiration time field in the batch storage location binding record, and the value range is positive integer.

[0220] The current timestamp of the system executing the current judgment is derived from the system clock of the warehouse management system, and its value range is positive integer;

[0221] : No. The workshop life start time benchmark for each batch, i.e., the opening timestamp, is derived from the opening timestamp field in the batch storage location binding record, and its value range is positive integer.

[0222] : No. The opening timestamps of each batch, and For the same field value, the range of values ​​is positive integers;

[0223] : No. The workshop life status code for each batch is obtained through segmented determination, with a value range of [value range missing]. ,in This indicates an expired lockout status. Indicates priority picking status. Indicates a normal state;

[0224] : No. The priority pick-out checkpoint threshold for each batch is derived from the workshop life checkpoint configuration corresponding to the humidity sensitivity level MSL in the workshop life rule table, and its value range is [value range missing]. It is used to define the remaining lifetime ratio boundary between the normal state and the priority picking state;

[0225] : No. The threshold separating the normal state from the priority picking state of each batch is given by the formula. The calculated range is: ;

[0226] : No. The absolute time value of the normal state checkpoint in the workshop life rule table corresponding to each batch is derived from the workshop life rule table, and the value range is positive integer.

[0227] The data source mapping relationship is as follows: the workshop lifespan expiration time is read from the batch storage location binding record and denoted as... Read the Kaifeng timestamp as (At the same time as) The current time is obtained from the system clock and recorded as follows: The priority pick-out checkpoint threshold corresponding to the humidity sensitivity level (MSL) is read from the workshop life rule table and recorded as follows: The absolute time value of the normal state checkpoint is recorded as follows. .

[0228] Formula 11 addresses the practical problem of converting the absolute difference between the end time of the workshop life and the current time into the remaining life ratio based on the opening time. This allows batches with different MSL levels (with different total workshop life durations) to be compared and their status determined on the same scale. At the same time, it directly outputs the status code through a piecewise function, avoiding repeated conditional judgments in the timing warning module.

[0229] Formula 12 is:

[0230]

[0231] in, : No. The batch of workshop life status re-entry records is constructed using formula ⑫, and is derived from status codes. Status change flag and rule version number It consists of three components, used for writing back to the batch storage location binding record;

[0232] : State change flag, generated by the bitwise XOR operator For the current status code Compared with historical status codes The result of performing an XOR operation is an integer variable. This indicates that the state has not changed. This indicates a change in status;

[0233] : No. The historical status code of each batch from the previous inspection cycle is derived from the historical value of the status field in the batch storage location binding record, and the value range is [value range missing]. ;

[0234] : The rule version number of the batch storage location binding record is used for refilling. When the status changes, the version number of the current workshop lifespan rule table is used. When the status remains unchanged, the historical rule version number is retained. The version number field, derived from the version number field of the workshop life rule table or the rule version number field of the batch storage location binding record, is a string or integer identifier.

[0235] : The current version number of the workshop life rule table in the warehouse management system when the current judgment is executed. It comes from the version management field of the workshop life rule table and is a string or integer identifier.

[0236] The rule version number recorded in this batch of storage location binding records comes from the rule version number field of the batch storage location binding record and is a string or integer identifier.

[0237] The data source mapping relationship is obtained from formula 11. As input to formula ⑫; read the historical status code from the batch storage location binding record and record it as... The historical rule version number is recorded as The current version number is read from the workshop lifespan rule table and recorded as follows: .

[0238] Formula 12 addresses the practical problem of comparing the current status code with historical status codes and updating the rule version number only when the status changes. This ensures that the rule version number written to the batch storage location binding record remains unchanged when the status does not change, thus achieving a "rule version number is fixed with the batch" freezing mechanism. When the same batch has both an environmental anomaly warning tag and a priority picking status, the environmental monitoring module and the timing warning module independently write their respective status fields, ultimately coexisting in the batch storage location binding record as status components superimposed.

[0239] The technical effects of this section are as follows: By cascading calculations of environmental reading deviation measurement and severity scoring for exceeding thresholds, physical deviations of three different dimensions—high temperature, low temperature, and high humidity—are transformed into a unified environmental anomaly intensity index and timeliness score, enabling environmental anomaly judgment to simultaneously possess physical deviation measurement capabilities and time sensitivity. Through batch status update and status overlay arbitration mechanisms, the weighted fusion scores of multiple sensors within the same storage area subdomain are discretized into structured status vectors, enabling batch status writing of all valid batch storage location binding records within the same subdomain. Through workshop lifespan status determination and rule version freezing mechanisms, the difference between the current time and the workshop lifespan expiration time is transformed into the remaining lifespan ratio and segmented status codes, ensuring that the rule version number is updated only when the status changes and remains unchanged when the status does not change. This allows batches of different MSL levels to complete status determination on a unified scale and solidify their respective execution standard versions. This technical link differs from the approach of ordinary environmental alarm systems that only output global alarms without associating batch-level inventory status.

[0240] S500: When receiving an outbound picking task, determine the route area based on the storage location sequence, and generate picking verification results and an anti-static operation item list according to the electrostatic sensitivity attributes corresponding to the route area.

[0241] In this embodiment, S500 is executed by the outbound verification module and can be jointly written into the inventory data table record with the return re-judgment module. The outbound verification module receives outbound picking tasks; the outbound picking task includes picking task identifier, material number, batch information, outbound quantity, storage location sequence, and outbound time. The storage location sequence is generated by the warehouse management system based on batch storage location binding records and includes one or more storage location numbers and their retrieval and placement order. The outbound verification module queries the storage location status data based on the storage location sequence to obtain the storage area subdomain code and route area corresponding to each storage location number.

[0242] The transit area refers to the storage area or passageway area traversed from the operation start position to each storage location number in the storage location sequence. The transit area can be generated by a region mapping table in the warehouse management system; the region mapping table records the storage location number, passage number, storage area subdomain code, grounding qualification identifier, and electrostatic sensitivity attribute. The outbound verification module matches each storage location number in the storage location sequence with the region mapping table to obtain a transit area set; then it reads the electrostatic sensitivity attribute and grounding qualification identifier from the transit area set to generate the picking verification result.

[0243] The electrostatic sensitivity attribute is derived from the electrostatic sensitivity classification and target warehouse area subdomain code formed in S100. For outbound picking tasks that pass through areas containing high electrostatic sensitivity subdomains, the outbound verification module generates an anti-static operation item list; the anti-static operation item list includes several categories of operation items such as anti-static wrist straps, conductive trays, and prohibition of bare-hand contact. In one embodiment, the anti-static operation item list is generated by an operation item configuration table; the operation item configuration table uses electrostatic sensitivity attributes and warehouse area subdomain codes as indexes to record the corresponding operation item names and display order. The outbound verification module writes the anti-static operation item list into the picking order.

[0244] When the grounding qualification indicator in the transit area does not meet the requirements, the outbound verification module records the grounding qualification indicator as abnormal in the picking verification result and marks the outbound picking task as pending review. If an alternative storage location sequence exists, the warehouse management system can regenerate the storage location sequence and execute S500 again; if no alternative storage location sequence exists, the outbound verification module retains the pending review status and writes the grounding qualification indicator as abnormal into the data update record. The pending review status does not change the batch quantity field in the batch storage location binding record.

[0245] The outbound verification module also reads the environmental anomaly warning tag, priority picking status, and overdue lock status generated by the S400. If the batch storage location binding record has an overdue lock status, the outbound verification module records the overdue lock in the picking verification result and excludes the batch from the current normal outbound picking task; if the batch storage location binding record has a priority picking status, the outbound verification module records priority picking in the picking verification result. If the batch storage location binding record has an environmental anomaly warning tag, the outbound verification module writes the environmental anomaly warning tag into the status field of the picking order and outputs it together with the anti-static operation item list.

[0246] In one implementation of a semiconductor warehouse, the outbound picking task includes storage location sequences D-03, D-04, and E-01. The outbound verification module queries the area mapping table to find that D-03 and D-04 are located in the reinforced drying cabinet sub-domain, and E-01 is located in the regular shelf sub-domain; D-03 and D-04 correspond to high electrostatic discharge (ESD) sensitive sub-domains, and the grounding qualification markers in the areas they pass through are qualified. The outbound verification module generates an ESD protection operation item list based on the high ESD sensitive sub-domains and writes it into the picking list; simultaneously, it reads the priority picking status from the storage location binding record of the batch corresponding to D-03 and writes this status into the picking verification result. If the batch corresponding to E-01 has an overdue lock status, the outbound verification module excludes the batch corresponding to E-01 from the normal picking output and records the overdue lock field.

[0247] In one implementation, S500 further includes the re-entry processing of returned or transferred materials. Upon receiving a re-entry request for returned or transferred materials, the return-to-warehouse re-determination module rereads the packaging integrity and humidity indication status. The re-entry request includes the material number, batch information, original storage location number, and re-entry time. If the packaging integrity indicates packaging damage or the humidity indication status indicates abnormal humidity, the return-to-warehouse re-determination module generates isolation inspection information and prevents the returned or transferred materials from returning to the normal storage location. If both packaging integrity and humidity indication status are normal, the return-to-warehouse re-determination module returns the reread fields to S100, where the hierarchical mapping module re-matches the target storage area subdomain code.

[0248] The return-to-stock re-judgment module writes back the status of the original batch storage location binding record. If isolation pending inspection information is generated, the return-to-stock re-judgment module updates the batch storage location binding record corresponding to the original storage location number to the moved-out or pending inspection status, and writes the isolation pending inspection information to a new inventory data table record. If the target storage area subdomain code changes after re-entry, the return-to-stock re-judgment module writes the original target storage area subdomain code, the re-matched target storage area subdomain code, and the re-entry time to the data update record. This data update record serves as the basis for status query in subsequent inbound, transfer, and outbound picking tasks.

[0249] The picking verification results output by S500 include picking task identifier, storage location sequence, route area, electrostatic sensitivity attribute, grounding qualification identifier, environmental anomaly warning label, priority picking status, and overdue lockout status. The anti-static operation item list is output to the warehouse terminal along with the picking order; the isolation inspection information is written to the inventory data table and entered into the hierarchical mapping input of S100 or the storage location allocation input of the isolation inspection subdomain. Through the above data flow, the electrostatic sensitivity classification and target storage area subdomain code generated by S100 are called again in S500, the batch status generated by S400 is read and recorded in S500, and the isolation inspection information generated by the return-to-warehouse re-judgment module is returned to the inventory data table for continued use in subsequent inbound and outbound processes.

[0250] Example 2: Figure 2 This diagram illustrates a structural block diagram of a graded storage and management system for electrostatic sensitive semiconductor materials according to an embodiment of the present invention. Figure 2 As shown, the structure may include:

[0251] The attribute recognition and classification mapping module 01 is used to receive barcode information or outer packaging label information of the semiconductor materials, identify the part number, batch information, package type, moisture sensitivity level (MSL), seal mark, packaging integrity, and humidity indication status, determine the electrostatic sensitivity classification based on the package type, and generate a target warehouse sub-domain code by matching the classification mapping configuration table. Specifically, the attribute recognition and classification mapping module receives barcode information or outer packaging label information from the receiving terminal, barcode reader, or outer packaging label input interface, parses the fields of the barcode information or outer packaging label information, and forms a material information record containing part number, batch information, package type, moisture sensitivity level (MSL), seal mark, packaging integrity, and humidity indication status. The attribute recognition and classification mapping module calls the correspondence between package type and electrostatic sensitivity classification, and matches exposed solder ball packages, tape and lead packages, or through-hole packages to the corresponding electrostatic sensitivity classifications. The grading mapping configuration table includes fields for electrostatic sensitivity grading, humidity sensitivity level (MSL), seal identification, packaging integrity, humidity indication status, and target storage area subdomain code. The attribute recognition and grading mapping module matches the electrostatic sensitivity grading, humidity sensitivity level (MSL), seal identification, packaging integrity, and humidity indication status with the grading mapping configuration table to generate a target storage area subdomain code. When the barcode information is incomplete, the humidity sensitivity level (MSL) is missing, the packaging integrity indicates damaged packaging, or the humidity indication status indicates abnormal humidity, the attribute recognition and grading mapping module generates isolation inspection information and writes it into the inventory data table record. The attribute recognition and grading mapping module provides the target storage area subdomain code, batch information, and material information record to the storage location allocation module, with the target storage area subdomain code serving as the input for the storage location candidate range.

[0252] The storage location allocation module 02, connected to the attribute recognition and hierarchical mapping module, is used to obtain a list of available storage locations and storage location status data based on the target storage area subdomain code, calculate recommended storage location numbers according to the correspondence between batch expiration information or workshop life status and storage location accessibility, and generate a shelving instruction. Specifically, the storage location allocation module receives the target storage area subdomain code, batch information, and material information records output by the attribute recognition and hierarchical mapping module, and reads the list of available storage locations and storage location status data corresponding to the target storage area subdomain code from the inventory data table. The storage location status data includes storage location number, storage area subdomain code, occupancy status, existing storage locations with the same material number, existing storage locations with the same batch, and storage location accessibility. The storage location allocation module filters candidate storage locations based on the target storage area subdomain code and, based on existing storage locations with the same material number or batch, selects recommended storage locations. The system determines adjacent candidate storage locations from the candidate storage locations; the storage location allocation module reads batch expiration information or workshop life status, sorts the batch expiration information or workshop life status with the accessibility of the storage locations, and obtains recommended storage location numbers; when the list of available storage locations corresponding to the target storage area subdomain code is empty, the storage location allocation module generates a pending allocation status record and retains the correspondence between the target storage area subdomain code and the batch information; when a candidate storage location has an environmental anomaly warning tag or an overdue lock status, the storage location allocation module excludes the corresponding storage location number from the candidate storage locations; the storage location allocation module generates a put-away instruction, which records batch information, target storage area subdomain code, recommended storage location number, and put-away status, and transmits the put-away instruction to the batch binding module.

[0253] Batch binding module 03, connected to the storage location allocation module, is used to establish a batch storage location binding record based on the put-away instruction and put-away feedback, recording the storage location number, humidity sensitivity level MSL, opening identifier, and workshop lifespan expiration time. Specifically, the batch binding module receives the put-away instruction output by the storage location allocation module and receives put-away feedback from the warehousing terminal or warehouse management system. The put-away feedback includes the actual put-away storage location number, put-away time, and put-away status. The batch binding module matches the recommended storage location number in the put-away instruction with the storage location number in the put-away feedback. When the match is consistent, a batch storage location binding record is established. The batch storage location binding record includes batch information, target storage area subdomain code, storage location number, storage time, humidity sensitivity level MSL, opening identifier, and workshop lifespan expiration time. When the seal identifier indicates that the package has been opened, the batch binding module reads the opening timestamp and the workshop life rule corresponding to the moisture sensitivity level MSL, calculates the workshop life expiration time, and writes the workshop life expiration time into the batch storage location binding record. When the storage location number in the shelving feedback is inconsistent with the recommended storage location number, the batch binding module generates a storage location difference record and writes the storage location difference record into the inventory data table. When the opening identifier indicates that the package has not been opened, the batch binding module records the sealing status and retains the correspondence between the moisture sensitivity level MSL and the batch information. The batch binding module provides the batch storage location binding record to the early warning status generation module, with the target storage area subdomain code, the storage location number, and the workshop life expiration time serving as input fields for the early warning status generation module.

[0254] The early warning status generation module 04, connected to the batch binding module, is used to compare environmental monitoring sensor readings with environmental thresholds corresponding to the target storage area subdomain code based on the batch storage location binding records, and query batch storage location binding records within the same storage area subdomain to generate environmental anomaly early warning tags, priority picking status, or overdue lockout status. Specifically, the early warning status generation module receives batch storage location binding records output by the batch binding module and receives temperature and humidity readings uploaded by environmental monitoring sensors. The environmental monitoring sensor readings carry the corresponding storage area subdomain code and acquisition time. The early warning status generation module calls the corresponding environmental threshold based on the storage area subdomain code and compares the temperature and humidity with the environmental threshold respectively. When the temperature or humidity exceeds the environmental threshold, the early warning status generation module, based on the target storage area subdomain code, generates an environmental anomaly early warning tag, priority picking status, or overdue lockout status. The domain code queries batch storage location binding records within the same subdomain of the warehouse area and updates the environmental anomaly warning label for the retrieved batch storage location binding records. The warning status generation module also compares the current time with the workshop lifespan expiration time. When the remaining workshop lifespan reaches the workshop lifespan checkpoint, a priority picking status is generated; when the current time exceeds the workshop lifespan expiration time, an overdue lock status is generated. When environmental monitoring sensor readings are missing or the acquisition time exceeds the acquisition cycle, the warning status generation module generates an environmental reading anomaly record and retains the original batch status. The environmental anomaly warning label, the priority picking status, and the overdue lock status are written into the corresponding batch storage location binding records. The warning status generation module provides the batch storage location binding records, the environmental anomaly warning label, the priority picking status, and the overdue lock status to the outbound verification module.

[0255] The outbound verification module 05, connected to the early warning status generation module, is used to determine the transit area based on the storage location sequence when receiving an outbound picking task, and generate picking verification results and an anti-static operation item list according to the electrostatic sensitivity attribute corresponding to the transit area. Specifically, the outbound verification module receives the outbound picking task from the outbound scheduling and receives the batch storage location binding record, environmental anomaly early warning tag, priority picking status, and overdue lock status provided by the early warning status generation module; the outbound picking task includes the batch information to be picked and the storage location sequence; the outbound verification module queries the correspondence between the storage location number and the storage area subdomain code based on the storage location sequence to generate the transit area; the outbound verification module reads the electrostatic sensitivity attribute corresponding to the transit area and matches the electrostatic sensitivity attribute with the batch information in the outbound picking task to generate a picking verification result; when the transit area contains a high electrostatic sensitivity subdomain, the outbound verification module... The warehouse verification module generates an anti-static operation item list and writes the anti-static operation item list into the picking list. When the batch storage location binding record has an overdue lock status, the outbound verification module records a prohibited outbound status in the picking verification result. When the batch storage location binding record has a priority picking status, the outbound verification module records a priority picking status in the picking verification result. The outbound verification module outputs the picking verification result and the anti-static operation item list to the warehouse terminal and writes the outbound verification record into the inventory data table. The outbound verification record retains the correspondence between the outbound picking task, storage location sequence, route area, electrostatic sensitivity attribute, and batch status.

Claims

1. A method for graded storage and management of electrostatic sensitive semiconductor materials, characterized in that, include: S100: Upon receiving the barcode information or outer packaging label information of the semiconductor material, identify the part number, batch information, package type, humidity sensitivity level MSL, sealing mark, packaging integrity and humidity indication status, determine the electrostatic sensitivity classification according to the package type, and generate the target warehouse area subdomain code by matching the classification mapping configuration table. S200: Based on the target storage area subdomain code, obtain the list of available storage locations and storage location status data, calculate the recommended storage location number according to the correspondence between batch expiration information or workshop life status and the ease of access to storage locations, and generate a shelf placement instruction. S300. Based on the put-away instruction and put-away feedback, establish a batch storage location binding record, recording the storage location number, humidity sensitivity level MSL, opening mark and workshop lifespan end time. S400. Based on the batch storage location binding record, compare the environmental monitoring sensor readings with the environmental threshold corresponding to the target storage area subdomain code, and query the batch storage location binding record within the same storage area subdomain to generate an environmental anomaly warning label, priority picking status, or overdue lock status. S500: When receiving an outbound picking task, determine the route area based on the storage location sequence, and generate picking verification results and an anti-static operation item list according to the electrostatic sensitivity attributes corresponding to the route area.

2. The method according to claim 1, characterized in that, The electrostatic sensitivity classification is determined based on the package type, including: classifying exposed solder ball packages as high electrostatic sensitivity, tape and lead packages as medium electrostatic sensitivity, and through-hole packages as low electrostatic sensitivity.

3. The method according to claim 1, characterized in that, The hierarchical mapping configuration table includes fields for electrostatic sensitivity classification, humidity sensitivity level (MSL), seal identification, packaging integrity, humidity indication status, and target storage area subdomain code. The electrostatic sensitivity classification, humidity sensitivity level (MSL), seal identification, packaging integrity, and humidity indication status are matched with the fields in the hierarchical mapping configuration table to obtain the target storage area subdomain code.

4. The method according to claim 1, characterized in that, Generating the target warehouse area subdomain code includes: when the packaging integrity indicates packaging damage, the humidity indication status indicates abnormal humidity, the barcode information is incomplete, or the humidity sensitivity level MSL is missing, generating isolation inspection information and writing the isolation inspection information into the inventory data table record.

5. The method according to claim 1, characterized in that, Calculating the recommended storage location number includes: screening candidate storage locations based on the target storage area subdomain code; determining adjacent candidate storage locations from the candidate storage locations based on existing storage locations with the same material number or batch; sorting the adjacent candidate storage locations according to the ease of access to the storage location, the batch expiration information, and the workshop life status to obtain the recommended storage location number.

6. The method according to claim 1, characterized in that, Establishing the batch storage location binding record includes: writing the batch information, the target storage area subdomain code, the recommended storage location number, the storage time, the humidity sensitivity level MSL, the opening identifier, and the workshop lifespan expiration time into the inventory data table; when the opening identifier indicates that it has been opened, the workshop lifespan expiration time is calculated according to the opening timestamp and the workshop lifespan rule corresponding to the humidity sensitivity level MSL.

7. The method according to claim 1, characterized in that, Generating the environmental anomaly warning label includes: calling an environmental threshold based on the storage area subdomain code corresponding to the environmental monitoring sensor reading; comparing the temperature or humidity with the environmental threshold; when the temperature or humidity exceeds the environmental threshold, querying the batch storage location binding record within the same storage area subdomain, and updating the environmental anomaly warning label on the queried batch storage location binding record.

8. The method according to claim 1, characterized in that, Generating the priority picking state or the overdue lock state includes: comparing the current time with the workshop lifespan deadline; generating the priority picking state when the remaining workshop lifespan reaches the workshop lifespan checkpoint; generating the overdue lock state when the current time exceeds the workshop lifespan deadline, and outputting a transfer baking work order or a return inspection work order.

9. The method according to claim 1, characterized in that, Upon receiving a request to re-enter returned or transferred materials, the system re-reads the packaging integrity and humidity indication status of the returned or transferred materials. When the packaging integrity indicates packaging damage or the humidity indication status indicates abnormal humidity, the system generates isolation inspection information and prevents the returned or transferred materials from returning to the normal storage location.

10. A graded storage management system for electrostatic sensitive semiconductor materials, characterized in that, include: Attribute recognition and hierarchical mapping module, storage location allocation module, batch binding module, early warning status generation module, and outbound verification module; The system is used to implement the method described in any one of claims 1-9.

Images