An electronic component quality database construction method, device and medium

Abstract

The application discloses a kind of electronic component quality database construction method, equipment and medium, it is related to quality data management technical field, comprising: collecting electronic component identity, quality requirement, batch circulation and detection result data and carries out coding association, generates component standard identity record, quality requirement benchmark record, batch pedigree record and original quality evidence record;According to quality requirement benchmark record, original quality evidence record is standardized, detection determination, validity identification and repeated conflict identification, generate standard quality evidence record and quality evidence conflict record;According to batch pedigree record, divide batch state interval, form quality evidence applicable relationship record and stage quality state record;Establish association table and query index, integrity and consistency check are constructed electronic component quality database by consistency check.This application realizes that quality evidence applicable boundary is clear, and repeated, conflict detection evidence unified identification and traceable management.

Description

Technical Field

[0001] This invention relates to the field of quality data management technology, and in particular to a method, device and medium for constructing a quality database for electronic components. Background Technology

[0002] Electronic components in equipment manufacturing, communication control, aerospace, and industrial electronic systems are typically procured, stored, screened, assembled, and maintained in batches. Their quality management relies on data such as model, package, quality grade, manufacturing batch number, testing items, test reports, and certificates of conformity. Conventional quality database construction methods often use material master data and inspection records as the core, combined with supplier information, procurement technical agreements, and test reports, to establish query relationships between component identity, batch, test results, and quality conclusions for quality traceability, incoming inspection, inventory screening, and failure analysis.

[0003] In the above methods, on the one hand, the same detection event may come from multiple sources such as testing equipment, report documents, and business systems. Without a unified unique key for testing and a mechanism for identifying the validity of evidence, duplicate data and conflicting conclusions are difficult to form a verifiable chain of evidence. On the other hand, after component batches undergo changes in state such as repackaging, screening, aging, and rework, the applicable boundary between existing quality evidence and the current batch state is not easy to define, which can easily affect the objectivity of the stage quality status determination. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a method for constructing an electronic component quality database to solve the problems of unclear and repetitive application boundaries of quality evidence after batch state changes and the lack of a unified identification mechanism for conflict detection evidence in the prior art.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: In a first aspect, the present invention provides a method for constructing an electronic component quality database, comprising: collecting data on the identity, quality requirements, batch flow, and test results of electronic components, and encoding and associating them to generate standard identity records, quality requirement benchmark records, batch lineage records, and original quality evidence records; standardizing, testing, and validating the original quality evidence records based on the quality requirement benchmark records, and identifying duplicate and conflicting data according to the unique test keys to generate standard quality evidence records and quality evidence conflict records; dividing batch status intervals according to the batch lineage records, determining the direct applicability, inheritance, and historical retention relationships of quality evidence in conjunction with the standard quality evidence records to form a quality evidence applicability relationship record, and generating a stage quality status record based on valid evidence, conflicting evidence, and the completeness of mandatory inspection items; establishing an association table and query index based on the standard identity records, quality evidence applicability relationship records, and stage quality status records, and constructing an electronic component quality database after completeness and consistency verification.

[0007] As a preferred embodiment of the electronic component quality database construction method described in this invention, the method involves: collecting manufacturer names, electronic component models, packaging forms, quality grades, test item names, units of measurement, and test conditions; standardizing and mapping the collected content to generate basic data dictionary records; determining manufacturer codes, standardized model numbers, packaging codes, and quality grade codes based on the basic data dictionary records, and encoding and associating them according to the field order to generate component standard identity records; acquiring procurement technical agreements, detailed component specifications, product design documents, implementation standards, and manufacturer specifications; filtering quality requirements based on component standard identity, document scope of application, and document validity period; determining test items, test methods, test conditions, specification limits, allowable results, and sampling plans based on the priority of quality requirement documents; determining common allowable ranges for quality requirements under the same test conditions; and generating quality requirement benchmark records.

[0008] As a preferred embodiment of the electronic component quality database construction method of the present invention, the following steps are taken: Manufacturing batch number, date code, supplier delivery batch number, warehousing batch number, and batch quantity are collected. The batch data is encoded and associated according to the component standard identity record to generate source batch identifiers and target batch identifiers. Batch processing data corresponding to ordinary repackaging, repackaging, warehouse transfer, batch combination establishment, screening, aging, rework, replating, baking, and cleaning are collected, and batch processing events are divided into identity relationship events and status change events. Batch association relationships are established based on source batch identifier, target batch identifier, event type, event time, processing quantity, remaining quantity, isolated quantity, and scrap quantity, and batch quantity balance verification is performed to generate batch genealogy records. Testing task number, testing object, testing item, testing sequence, testing conditions, original testing value, testing equipment number, testing time, and executed standard version are collected. The testing results are associated with the component standard identity record and batch genealogy record. File summary values ​​are generated for testing reports, equipment output files, and certificate of conformity, and the original file storage address, source system number, and source record primary key are recorded to generate original quality evidence records.

[0009] As a preferred embodiment of the electronic component quality database construction method of the present invention, the method involves: acquiring the component standard identification, testing items, testing conditions, original test values, original units of measurement, testing time, and applicable standard version from the original quality evidence records; standardizing the testing items, original test values, and testing conditions according to the mapping relationship of testing items, the conversion relationship of units of measurement, and the coding relationship of testing conditions to generate standard testing items, standard test values, and standard testing conditions; selecting the currently applicable quality requirement benchmark from the quality requirement benchmark records according to the component standard identification, standard testing items, standard testing conditions, testing time, and applicable standard version; comparing the standard test values ​​and the standardized non-numerical test results according to the lower limit of specifications, upper limit of specifications, and allowable result set in the currently applicable quality requirement benchmark to generate a standard testing conclusion; and associating the standard testing items, standard test values, standard testing conditions, currently applicable quality requirement benchmarks, and standard testing conclusions with the corresponding original quality evidence records to generate standard quality evidence to be identified.

[0010] As a preferred embodiment of the electronic component quality database construction method of the present invention, the following steps are taken: First, the validity status of the standard quality evidence to be identified is determined based on the matching status of the current applicable quality requirement benchmark, the field integrity status of the original quality evidence record, the calibration status of the testing equipment, and the confirmation status of the executed standard version. Second, a unique testing key is generated based on the testing task number, testing object identifier, standard testing item, testing sequence, and standard testing conditions. Third, the unique testing key, standard testing value, standard testing conclusion, validity status of the quality evidence, and the source of the original quality evidence are associated to generate a standard quality evidence record. Fourth, the file summary value, standard testing value, and standard testing conclusion of standard quality evidence records with the same unique testing key are compared, and the sources of the original quality evidence for standard quality evidence records with consistent content are merged. Fifth, standard quality evidence records with the same unique testing key but inconsistent standard testing values, standard testing conclusions, and sources of the original quality evidence are retained, and conflict associations are established between corresponding standard quality evidence records to generate a quality evidence conflict record.

[0011] As a preferred embodiment of the electronic component quality database construction method of the present invention, the batch establishment time and the state change event completion time in the batch genealogy record are sorted by time, the time range between adjacent state change events is divided into batch state intervals, and batch state interval records are generated; according to the batch identifier and detection time in the standard quality evidence record, the standard quality evidence record is associated with the batch state interval to which the detection time belongs, and the valid quality evidence is determined as directly applicable evidence. Based on the identity relationship events in the batch genealogy record, valid quality evidence applicable to the entire batch in the source batch is inherited to the batch status interval corresponding to the target batch; based on the status change events in the batch genealogy record, quality evidence formed before the occurrence of the status change event is identified as historically retained evidence for the processed batch status interval; based on the standard quality evidence record identifier, the evidence formation batch status interval, the evidence application batch status interval, the applicable object, the relationship type, and the basis for the relationship formation, a quality evidence application relationship record is generated.

[0012] As a preferred embodiment of the electronic component quality database construction method of the present invention, the following steps are taken: Based on the quality evidence application relationship record, standard quality evidence records with direct application and inherited application relationships that participate in the current stage quality status determination are screened to determine valid evidence; based on the unique detection key, conflict detection items, and conflict handling status in the quality evidence conflict record, unresolved conflict evidence within the current batch status interval is determined; based on the mandatory inspection items in the quality requirement benchmark record, valid evidence consistent with the detection items, detection conditions, and execution standard version within the current batch status interval is searched item by item to determine missing mandatory inspection items; when valid non-conforming evidence exists, the stage quality status is determined to be quality non-conforming; when no valid non-conforming evidence exists but unresolved conflict evidence exists, the stage quality status is determined to be evidence conflict; when neither valid non-conforming evidence nor unresolved conflict evidence exists but missing mandatory inspection items exist, the stage quality status is determined to be evidence insufficient; when all mandatory inspection items have valid conforming evidence, the stage quality status is determined to be quality conforming, and a stage quality status record is generated.

[0013] As a preferred embodiment of the electronic component quality database construction method of the present invention, the following steps are taken: A standard component identity table, a batch lineage table, a standard quality evidence table, a quality evidence applicability table, and a stage quality status table are established based on component standard identity records, batch lineage records, standard quality evidence records, quality evidence applicability relationship records, and stage quality status records. Primary keys and foreign keys are set between the tables based on component standard identity identifiers, batch identifiers, standard quality evidence record identifiers, and batch status interval identifiers, forming associations between component identity, batch status intervals, quality evidence, and stage quality status. A query index is established based on standardized model, manufacturing batch number, testing items, quality evidence validity status, and stage quality status, forming a query path from component identity to production batch, quality evidence, and stage quality status. Each table is checked for primary key uniqueness, field integrity, foreign key reference integrity, evidence source integrity, quality evidence applicability relationship consistency, and stage quality status consistency. Records that pass the checks are written into the valid data query set, and records that fail the checks are written into the data set to be reviewed, thus constructing the electronic component quality database.

[0014] In a second aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the computer program, when executed by the processor, implements any step of the electronic component quality database construction method as described in the first aspect of the present invention.

[0015] Thirdly, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any step of the electronic component quality database construction method as described in the first aspect of the present invention.

[0016] The beneficial effects of this invention are as follows: By combining valid evidence, unresolved conflict evidence, and the completeness of mandatory inspection items to generate stage quality status records, it achieves graded judgment of quality qualified, quality unqualified, conflicting evidence, and insufficient evidence, thereby improving the objectivity and consistency of batch quality status output for electronic components; by performing primary key uniqueness, field integrity, foreign key reference integrity, evidence source integrity, consistency of applicable quality evidence relationships, and consistency of stage quality status on database records, it achieves differentiated management of valid data and data to be reviewed, thereby improving the reliability of the electronic component quality database construction results. Attached Figure Description

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

[0018] Figure 1 A flowchart illustrating the method for constructing a quality database for electronic components.

[0019] Figure 2 This is a flowchart for standard quality evidence generation and conflict identification.

[0020] Figure 3 A flowchart for generating the applicable relationship of quality evidence and the stage quality status.

[0021] Figure 4 A flowchart for the construction and verification of an electronic component quality database. Detailed Implementation

[0022] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0023] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0024] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0025] Reference Figures 1-4 As one embodiment of the present invention, this embodiment provides a method for constructing an electronic component quality database, including the following steps: S1. By collecting data on the identity, quality requirements, batch flow, and test results of electronic components, and by encoding and associating them, standard identity records, quality requirement benchmark records, batch lineage records, and original quality evidence records of electronic components are generated.

[0026] Furthermore, data on the identity, quality requirements, batch flow, and test results of electronic components are collected from the material management system, supplier management system, procurement management system, warehouse management system, quality inspection system, data acquisition terminal of testing equipment, production execution system, after-sales maintenance system, and failure analysis system.

[0027] Specifically, the system retrieves manufacturer name, manufacturer material number, electronic component model, package type, quality grade, enterprise material number, and manufacturer specification version from the material management system and supplier management system; it retrieves procurement technical agreements, detailed component specifications, product design documents, implementation standards, and testing items, testing methods, testing conditions, specification limits, permissible results, sampling plans, and document validity periods from the procurement management system and quality inspection system; it retrieves manufacturing batch number, date code, supplier delivery batch number, warehousing batch number, batch quantity, and batch processing data from the warehouse management system and production execution system; and it retrieves testing task number, testing object, testing item, testing sequence, testing conditions, original test value, original unit of measurement, original testing conclusion, testing equipment number, testing time, implementation standard version, and testing report from the quality inspection system, testing equipment data acquisition terminal, after-sales maintenance system, and failure analysis system.

[0028] The batch processing data includes operational data for ordinary repackaging, repackaging, warehouse transfer, batch combination establishment, screening, aging, rework, recoating, baking, and cleaning; the testing objects include batches, individual pieces, and test samples; the testing reports include incoming inspection reports, screening test reports, reliability test reports, certificate of conformity, and failure analysis reports.

[0029] It should be noted that structured data is collected through database interfaces, message interfaces, and file exchange interfaces; unstructured data in test reports, qualification certificates, and failure analysis reports are extracted using publicly available and mature optical character recognition and template field parsing methods. When performing field extraction on unstructured files, the original file is retained, and the extracted results are not used to replace the original file.

[0030] Furthermore, the electronic component identification data is standardized, and standard component identification records are generated according to coding association rules.

[0031] Specifically, the manufacturer code is read from the approved supplier directory, and the corresponding manufacturer code is determined based on the manufacturer name and manufacturer alias; the full-width characters, half-width characters, uppercase and lowercase letters, and semantic spaces in the component model are standardized according to the component model mapping table to obtain the standardized model; the packaging code and quality grade code are determined according to the packaging code table and quality grade code table respectively; the manufacturer code, standardized model, packaging code, and quality grade code are concatenated according to the preset field order, and the digest value of the concatenated result is calculated using a publicly available and mature digest algorithm. The complete digest value is used as the standard identity identifier of the component, and the standard identity identifier of the component is associated with the electronic component identity data to generate the standard identity record of the component.

[0032] The component standard identification record includes the component standard identification identifier, manufacturer code, manufacturer name, standardized model, original model, package code, quality grade code, enterprise material number, coding rule version, and identification data source.

[0033] It should be noted that voltage rating, temperature rating, speed rating, accuracy rating, lead-free marking, screening rating, and other product-distinguishing suffixes in component model names are retained and not deleted as semantically meaningless characters. When any field among the manufacturer name, component model, package type, and quality grade cannot be uniquely mapped, the mapping result is not forcibly selected based on text similarity; instead, the corresponding field is written to the pending review status. The manufacturer's specification version is saved as a source field for quality requirements and is not used to change the component's standard identification.

[0034] Furthermore, based on the component standard identity record, the quality requirement data is screened for applicability and associated with versions to generate a quality requirement benchmark record.

[0035] Specifically, based on the component's standard identification, quality grade, product application, validity period of the quality requirement document, and the scope of application specified in the quality requirement document, quality requirement documents matching the corresponding electronic components are selected. The quality requirements for each testing item are determined according to the priority of the quality requirement documents pre-configured in the company's quality management system. For cases where multiple numerical quality requirements exist within the same priority, testing item, testing method, testing conditions, and validity period, the maximum lower limit of each numerical quality requirement is used as the lower limit of the quality requirement benchmark, and the minimum upper limit of each numerical quality requirement is used as the upper limit of the quality requirement benchmark. For non-numerical quality requirements, the results commonly allowed by all quality requirements are used as the set of allowed results.

[0036] The priority of quality requirement documents is determined based on the project contract and the list of enterprise-approved documents. When no separate priority is specified for a specific project, the quality requirements are determined in the following order: procurement technical agreement, detailed component specifications, product design documents, implementation standards, and manufacturer specifications. The quality requirement benchmark record includes component standard identification, testing items, testing methods, testing conditions, lower limit of specifications, upper limit of specifications, allowable result set, mandatory test item marking, sampling plan, source of quality requirements, source document version, document priority, effective start time, effective end time, and quality requirement conflict marking.

[0037] It should be noted that a common allowable range is determined only for quality requirements with the same testing method and conditions. If any of the applicable conditions—temperature, applied voltage, operating frequency, load state, or testing duration—are different, a separate quality requirement baseline record is generated; specification limits under different testing conditions are not merged. When the determined lower specification limit is not greater than the upper specification limit, the corresponding lower and upper specification limits are written into the quality requirement baseline record. When the lower specification limit is greater than the upper specification limit, or when there is no common allowable result among non-numerical quality requirements, a quality requirement conflict marker is written into the quality requirement baseline record, and all sources of conflicting quality requirements are retained; a single testing limit is not directly generated.

[0038] Furthermore, batch identifiers are generated based on batch flow data, and the source relationships and status change relationships between batches of electronic components are encoded and associated to generate batch genealogy records.

[0039] Specifically, batch identifiers are generated based on the component's standard identification, manufacturing batch number, date code, supplier delivery batch number, and warehousing batch number. The original manufacturing batch number and date code are retained for the same manufacturing batch at different delivery, warehousing, and repackaging stages, and the actual circulation objects are distinguished by different delivery batch numbers, warehousing batch numbers, and target batch identifiers. Ordinary repackaging, repackaging, warehouse transfer, and batch combination are identified as identity relationship events, while screening, aging, rework, replating, baking, and cleaning are identified as state change events. A directed association relationship from the source batch to the target batch is established based on the source batch, target batch, event type, event time, processed quantity, remaining quantity, isolated quantity, scrapped quantity, and operation voucher for each event.

[0040] Among them, ordinary repackaging refers to the operation of dividing a single source batch into multiple packages without changing the physical state and quality state of electronic components; combined batch creation refers to the operation of creating a set of multiple original batches into a higher-level management set for purchase orders, warehousing tasks, or assembly tasks, and retaining the identifiers of each original batch after the combined batch is created; state change event refers to an operation that may change the current quality state of electronic components and requires distinguishing between pre-processing and post-processing quality evidence in subsequent steps.

[0041] It should be noted that when both the manufacturing batch number and date code are missing, a temporary batch identifier is generated based on the supplier traceability number, the receiving slip number, and the receiving time, and an incomplete source batch information mark is written into the batch lineage record; the temporary batch identifier is used to maintain data association and does not replace the original batch information that the manufacturer should provide.

[0042] For an event where a source batch is divided into multiple target batches, a batch quantity balance check is performed. The number of source batches before the event occurred is represented as: ; in, This indicates the number of the source batches prior to the incident. Indicates the first Number of target batches Indicates the total number of target batches. This indicates the quantity that remains in the source batch after the event has ended. This indicates the quantity that was isolated, scrapped, or confirmed to have been lost during the event.

[0043] Specifically, when the batch quantity balance verification is successful, the batch lineage relationship is marked as quantity balanced; when the batch quantity balance verification is unsuccessful, the batch lineage relationship is marked as quantity pending verification, and the association between the source batch and the target batch is retained, but the corresponding association is not used as the basis for automatic inheritance of subsequent quality evidence.

[0044] The batch genealogy record includes component standard identification, source batch identification, target batch identification, event type, event attribute, event time, processed quantity, remaining quantity, isolated quantity, scrapped quantity, operation certificate identification, quantity balance status, and source batch information completeness status.

[0045] It should be noted that, in the case of creating a combined batch from multiple source batches, batch quantity balancing checks are performed separately for each source batch; the quantities from multiple source batches are not merged to replace the individual checks of each source batch. After a state change event occurs, a target batch identifier is established for the processed electronic components, enabling the pre-processing and post-processing batches to be traced separately in the batch lineage record.

[0046] Furthermore, based on the component standard identification record, quality requirement benchmark record, and batch genealogy record, the source of the test result data is located and the original content is preserved to generate original quality evidence records.

[0047] Specifically, the original quality evidence is recorded at the granularity of one test object, one test sequence, and one test item in a single test task. Based on the test task number, component standard identification, batch identification, single-piece serial number, test sample number, test item, test sequence, and test time, the test result data is associated with the corresponding component standard identification record and batch lineage record. Publicly available and mature abstracting algorithms are used to calculate the document abstract value for test reports, equipment output files, and certificate of conformity. For test result data directly collected from the database, the source system number, source data table, source record primary key, and collection time are all written into the source location field.

[0048] For electronic components with individual serial numbers, the individual serial numbers are written into the original quality evidence record; for electronic components without individual serial numbers but subject to sampling inspection, a test sample number is generated based on the batch identifier, sampling time, sampling location, and sample sequence, and the test sample number is associated with the corresponding batch identifier; for test results for which individual tracking and sampling number management are not implemented, the batch identifier is used as the minimum quality traceability object.

[0049] The original quality evidence record includes the original quality evidence record identifier, component standard identification identifier, batch identifier, single item serial number, test sample number, test task number, test item, test sequence, original test conditions, original test value, original unit of measurement, original test conclusion, test equipment number, test time, version of the standard implemented, original file storage address, file summary value, source location field, collection time, and data integrity status.

[0050] Specifically, integrity checks are performed on the component standard identification, batch identification, test items, original test values ​​or original test conclusions, test conditions, test time and data source; when all of the aforementioned fields can be read from the test result data, the data integrity status is written as complete; when any field is missing, the data integrity status is written as critical field incomplete, and the original content that has been collected is retained.

[0051] It should be noted that the original test values, original units of measurement, and original test conclusions are saved according to the content of the source documents. This step does not convert the units of the original test values, does not make a pass / fail determination based on the quality requirement benchmark records, and does not overwrite the original data due to inconsistencies in test results from different sources. Field standardization of test results, comparison of quality limits, identification of evidence validity, and conflict identification are performed in subsequent steps.

[0052] S2. Based on the quality requirement benchmark records, standardize, test and determine the validity of the original quality evidence records, and identify duplicate and conflicting data according to the unique test key to generate standard quality evidence records and quality evidence conflict records.

[0053] Furthermore, the original quality evidence records and quality requirement benchmark records are read, and the currently applicable quality requirement benchmark records are selected based on the matching results of the testing time, testing items, testing conditions, and the version of the source document of the quality requirements.

[0054] Specifically, the process involves reading the component standard identification, batch identification, single-piece serial number, test sample number, test task number, test items, test sequence, original test conditions, original test values, original units of measurement, original test conclusions, test equipment number, test time, implementation standard version, document summary value, source location field, and data integrity status from the original quality evidence record. First, quality requirement benchmark records with the same component standard identification and test times between the valid start and end times are selected. Then, the original test items, test methods, and original test conditions are compared. When the quality requirement source of a candidate quality requirement benchmark record is an implementation standard, the implementation standard version in the original quality evidence record is matched with the source document version in the candidate quality requirement benchmark record. When the quality requirement source of a candidate quality requirement benchmark record is any one of the following: procurement technical agreement, component detailed specifications, product design documents, and manufacturer specifications, the quality requirement benchmark record corresponding to the original quality evidence record is determined by matching the source location field of the original quality evidence record, test task association information, the quality requirement source, source document version, validity period, and document priority in the candidate quality requirement benchmark record.

[0055] The testing conditions include testing temperature, testing humidity, applied voltage, operating current, operating frequency, load status, and testing duration. If the quality requirement benchmark record does not specify a certain testing condition, that testing condition will not be used as a matching field. If the quality requirement benchmark record specifies a numerical range for a certain testing condition, the original testing condition is considered a match if it falls within the corresponding numerical range. If the quality requirement benchmark record specifies a fixed value, the original testing condition is considered a match only if it is consistent with the fixed value after conversion of the measurement unit.

[0056] It should be noted that when multiple quality requirement benchmark records correspond to the same component standard identification and testing item, the selection is performed step-by-step according to the testing method, testing conditions, quality requirement source document version matching result, document priority, and validity period. When the quality requirement source is an implemented standard, the quality requirement source document version matching result is determined by the consistency between the implemented standard version and the source document version. When the quality requirement source is any of the following: procurement technical agreement, component detailed specification, product design document, and manufacturer specification, the quality requirement source document version matching result is determined by the quality requirement source identification, source document version, validity period, and document priority. If only one quality requirement benchmark record meets all matching conditions, it is determined as the currently applicable quality requirement benchmark record. If multiple quality requirement benchmark records exist and some have quality requirement conflict markers, no quality requirement benchmark record is automatically selected, and the corresponding original quality evidence record is written to the benchmark pending review status. If the quality requirement source document version matching result cannot be determined, the corresponding original quality evidence record is written to the benchmark pending review status.

[0057] Furthermore, based on the standard test item names, standard units of measurement, test condition codes, and test result formats in the current applicable quality requirement benchmark records, the original quality evidence records are standardized in terms of fields.

[0058] Specifically, based on the mapping relationship of test item names, the test item names, test item abbreviations, and test equipment field names in the original quality evidence records are mapped to the standard test item names in the quality requirement benchmark records; the original test values ​​are converted to units according to the standard units of measurement to generate standard test values; the original test conditions are split according to the test condition name, condition value, and condition unit, and arranged according to the order of the test condition fields in the quality requirement benchmark records to generate standard test conditions.

[0059] The conversion of measurement units adopts publicly available and mature conversion relationships from national metrological specifications, industry testing standards, testing equipment manuals, and enterprise-approved measurement unit conversion tables. For linear measurement units, the original test value is multiplied by the unit conversion factor and a unit conversion offset is added to obtain the standard test value; for decibels, logarithmic response, and other nonlinear measurement units, the conversion methods specified in the corresponding testing standards are followed, and linear conversion relationships are not used.

[0060] It should be noted that unit conversion only changes the standard test values ​​used for comparison and query, and does not modify the original test values ​​and original units of measurement in the original quality evidence records. When the original units of measurement cannot be mapped to the standard units of measurement, or when the unit conversion relationship cannot be determined, the corresponding original quality evidence record will be marked as "units pending review," and no test conclusion will be made for it.

[0061] Furthermore, the standardized test results are evaluated based on the standard test values ​​and the specification limits and allowable result sets in the current applicable quality requirement benchmark records.

[0062] Specifically, for numerical testing items, the quality limit margin is calculated based on the relationship between the standard test value and the specification limit, and is expressed as: ; in, Indicates the quality limit margin. Indicates the standard test value. This indicates the lower limit of the specification in the current applicable quality requirement benchmark record. This indicates the upper limit of the specifications in the current applicable quality requirement benchmark record.

[0063] Specifically, when the quality limit margin is greater than zero, the test result for numerical test items is determined to be qualified; when the quality limit margin is equal to zero, the test result is determined to be boundary qualified; and when the quality limit margin is less than zero, the test result is determined to be unqualified. For non-numerical test items, the standardized test results are matched with the set of permissible results in the currently applicable quality requirement benchmark record; if the standardized test results belong to the set of permissible results, the test result is determined to be qualified; if the standardized test results do not belong to the set of permissible results, the test result is determined to be unqualified.

[0064] Non-numerical testing items include appearance defect inspection, package integrity inspection, pin status inspection, solderability inspection, marking consistency inspection, and other enumerated testing items specified in the quality requirements document. Non-numerical test results are uniformly coded as qualified, unqualified, and indeterminate status codes according to the result mapping table. The result mapping table is established based on the implementation standard, enterprise inspection procedures, quality requirements document, and enterprise-approved result coding rules, and records the result mapping rule version, applicable test items, applicable test methods, applicable test conditions, applicable document version, and validity period. When the original description cannot determine a unique result code in the result mapping table, the corresponding original quality evidence record is marked as a result code pending review, and the corresponding test result is not used to form a quality qualified conclusion.

[0065] It should be noted that boundary compliance is a type of compliance conclusion, but it is separately marked in the standard quality evidence record for subsequent retrieval of test results close to the specification limits. Quality limit margins are only used for comparing test results of the same test items, the same standard units of measurement, the same test methods, and the same test conditions; they are not used for direct ranking between different test items. Original test conclusions are retained only as source data; standard test conclusions are regenerated based on the currently applicable quality requirement benchmark record.

[0066] Furthermore, based on the matching results of the current applicable quality requirement benchmark records, the data integrity status of the original quality evidence records, the standardization results of the test results, and the test judgment results, the validity of the original quality evidence records is identified.

[0067] Specifically, when the component standard identification, batch identification, test task number, test object identification, test item, test sequence, test conditions, test time, and data source are all complete, can uniquely match the current applicable quality requirement benchmark record, the original unit of measurement can be converted to the standard unit of measurement, and a standard test conclusion can be generated, the corresponding quality evidence is determined to be valid quality evidence. When any of the following situations exist, such as the quality requirement benchmark record cannot be uniquely matched, the quality requirement benchmark record has a quality requirement conflict mark, the test object identification is missing, the test conditions are incomplete, the original unit of measurement cannot be converted, the version of the executed standard cannot be confirmed, the original file lacks a file summary value and source location field, or the non-numerical test result cannot be uniquely encoded according to the result mapping table and is marked as a result code pending review, the corresponding quality evidence is determined to be restricted quality evidence.

[0068] The identification of the test object is determined according to the actual test granularity; the single item serial number is used when there is a single item serial number, the test sample number is used when there is no single item serial number but there is a test sample number, and the batch identification is used when there is neither a single item serial number nor a test sample number.

[0069] It should be noted that limited quality evidence remains in the electronic component quality database for tracing origin and manual verification, but is not directly used to form a quality compliance conclusion. Clearly identified non-compliance results within the limited quality evidence will still be retained as non-compliance test conclusions to avoid obscuring discovered quality anomalies due to incomplete evidence fields.

[0070] Furthermore, a unique test key is generated based on the test task number, test object identifier, standard test items, test sequence, and standard test conditions, and duplicate and conflicting data are identified according to the unique test key.

[0071] Specifically, the detection task number, detection object identifier, standard detection item code, detection sequence, and standard detection condition code are concatenated according to a preset field order. A fixed digest algorithm is used to generate a unique detection key for the concatenated result. Standardized detection results with the same unique detection key are grouped into the same detection evidence comparison group. When there are identical file digest values ​​within the detection evidence comparison group, the corresponding original quality evidence record is identified as duplicate file upload data. Instead of generating a duplicate standard quality evidence record, the original quality evidence record identifier, source system number, and collection time of the duplicate upload data are written into the evidence source field of the existing standard quality evidence record.

[0072] The standard test condition code is generated based on the test temperature, test humidity, applied voltage, operating current, operating frequency, load status, and test duration. Test conditions not specified in the quality requirement benchmark record are not included in the standard test condition code. When the test condition is a numerical range, the actual standard test condition value is used to generate the standard test condition code, and the upper and lower boundaries of the numerical range are not used to replace the actual test condition.

[0073] Specifically, if the document summary values ​​within the test evidence comparison group are different, but the component standard identification, batch identification, standard test items, standard test conditions, standard test values, and standard test conclusions are all the same, the corresponding data will be identified as multi-source duplicate data for the same test event, and only one standard quality evidence record will be generated. All original quality evidence records will be written together into the evidence source field. If different original quality evidence records within the test evidence comparison group have the same test unique key, but the standard test values ​​after standardization are different, the standard test conclusions are different, the test methods are different, the versions of the executed standards are different, or the test objects belong to different categories, the corresponding data will be identified as conflicting data.

[0074] Among them, different test object affiliations mean that the original quality evidence records corresponding to the same test unique key are associated with different batch identifiers, different single item serial numbers, or different test sample numbers; different implementation standard versions mean that different data sources for the same test event record inconsistent implementation standard versions.

[0075] It should be noted that the unique detection key is used to determine the merging scope of the same detection event. When the detection task number is generated by a single quality inspection system and can uniquely represent the detection task within that system, the unique detection key is generated based on the detection task number, the detection object identifier, the standard detection item code, the detection sequence, and the standard detection condition code. When the detection results come from multiple source systems, including the quality inspection system, the data acquisition terminal of the testing equipment, the after-sales maintenance system, and the failure analysis system, it is first determined whether different source records point to the same detection task based on the source system number, the primary key of the source record, the detection task number, and the detection task source mapping relationship. If it can be confirmed that they point to the same detection task, the same detection task number is used to participate in the generation of the unique detection key. If it cannot be confirmed that they point to the same detection task, detection tasks with the same number from different source systems are not automatically merged. The testing method, quality requirement benchmark record identifier, implementation standard version, standard test value, and standard test conclusion are used for duplicate merging and conflict identification within the same testing event, and are not used as fields to prevent the merging of evidence from multiple sources. Testing results with different testing sequences belong to different testing events. Even if the corresponding testing object, testing item, and testing conditions are the same, different unique testing keys are generated to avoid misjudging normal repeated measurements as duplicate or conflicting data. When the testing task number is missing, and the attribution of the testing task cannot be confirmed through the source system number, source record primary key, and testing task source mapping relationship, the testing time is not used to automatically generate a complete unique testing key instead of replacing the testing task number. A temporary testing association identifier is generated, and the corresponding quality evidence validity status is determined as restricted quality evidence.

[0076] Furthermore, based on standardized fields, test results, validity status of quality evidence, unique test keys, and sources of evidence, standard quality evidence records and quality evidence conflict records are generated.

[0077] Specifically, standard quality evidence records are generated for conflicting data, without selecting any test result to cover other test results; the validity status of quality evidence in each standard quality evidence record is determined as conflicting quality evidence, and the association between conflicting quality evidence is established based on the test unique key to generate quality evidence conflict records; for standardized test results that do not form conflicts, the test unique key, standard test value, standard test conclusion, validity status of quality evidence, and original quality evidence source are associated to generate standard quality evidence records.

[0078] The standard quality evidence record includes the standard quality evidence record identifier, unique test key, component standard identification identifier, batch identifier, single item serial number, test sample number, test task number, standard test item, test sequence, standard test conditions, standard test value, standard unit of measurement, quality requirement benchmark record identifier, lower specification limit, upper specification limit, allowable result set, quality limit margin, standard test conclusion, quality evidence validity status, conclusion difference marker, evidence source field, standardization rule version, and record generation time.

[0079] The quality evidence conflict record includes a quality evidence conflict record identifier, a detection unique key, a set of conflict quality evidence record identifiers, conflict fields, field values ​​corresponding to each conflict field, a set of original quality evidence record identifiers, a set of file summary values, a set of data sources, conflict identification time, and conflict handling status.

[0080] It should be noted that the initial conflict resolution status is set to "Pending Review". Conflicting data is not automatically deleted based on source system priority, file generation time, or whether the test results are qualified, nor is a final credible result automatically determined, thus avoiding unfounded overwriting of original quality evidence. Upon completion of conflict review, a conflict resolution result record is generated. This record includes a quality evidence conflict record identifier, an accepted standard quality evidence record identifier, a set of unaccepted standard quality evidence record identifiers, review basis, review method, reviewer identifier or review system identifier, review time, and conflict resolution result status. Accepted standard quality evidence records are used as standard quality evidence that can participate in the stage quality status determination. Unaccepted standard quality evidence records are retained in both the standard quality evidence record and the quality evidence conflict record, and are marked as not participating in the stage quality status determination. When the conflict review fails to determine an accepted standard quality evidence record, the conflict resolution status remains "Pending Review", and the corresponding conflicting quality evidence is not used to form a quality qualified conclusion. The standardized rule version is used to identify the rule version used for this field mapping, unit conversion, test condition coding, and result coding. Standard quality evidence records generated by different standardized rule versions are stored separately, and the processing results of the new version do not overwrite the processing results of the old version. The stage quality status determination shall use the standard quality evidence records generated under the same standardized rule version, and standard quality evidence records generated under different standardized rule versions shall not be mixed for the same stage quality status determination. When the standard test values, standard test conditions, or standard test conclusions corresponding to different standardized rule versions within the same batch status interval are inconsistent, a rule version difference review record shall be generated, and the corresponding difference evidence shall not be used to form a quality qualified conclusion before the review is completed.

[0081] S3. Divide the batch status intervals according to the batch genealogy record, determine the direct application, inheritance and historical retention relationship of quality evidence in combination with the standard quality evidence record, form a quality evidence application relationship record, and generate a stage quality status record based on valid evidence, conflicting evidence and the completeness of mandatory inspection items.

[0082] Furthermore, the source batch identifier, target batch identifier, event type, event attribute, event time, processing quantity, remaining quantity, isolation quantity, scrap quantity, quantity balance status, and source batch information integrity status are read from the batch genealogy record, and the batch status intervals are divided according to the time sequence of the status change events.

[0083] Specifically, batch lineage records associated with the same batch identifier are collected and arranged in chronological order according to the event time. The batch creation time is determined as the start time of the first batch state interval, and the completion time of the corresponding state change events such as screening, aging, rework, recoating, baking, and cleaning is determined as the end time of the previous batch state interval and the start time of the next batch state interval. For batches without subsequent state change events, the end time of the last batch state interval is set to an unfinished state.

[0084] Among them, batch establishment time refers to the time when the electronic component batch first enters the current quality management scope, including the warehousing time, the target batch generation time after repackaging, and the target batch generation time after the completion of the status change event; the completion time of the status change event is determined according to the corresponding operation equipment record, process execution record, and quality processing record; the batch status interval record includes batch status interval identifier, batch identifier, component standard identity identifier, interval start time, interval end time, start event type, start event record identifier, previous batch status interval identifier, quantity balance status, and interval valid status.

[0085] It should be noted that ordinary repackaging, repackaging, warehouse transfer, and batch combination establishment are identity relationship events and do not directly terminate the current batch status interval; identity relationship events do not change the physical and quality status of electronic components, therefore, valid quality evidence formed by the source batch before the occurrence of the identity relationship event can be associated with the target batch when the subsequent inheritance conditions are met; status change events may change the current quality status of electronic components, therefore, quality evidence formed before the status change event cannot be directly used to determine the current stage quality status after the status change event.

[0086] Furthermore, the system reads the unique test key, component standard identification, batch identification, single item serial number, test sample number, test item, test time, standard test conditions, standard test conclusion, quality evidence validity status, and quality requirement benchmark record identification from the standard quality evidence record. The system then associates the standard quality evidence record with the corresponding batch status range and determines the direct applicability relationship.

[0087] Specifically, the corresponding batch status interval is found based on the batch identifier in the standard quality evidence record, and the batch status interval with the test time between the start time and the end time of the interval is determined as the evidence formation interval; for batch status intervals with an end time that is not yet ended, the standard quality evidence record with a test time no earlier than the start time of the interval is associated with that batch status interval; when the quality evidence validity status of the standard quality evidence record is valid quality evidence, the batch identifier in the standard quality evidence record is the same as the batch identifier in the batch status interval, and the test time is within the corresponding batch status interval, the standard quality evidence record is determined as the directly applicable evidence for the corresponding batch status interval.

[0088] The granularity of inspection includes single-item inspection, sampling inspection, and batch inspection. Valid quality evidence from single-item inspection is directly applicable to the electronic components represented by the corresponding single-item serial number. Valid quality evidence from batch inspection is directly applicable to the corresponding batch status range. Valid quality evidence from sampling inspection is directly applicable to the corresponding batch status range when the sampling plan is consistent with the sampling plan in the current applicable quality requirement benchmark record, the actual number of non-conforming items does not exceed the acceptance number, and the sampling execution conclusion is acceptance.

[0089] It should be noted that if the batch identifier in the standard quality evidence record cannot be associated with a unique batch status interval, or if the testing time falls within the overlapping time range of two status change events, the evidence formation interval will not be automatically determined, and the corresponding standard quality evidence record will be written to the evidence application pending review status. If the sampling execution record lacks any of the following: sampling plan number, sampling quantity, number received, actual number of nonconformities, or sampling execution conclusion, the sampling test results will only be associated with the tested sample and will not extend to the entire batch status interval.

[0090] Furthermore, the inheritance relationship of quality evidence is determined based on the source batch, target batch, and event time corresponding to the identity relationship event.

[0091] Specifically, for target batches formed through ordinary repackaging, repackaging, and warehouse transfer, the applicability of quality evidence from the source batch before the identity relationship event is read. If the quality evidence from the source batch is valid, applicable to the source batch's state interval at the time of the identity relationship event, and there are no state change events between the source batch and the target batch, and the batch lineage record shows a quantity balance, then this quality evidence is inherited to the first batch state interval of the target batch. In cases where multiple target batches are formed from repackaging of the source batch, batch testing evidence applicable to the entire source batch and sampling testing evidence meeting the sampling plan requirements are inherited to each target batch. Individual testing evidence applicable only to a specific piece is inherited to the corresponding target batch according to the actual flow of the individual piece's serial number.

[0092] Among them, the quality evidence inherited to the target batch retains the original standard quality evidence record identifier, testing time, standard testing conclusion and original evidence source, without regenerating the test results, only generating the quality evidence inheritance relationship from the source batch status interval to the target batch status interval.

[0093] Specifically, when creating a combined batch from multiple source batches, the original batch identifiers of each source batch are retained. If each source batch has valid evidence of conformity under the same testing items, testing methods, standard testing conditions, applicable standard versions, and quality requirements, the valid evidence of conformity for the corresponding testing items is determined as the inherited applicable evidence for the combined batch. If any source batch lacks corresponding valid quality evidence, has valid non-conformity evidence, has unresolved conflicts of quality evidence, or has inconsistent applicable quality requirements, no inheritance relationship for the corresponding testing items of the combined batch is generated.

[0094] It should be noted that combined batches are only used for warehousing, order and assembly task management, and do not eliminate the original identity and quality evidence of each source batch; the testing evidence formed after the combined batch occurs should continue to record the actual testing object, and the combined batch identifier cannot replace the original batch identifier that can be identified.

[0095] Furthermore, the historical retention relationship of quality evidence is determined based on the status change event, and a record of the application relationship of quality evidence is generated based on the direct application relationship, the inheritance relationship, and the historical retention relationship.

[0096] Specifically, when state change events corresponding to screening, aging, rework, recoating, baking, and cleaning occur, quality evidence formed before the state change event and applicable to the previous batch state interval is associated with the subsequent batch state interval, but the quality evidence relationship type is determined to be historical retention, and whether it participates in the current stage quality state determination is marked as no; valid quality evidence formed by re-implementing testing after the state change event is directly associated with the batch state interval after the state change event according to the testing time, and is determined to be directly applicable evidence.

[0097] Among them, the record of applicable relationship of quality evidence includes the record identifier of applicable relationship of quality evidence, the record identifier of standard quality evidence, the record identifier of the batch status interval of evidence formation, the record identifier of the batch status interval of evidence application, the type of applicable object, the record identifier of applicable object, the type of relationship, the basis for the formation of the relationship, the start time of application, the end time of application, whether it participates in the current stage of quality status determination, the record identifier of batch lineage, and the effective status of the relationship; the type of relationship includes direct application, inherited application, and historical retention.

[0098] It should be noted that nonconforming evidence generated before the status change event is also retained as historical evidence. When the purpose of the status change event is to address identified nonconformities, pre-treatment nonconforming evidence is not directly used to determine the post-treatment stage quality status, but should be traced back to the post-treatment batch status interval through batch lineage relationships. When the valid status of quality evidence is restricted quality evidence, the association between the standard quality evidence record and the batch status interval is retained, but the valid status of the relationship is determined to be restricted, and the quality evidence is not used to form a quality compliance conclusion.

[0099] Furthermore, for each batch status interval, a stage quality status judgment point is determined, and based on the judgment point, the currently applicable quality requirement benchmark records and the set of mandatory inspection items are selected.

[0100] Specifically, for batch status intervals that have ended, the end time of the interval is determined as the time point for determining the stage quality status; for batch status intervals where the end time is not yet the end time, the generation time of the stage quality status record is determined as the time point for determining the stage quality status; based on the component standard identification, quality level, test items, standard test conditions, and the time point for determining the stage quality status, the mandatory inspection item markers that are in the valid period are read from the quality requirement benchmark record to form the set of mandatory inspection items for the current batch status interval.

[0101] If the quality requirement benchmark record has a quality requirement conflict mark, or if the quality requirement benchmark applicable at the time of stage quality status determination cannot be uniquely determined, the corresponding mandatory inspection item will be marked as a benchmark to be reviewed, and treated as a mandatory inspection item that has not formed valid quality evidence in the subsequent integrity determination.

[0102] It should be noted that the set of mandatory inspection items is jointly defined by the inspection items, inspection methods, standard inspection conditions, and the version of the applicable standard in the quality requirement benchmark record; quality evidence that only has the same inspection item name but different inspection methods or standard inspection conditions is not used to supplement the corresponding mandatory inspection items.

[0103] Furthermore, based on the record of applicable quality evidence, valid evidence, restricted nonconformity evidence, conflicting evidence, and missing mandatory inspection items are selected from the current batch status interval to participate in the stage quality status determination, and a stage quality status record is generated.

[0104] Specifically, the standardized rule version for stage judgment is determined based on the standardized rule version corresponding to the stage quality status determination point. Records with the relationship type of direct application and inherited application, the relationship validity status of "valid", the participation in the current stage quality status determination marked as "yes", the quality evidence validity status of the standard quality evidence record is "valid quality evidence", and the standardized rule version is consistent with the stage judgment standardized rule version are identified as valid evidence for the current batch status interval. Records with conflicting quality evidence records that are associated with the unique detection key, conflicting detection items, and conflicting standard quality evidence record identifiers with the current batch status interval and whose conflict handling status is "pending review" are identified as conflicting evidence for the current batch status interval. Valid evidence within the current batch status interval is searched item by item according to the set of mandatory inspection items. If there is no valid evidence that meets the corresponding detection method, standard detection conditions, and quality requirement benchmark record identifier for any mandatory inspection item, the mandatory inspection item is added to the set of missing mandatory inspection items.

[0105] Historically retained evidence, restricted quality evidence, and unresolved conflicting quality evidence are not used to supplement mandatory testing items. When there are multiple valid quality evidences for the same mandatory testing item, all valid quality evidences are used together to determine the test conclusion, and only the quality evidence with the most recent test time is selected.

[0106] Specifically, if any valid quality evidence exists within the current batch status interval that participates in the stage quality status determination, and the standard test conclusion of this valid quality evidence is unqualified, the stage quality status is determined to be unqualified. If there is no valid unqualified evidence, but there is limited unqualified evidence, the stage quality status is determined to be quality risk pending review. If there is no valid unqualified evidence or limited unqualified evidence, but there is unresolved conflicting evidence, the stage quality status is determined to be evidence conflict. If there is no valid unqualified evidence, limited unqualified evidence, or unresolved conflicting evidence, but the set of missing mandatory inspection items is not empty, the stage quality status is determined to be insufficient evidence. If there is no valid unqualified evidence, limited unqualified evidence, or unresolved conflicting evidence, the set of missing mandatory inspection items is empty, and the standard test conclusion of the valid quality evidence corresponding to each mandatory inspection item is qualified or boundary qualified, the stage quality status is determined to be qualified.

[0107] The stage quality status record includes stage quality status record identifier, batch status interval identifier, batch identifier, component standard identity identifier, stage quality status judgment time point, stage judgment standardization rule version, quality requirement benchmark record identifier set, mandatory inspection item set, directly applicable evidence record identifier set, inherited applicable evidence record identifier set, non-conforming evidence record identifier set, quality evidence conflict record identifier set, rule version difference review record identifier set, missing mandatory inspection item set, boundary qualified item set, stage quality status, status formation basis, review mark, and record generation time.

[0108] It should be noted that boundary compliance is used in the stage quality status determination according to the compliance conclusion. At the same time, the boundary compliance test items and corresponding quality limit margins are retained in the stage quality status record to facilitate subsequent retrieval of test items close to the specification limits. In the case where there is valid non-compliance evidence, limited non-compliance evidence, conflicting evidence, and missing mandatory test items in the same batch status range, a unique stage quality status is determined according to the priority order of quality non-compliance, quality risk pending verification, conflicting evidence, insufficient evidence, and quality compliance. At the same time, limited non-compliance evidence, conflicting items, and missing mandatory test items that are not used as the final status are retained to avoid the stage quality status covering other quality evidence.

[0109] It should be noted that the stage quality status record records the quality evidence status of a specific batch within a specific status interval at a specific judgment point. It does not modify the standard quality evidence record or the original quality evidence record, nor does it delete historical stage quality status records. When new valid quality evidence is subsequently added to the batch status interval and a new stage quality status record is generated, the original stage quality status record is retained, and different judgment results are distinguished by the record generation time.

[0110] S4. Establish association tables and query indexes based on component standard identity records, quality evidence application relationship records, and stage quality status records. After integrity and consistency verification, construct an electronic component quality database.

[0111] Furthermore, the system reads component standard identification records, quality requirement benchmark records, batch genealogy records, original quality evidence records, standard quality evidence records, quality evidence conflict records, batch status interval records, quality evidence applicability relationship records, and stage quality status records, and establishes the data table structure of the electronic component quality database based on the identification fields and related fields in each record.

[0112] Specifically, a component standard identity table is established using the component standard identity record as the starting point for identity association in the electronic component quality database; a batch master table and a batch genealogy table are established by extracting the source batch identifier, target batch identifier, and corresponding component standard identity identifier from the batch genealogy record; a quality requirement benchmark table is established based on the quality requirement benchmark record; and an original quality evidence table and a standard quality evidence table are established based on the original quality evidence record and the standard quality evidence record, respectively.

[0113] The component standard identity table uses the component standard identity identifier as the primary key; the batch master table uses the batch identifier as the primary key, and sets the component standard identity identifier as a foreign key pointing to the component standard identity table; the batch lineage relationship table uses the batch lineage record identifier as the primary key, and sets the source batch identifier and target batch identifier as foreign keys pointing to the batch master table respectively; the quality requirement benchmark table uses the quality requirement benchmark record identifier as the primary key, and sets the component standard identity identifier as a foreign key pointing to the component standard identity table.

[0114] It should be noted that when one standard quality evidence record corresponds to multiple original quality evidence records, the standard quality evidence record identifier and the identifiers of each original quality evidence record should be written separately into the standard quality evidence source association table, and multiple identifiers should not be written repeatedly in the same field of the standard quality evidence table. The standard quality evidence source association table is used to maintain the many-to-many association relationship between standard quality evidence records and test reports, test equipment output files, and source system records.

[0115] Furthermore, based on the quality evidence conflict record, batch status interval record, quality evidence applicability record, and stage quality status record, data tables corresponding to conflict relationships, evidence applicability relationships, and stage status relationships are established.

[0116] Specifically, the Quality Evidence Conflict Table uses the Quality Evidence Conflict Record Identifier as the primary key and records the detection unique key, conflict field, conflict identification time, and conflict handling status; the Quality Evidence Conflict Association Table records the Quality Evidence Conflict Record Identifier, Standard Quality Evidence Record Identifier, Original Quality Evidence Record Identifier, and corresponding data sources; the Batch Status Interval Table uses the Batch Status Interval Identifier as the primary key and sets the batch identifier as a foreign key pointing to the Batch Main Table; the Quality Evidence Applicability Relationship Table uses the Quality Evidence Applicability Relationship Record Identifier as the primary key and sets the Standard Quality Evidence Record Identifier as a foreign key pointing to the Standard Quality Evidence Table, and sets the Evidence Formation Batch Status Interval Identifier and Evidence Applicability Batch Status Interval Identifier as foreign keys pointing to the Batch Status Interval Table, respectively.

[0117] The table of applicable relationships for quality evidence records the type of applicable object, the identifier of the applicable object, the type of relationship, the basis for the formation of the relationship, the start time of application, the end time of application, whether it participates in the current stage of quality status determination, and the validity status of the relationship; the types of relationships include direct application, inherited application, and historical retention.

[0118] Specifically, the stage quality status table uses the stage quality status record identifier as the primary key and sets the batch status interval identifier as a foreign key pointing to the batch status interval table; the set of directly applicable evidence record identifiers, the set of inherited applicable evidence record identifiers, and the set of non-conforming evidence record identifiers in the stage quality status records are split and written into the stage quality status evidence association table; the quality evidence conflict record identifiers in the stage quality status records are written into the stage quality status conflict association table; and the set of mandatory inspection items and the set of missing mandatory inspection items are written into the stage quality status mandatory inspection item table.

[0119] It should be noted that the quality evidence applicability table only stores the applicability relationship between quality evidence and batch status intervals, and does not copy standard test values, standard test conditions, or standard test conclusions. When querying specific content of quality evidence, it is retrieved from the standard quality evidence table based on the standard quality evidence record identifier, avoiding duplicate storage of the same test result in multiple relationship tables. The stage quality status table does not repeatedly save all standard quality evidence content, but only saves the stage quality status, judgment time point, basis for status formation, review mark, and record generation time.

[0120] Furthermore, a query index for the electronic component quality database is established based on the query paths between data.

[0121] Specifically, a component identity combination index is established in the component standard identity table based on the manufacturer code, standardized model, package code, and quality grade code, which is used to locate component standard identity records according to the electronic component model and quality grade; a batch combination index is established in the batch master table based on the component standard identity identifier, manufacturing batch number, date code, and batch identifier, which is used to query the production batch and circulation batch corresponding to the same electronic component standard identity; and a quality requirement application index is established in the quality requirement benchmark table based on the component standard identity identifier, testing items, effective start time, and effective end time, which is used to query the quality requirement benchmark records applicable to the testing time.

[0122] Specifically, a quality evidence combination index is established in the standard quality evidence table based on batch identifier, test item, test time, and validity status of quality evidence. This index is used to query standard quality evidence records for specific batches, specific test items, and specific time ranges. Based on the unique test key, test event indexes are established in both the standard quality evidence table and the quality evidence conflict table to query standard quality evidence records and quality evidence conflict records corresponding to the same test event. Based on the batch status interval identifier, relationship type, and whether the evidence participates in the current stage's quality status determination, an evidence applicability index is established in the quality evidence applicability relationship table to query directly applicable evidence and inherited applicable evidence that participate in the current batch status determination, as well as historically retained evidence that does not participate in the current determination. Based on the batch identifier, batch status interval identifier, stage quality status, and stage quality status determination time, a stage quality status combination index is established in the stage quality status table to query the quality status of electronic component batches at different processing stages.

[0123] The equality query field uses a hash index or an equality index structure supported by the database management system. The combined query of model, batch, time and test item uses a publicly available and mature balanced tree index structure. The specific index structure is established according to the standard index mechanism of the relational database management system used. This embodiment does not change the existing underlying index algorithm of the database management system.

[0124] Furthermore, the electronic component quality database is subjected to checks for primary key uniqueness, required field integrity, foreign key reference integrity, batch association integrity, evidence source integrity, relationship formation basis consistency, and stage status consistency.

[0125] Specifically, the primary key fields in each data table are statistically analyzed, and primary key duplication checks are generated for records with duplicate primary key values ​​in the same data table; the required fields set in advance in each data table are read, and field missing checks are generated for records with null values ​​in the required fields; the target table and target primary key corresponding to each foreign key field are read, and reference missing checks are generated for foreign key values ​​of records where the target primary key cannot be located; the source batch identifier and target batch identifier in the batch lineage relationship table are checked to see if they both exist in the batch master table, the batch status intervals corresponding to the same batch are arranged sequentially according to the interval start time, the end time of the previous batch status interval is consistent with the start time of the next batch status interval, and the interval end time is earlier than the interval start time.

[0126] Among them, the required fields are determined according to the purpose of the record; the component standard identity identifier, manufacturer code, standardized model, package code and quality grade code in the component standard identity table are required fields; the batch identifier and component standard identity identifier in the batch master table are required fields; the standard quality evidence record identifier, test unique key, test object identifier, standard test item, test time, standard test conclusion and quality evidence validity status in the standard quality evidence table are required fields.

[0127] It should be noted that the single item serial number and the test sample number are selected and filled in according to the granularity of the test object, and are not both required fields; when the test object is a single item, the single item serial number is a required field; when the test object is a sample, the test sample number is a required field; when the test object is a batch, the batch identifier is a required field.

[0128] Furthermore, the source correlation between standard quality evidence records and original quality evidence records is verified to ensure the integrity of the evidence source and the consistency of the judgment basis, and the application relationship records of quality evidence are verified to ensure the consistency of the relationship formation basis.

[0129] Specifically, check whether each standard quality evidence record is associated with at least one original quality evidence record; check whether the component standard identification, batch identification, test task number, and test object identification in the standard quality evidence record are consistent with its associated original quality evidence record; check whether the quality requirement benchmark record identifier in the standard quality evidence record can be located to a valid quality requirement benchmark record; for numerical test results, read the standard test value, specification lower limit, specification upper limit, and standard test conclusion, and re-execute the limit relationship verification; for non-numerical test results, check whether the standardized test results belong to the set of allowed results, and compare the matching results with the standard test conclusion.

[0130] Specifically, for direct application relationships, check whether the batch identifier in the standard quality evidence record is consistent with the batch identifier corresponding to the evidence application batch status interval, and check whether the testing time is within the evidence application batch status interval; for inherited application relationships, check whether there is an association path from the evidence formation batch to the evidence application batch in the batch genealogy relationship table, and check whether the corresponding association path only contains identity relationship events and whether the quantity balance status of each batch genealogy record is balanced; for historical retention relationships, check whether there is a status change event between the evidence formation batch status interval and the evidence application batch status interval, and check whether participation in the current stage quality status determination is written as no.

[0131] It should be noted that when a quality requirement benchmark record has a quality requirement conflict marker, or when the quality evidence validity status of a standard quality evidence record is restricted quality evidence, the qualification conclusion is not re-determined; only the restricted status is verified to be consistent with the corresponding restricted cause. When the same standard quality evidence record is associated with multiple target batch status intervals, each quality evidence applicability relationship record is verified separately, and other relationships are not directly determined to be valid simply because one relationship passes the verification.

[0132] Furthermore, the completeness and consistency of the status determination of the mandatory inspection items are checked on the stage quality status records, and the valid data and the data to be reviewed are divided according to the completeness and consistency check results, and the database construction check result records are generated.

[0133] Specifically, based on the batch status interval corresponding to the stage quality status record, the stage quality status determination time point, and the component standard identification, the applicable mandatory inspection items are read from the quality requirement benchmark table; according to the stage quality status evidence association table and the quality evidence application relationship table, each mandatory inspection item is checked to see if it has valid quality evidence to participate in the current stage quality status determination; if any valid non-conformity evidence exists in the batch status interval, the stage quality status is checked to see if it is quality non-conformity; if there is no valid non-conformity evidence but there are unresolved quality evidence conflict records, the stage quality status is checked to see if it is evidence conflict; if there is no valid non-conformity evidence and no unresolved quality evidence conflict records, but there are missing mandatory inspection items, the stage quality status is checked to see if it is evidence insufficient; if all mandatory inspection items have valid conformity evidence, the stage quality status is checked to see if it is quality conformity.

[0134] The priority order of stage quality status is: unqualified quality, conflicting evidence, insufficient evidence, and qualified quality. When the stage quality status is inconsistent with the corresponding priority judgment result, a stage quality status inconsistency verification result is generated. The database construction verification result record includes the database construction verification result record identifier, verification batch number, data table involved in verification, number of verification records, number of records that passed verification, number of records pending review, number of anomalies corresponding to each verification item, verification start time, verification end time, and database construction status.

[0135] Specifically, records that pass the checks for primary key uniqueness, required field completeness, foreign key reference completeness, evidence source completeness, consistency of quality evidence applicability relationships, and consistency of stage quality status are written into the valid data query set. Records that fail any check item are retained in the corresponding business data table, and the record identifier, record type, check item, abnormal field, abnormal reason, and related record identifier are written into the data table to be reviewed. When all core data tables have been established, all primary key and foreign key relationships can be executed, and the valid data query set can form a complete query chain from component standard identity to batch status range, batch status range to quality evidence applicability relationship, quality evidence applicability relationship to standard quality evidence record, and standard quality evidence record to original quality evidence record, the database construction status is determined to be completed.

[0136] It should be noted that the data to be reviewed retains the original records and relationships, but does not enter the effective quality status query results; this step only performs structured storage, relationship establishment, query index establishment, and integrity and consistency verification on existing records, without modifying the quality requirement benchmark, regenerating standard test conclusions, changing the applicable relationship of quality evidence, or performing database structure self-optimization and quality judgment rule updates.

[0137] This embodiment also provides a computer device applicable to the method for constructing an electronic component quality database, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the method for constructing an electronic component quality database as proposed in the above embodiment.

[0138] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0139] This embodiment also provides a storage medium storing a computer program, which, when executed by a processor, implements the method for constructing an electronic component quality database as proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0140] In summary, this invention improves the objectivity and consistency of batch quality status output for electronic components by combining valid evidence, unresolved conflicting evidence, and the completeness of mandatory inspection items to generate stage quality status records. This enables graded judgment of quality compliance, quality non-compliance, conflicting evidence, and insufficient evidence. Furthermore, by performing checks on the database records for primary key uniqueness, field integrity, foreign key reference integrity, evidence source integrity, consistency of applicable quality evidence relationships, and consistency of stage quality status, it achieves differentiated management of valid data and data to be reviewed, thereby improving the reliability of the electronic component quality database construction results.

[0141] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for constructing an electronic component quality database, characterized in that, include: By collecting data on the identity, quality requirements, batch flow, and test results of electronic components, and encoding and associating them, standard identity records, quality requirement benchmark records, batch lineage records, and original quality evidence records of components are generated. Based on the quality requirement benchmark records, the original quality evidence records are standardized, tested and judged, and their validity is identified. Duplicate and conflicting data are identified according to the unique test key, and standard quality evidence records and quality evidence conflict records are generated. The batch status intervals are divided according to the batch genealogy records. The direct application, inheritance and historical retention relationships of quality evidence are determined by combining the standard quality evidence records, forming a quality evidence application relationship record. A stage quality status record is generated based on valid evidence, conflicting evidence and the completeness of mandatory inspection items. Based on the component standard identification record, the record of applicable quality evidence, and the record of stage quality status, an association table and query index are established. After integrity and consistency verification, an electronic component quality database is constructed.

2. The method for constructing an electronic component quality database as described in claim 1, characterized in that, The generated component standard identification record, quality requirement benchmark record, batch genealogy record, and original quality evidence record include: Collect manufacturer name, electronic component model, packaging form, quality grade, test item name, unit of measurement, and test conditions; standardize and map the collected content to generate basic data dictionary records. Based on the basic data dictionary records, determine the manufacturer code, standardized model, package code, and quality grade code, and encode and associate them according to the field order to generate the component standard identity record; Obtain procurement technical agreements, detailed component specifications, product design documents, implementation standards, and manufacturer specifications, and screen quality requirements based on component standard identity, document scope of application, and document validity period; Based on the priority of the quality requirements document, determine the testing items, testing methods, testing conditions, specification limits, allowable results, and sampling plans. Determine the common allowable range for quality requirements under the same testing conditions and generate a quality requirements benchmark record.

3. The method for constructing an electronic component quality database as described in claim 2, characterized in that, The process of collecting data on the identity, quality requirements, batch flow, and test results of electronic components, and then encoding and associating this data to generate standard identity records, quality requirement benchmark records, batch lineage records, and original quality evidence records also includes: Collect manufacturing batch number, date code, supplier delivery batch number, warehouse entry batch number and batch quantity, encode and associate batch data according to component standard identity record, and generate source batch identifier and target batch identifier; Collect batch processing data for ordinary repackaging, repackaging, warehouse transfer, batch creation, screening, aging, rework, recoating, baking and cleaning, and classify batch processing events into identity relationship events and status change events. Establish batch association relationships based on source batch identifier, target batch identifier, event type, event time, processing quantity, remaining quantity, quarantine quantity, and scrap quantity, and perform batch quantity balance verification to generate batch genealogy records; Collect the testing task number, testing object, testing item, testing sequence, testing conditions, original test value, testing equipment number, testing time, and the version of the standard to be implemented, and associate the test results with the component standard identification record and batch genealogy record; Generate document summary values ​​for test reports, equipment output documents, and certificate of conformity, and record the original document storage address, source system number, and source record primary key to generate original quality evidence records.

4. The method for constructing an electronic component quality database as described in claim 3, characterized in that, The standardization and testing of original quality evidence records based on quality requirement benchmarks include: Obtain the component standard identification, test items, test conditions, original test values, original units of measurement, test time, and version of the applied standard from the original quality evidence records; Based on the mapping relationship of test items, the conversion relationship of measurement units and the coding relationship of test conditions, the test items, original test values ​​and test conditions are standardized to generate standard test items, standard test values ​​and standard test conditions. Based on the component's standard identification, standard testing items, standard testing conditions, testing time, and the version of the applicable standard, select the currently applicable quality requirement benchmark from the quality requirement benchmark record; Based on the lower limit of specifications, the upper limit of specifications, and the set of allowable results in the current applicable quality requirements benchmark, the standard test values ​​and the standardized non-numerical test results are compared to generate standard test conclusions. By associating standard test items, standard test values, standard test conditions, current applicable quality requirements benchmarks, and standard test conclusions with corresponding original quality evidence records, standard quality evidence to be identified is generated.

5. The method for constructing an electronic component quality database as described in claim 4, characterized in that, The process of standardizing, testing, and validating the original quality evidence records, and identifying duplicate and conflicting data according to the unique detection key, to generate standard quality evidence records and quality evidence conflict records includes: Based on the matching status of the current applicable quality requirement benchmark, the field completeness status of the original quality evidence record, the calibration status of the testing equipment, and the confirmation status of the executed standard version, determine the validity status of the quality evidence to be identified. Generate a unique test key based on the test task number, test object identifier, standard test items, test sequence, and standard test conditions; The system associates the unique test key, standard test value, standard test conclusion, validity status of quality evidence, and source of original quality evidence to generate a standard quality evidence record. Compare the document summary value, standard test value, and standard test conclusion of standard quality evidence records with the same unique test key, and merge the original quality evidence sources of standard quality evidence records with consistent content; Standard quality evidence records that have the same unique detection key but have inconsistent standard detection values, standard detection conclusions, and original sources of quality evidence are retained separately, and conflict associations are established between corresponding standard quality evidence records to generate quality evidence conflict records.

6. The method for constructing an electronic component quality database as described in claim 5, characterized in that, The process of dividing batch status intervals based on batch genealogy records and determining the direct applicability, inheritance, and historical retention relationships of quality evidence in conjunction with standard quality evidence records to form a quality evidence applicability relationship record includes: The batch status interval is generated by sorting the batch creation time and status change event completion time in the batch genealogy record and dividing the time range between adjacent status change events into batch status intervals. Based on the batch identifier and testing time in the standard quality evidence record, the standard quality evidence record is associated with the batch status interval to which the testing time belongs, and the valid quality evidence is determined as directly applicable evidence; Based on the identity relationship events in the batch genealogy record, valid quality evidence applicable to the entire batch in the source batch is inherited to the batch status interval corresponding to the target batch; Based on the state change events in the batch genealogy records, the quality evidence formed before the state change events occurred is identified as the historical retained evidence of the post-processed batch state interval. Based on the standard quality evidence record identifier, the evidence formation batch status interval, the evidence application batch status interval, the applicable object, the relationship type, and the basis for the relationship formation, a quality evidence application relationship record is generated.

7. The method for constructing an electronic component quality database as described in claim 6, characterized in that, The generation of phased quality status records based on valid evidence, conflicting evidence, and the completeness of mandatory inspection items includes: Based on the records of applicable relationships of quality evidence, standard quality evidence records with relationships of direct application and inherited application, and which are involved in the current stage of quality status determination, are selected to determine valid evidence. Based on the unique detection key, conflict detection items, and conflict handling status in the quality evidence conflict record, identify the unresolved conflict evidence within the current batch status range; Based on the mandatory inspection items in the quality requirement benchmark record, find valid evidence that is consistent with the inspection items, inspection conditions and the version of the executed standard within the current batch status range to determine the missing mandatory inspection items. When there is valid evidence of nonconformity, the stage quality status is determined to be nonconforming; when there is no valid evidence of nonconformity but there is unresolved conflicting evidence, the stage quality status is determined to be conflicting evidence. If there is no valid evidence of nonconformity or unresolved conflicting evidence and there are missing mandatory inspection items, the stage quality status will be determined as insufficient evidence. When all mandatory inspection items have valid evidence of compliance, the stage quality status is determined to be qualified, and a stage quality status record is generated.

8. The method for constructing an electronic component quality database as described in claim 7, characterized in that, The process of establishing association tables and query indexes based on component standard identity records, quality evidence applicability records, and stage quality status records, and constructing an electronic component quality database after integrity and consistency verification, includes: Based on the component standard identification record, batch genealogy record, standard quality evidence record, quality evidence applicability relationship record, and stage quality status record, establish a component standard identification table, a batch genealogy relationship table, a standard quality evidence table, a quality evidence applicability relationship table, and a stage quality status table; Based on the component standard identification, batch identification, standard quality evidence record identification and batch status interval identification, set the primary key and foreign key between each table to form the association relationship between component identity, batch status interval, quality evidence and stage quality status. A query index is established based on standardized model, manufacturing batch number, testing items, validity status of quality evidence, and stage quality status, forming a query path from component identity to production batch, quality evidence, and stage quality status; Perform primary key uniqueness, field integrity, foreign key reference integrity, evidence source integrity, consistency of quality evidence application relationship, and consistency of stage quality status on each table. Write the records that pass the verification into the valid data query set, and write the records that fail the verification into the data set to be reviewed, thus constructing an electronic component quality database.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the electronic component quality database construction method according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the electronic component quality database construction method according to any one of claims 1 to 8.

Images