Collaborative Management Method of Test Reports and Certificates Based on Laboratory Information Management System

By establishing associations under testing cases in the laboratory information management system, the test plan, original records, test reports and certification certificates can be calculably linked, solving the management problem of test reports and certification certificates under multi-market certification, realizing cross-market reuse, standard expiration traceability and mass production consistency management, and reducing compliance costs and risks.

CN123070969APending Publication Date: 2026-11-10SHENZHEN MICRO TESTING DETECTION CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611252295.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-18
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing laboratory information management systems struggle to achieve a calculable correlation between test reports and certification certificates in scenarios involving multi-market certification, continuous standard updates, and mass production changes. This leads to duplicate testing, delayed certificate expiration location, and loss of compliance control throughout the entire lifecycle.

Method used

By establishing a link between test plans, original records, test reports, and certification certificates under each test case, test item data can be identified and reused across multiple target markets using test cases as the root. Consistency verification is carried out during the report issuance stage, and the update process is triggered in response to standard failure events and product changes, thereby achieving seamless integration of report circulation, standard failure traceability, and mass production consistency.

Benefits of technology

Within a single system, it enables report flow, cross-market test data reuse, standard failure tracking, and mass production consistency management, reducing the cost of repetitive testing, maintaining full lifecycle compliance, and minimizing the risk of certificate expiration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070969A_ABST
    Figure CN123070969A_ABST
Patent Text Reader

Abstract

This application relates to a collaborative management method for test reports and certificates based on a laboratory information management system. The method establishes a link between test plans, original records, test reports, and certification certificates under a test case; for certifications in multiple target markets, it determines reusable and supplementary test items based on the required test items and existing test item data for each certification, and reuses these to generate test reports; the test reports are circulated through multiple roles and stages, and are issued after consistency verification of the test reports, original records, and certificate numbers during the report issuance stage; in response to failure events of referenced standards, it retrieves affected test reports and certification certificates and triggers updates; in response to changes in certified products, it identifies affected test items and certification certificates and triggers consistency verification. This application collaboratively manages report circulation, cross-market reuse, standard failure tracing, and mass production consistency within a single system, reducing the cost of repetitive testing and maintaining full lifecycle compliance.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of information technology in testing and certification, and in particular to a collaborative management method for testing report certificates based on a laboratory information management system. Background Technology

[0002] Before products can enter multiple target markets such as North America, the European Union, and China, they typically need to complete the corresponding testing and certification according to the certification requirements of each market, and maintain compliance throughout the product's entire lifecycle. To facilitate this process, testing organizations generally use laboratory information management systems to manage testing cases, test plans, original records, test reports, and certification certificates. Test reports circulate among multiple roles during the preparation, review, signing, and distribution stages.

[0003] With the increasing demand for certification of the same product in multiple markets, frequent updates to target market standards, and continuous changes in components, processes, and software versions during mass production, the number and relationships of test reports and certification certificates are becoming increasingly complex. It is necessary to reuse existing test data as much as possible in multi-market certification to control costs, and to maintain the continued validity of certification certificates in a timely manner when standards are updated or products are changed, which significantly increases the difficulty of compliance management.

[0004] However, most existing laboratory information management systems manage the flow of individual test reports at a specific granularity, with test reports and certification certificates managed separately, lacking a calculable link between test data, test reports, certification certificates, and the referenced standards. In scenarios involving multi-market certification, continuous standard updates, and mass production changes, it is difficult to reuse existing test data, locate affected test reports and certification certificates when standards expire, and link mass production changes back to the test reports on which issued certification certificates are based. Consequently, it is impossible to achieve collaborative management of report flow, cross-market reuse, standard expiration tracing, and mass production consistency within a single system, resulting in high costs of repeated testing, delayed exposure of certificate expiration and recall risks, and difficulty in maintaining continuous control over compliance status throughout the entire lifecycle. Summary of the Invention

[0005] To address the challenges of existing laboratory information management systems in scenarios involving multi-market certification, continuous standard updates, and mass production changes, which result in issues such as fragmented testing reports and certification certificates, lack of consistent test data, and inefficient certificate expiration location and compliance throughout the entire lifecycle, this application provides a collaborative management method for testing reports and certificates based on a laboratory information management system.

[0006] Firstly, this application provides a collaborative management method for test report certificates based on a laboratory information management system, which adopts the following technical solution: A collaborative management method for test report certificates based on a laboratory information management system includes: S1. Establish a link between test plans, original records, test reports, and certification certificates for each test case; S2. Execute tests according to the test plan to obtain test item data; for multiple target market certifications, determine reusable test items and test items to be supplemented based on the test items required for each target market certification and the test item data already obtained, and generate corresponding test reports by reusing the data of reusable test items; S3. The test report is circulated through multiple stages by multiple execution roles. The circulation stage includes report issuance. In the report issuance stage, the consistency of the test report, the original records referenced, and the certificate number to be assigned is verified. If the verification is successful, the report is issued and a certificate number is assigned. S4. In response to the failure event of the standard referenced in the test report, retrieve the test report and certification certificate of the standard that has failed, generate a list of failed report standards and trigger the update process; S5. In response to changes to products for which certification certificates have been issued, determine the test items and certification certificates affected by the changes, trigger conformity verification, and update the status of the certification certificates based on the results of the conformity verification.

[0007] By adopting the above technical solutions, test plans, original records, test reports, and certification certificates are incorporated into a single computable association based on the test cases. This enables test data to be identified and reused across multiple target markets, reducing independent and repetitive testing. During report circulation, the test report, original record, and certificate number are verified for consistency at the report issuance point before a certificate number is assigned, ensuring that the issued certificate corresponds to the report and original record on which it is based. Standard expiration and product changes are respectively traced back to the affected test reports and certification certificates along the association, so that the risk of certificate expiration is discovered and triggered when standards are updated or mass production changes occur. Thus, within a single system, report circulation, cross-market reuse, standard expiration tracing, and mass production consistency are integrated into a continuously controlled full lifecycle compliance management system.

[0008] Optionally, in S1, the test report references the original record, and the certification certificate is bound to the test report and certificate number; the test case is associated with the product name, product model, customer category and service details, the original record is associated with the test plan number, and the test report is associated with the report type and status.

[0009] By adopting the above technical solution, the association between reports and certificates is converged by using the detection cases and product identification as indexes, enabling the issuing office and failure tracing to locate objects along a defined association path.

[0010] Optionally, S2 includes sub-steps S21-S24: S21. Determine the set of test items required for certification in each target market.

[0011] S22. Compare the obtained test item data with the test item set to determine the reusable test items and the test items to be supplemented.

[0012] S23. Generate a supplementary test plan for the test items to be tested, and merge the test item data obtained from the supplementary test plan into the already obtained test item data.

[0013] S24. Reuse the test item data of reusable test items and generate a test report according to the report template of the corresponding target market certification.

[0014] By adopting the above technical solution, reuse is broken down into comparison, supplementary testing, and ordered sub-steps generated according to the template, so that supplementary testing is only for gap test items, avoiding repeated testing of already satisfied test items.

[0015] Optionally, in S3, the workflow stages include report preparation, report review, report group review, customer service confirmation, report issuance, quality confirmation, and report distribution. During the report issuance stage, consistency verification includes: verifying the validity of the original records referenced in the test report; verifying the uniqueness of the certificate number to be assigned among the issued certification certificates; verifying that the current version of the test report is consistent with the version to be issued; and returning the test report to the designated preceding workflow stage with the reasons for rejection if the consistency verification fails.

[0016] By adopting the above technical solution, the original record, certificate number and report version are verified separately at the issuing point, so that reports with invalid references, duplicate numbers or inconsistent versions cannot be issued. If the verification fails, the problem can be returned with a reason.

[0017] Optionally, S3 also includes: initiating a report change for a test report that has entered the circulation process, obtaining a changed test report, and returning the changed test report to the report preparation or report review stage for recirculation.

[0018] By adopting the above technical solutions, reports that have already been circulated can be recirculated after controlled changes when revisions are needed, rather than being directly modified outside the process.

[0019] Optionally, in S4, test reports and certification certificates in the report standard invalidation list are classified according to update paths, which include document review, retesting, and reapplication; for test reports and certification certificates in the report standard invalidation list, the corresponding update process is triggered according to their respective update paths.

[0020] By adopting the above technical solution, standard failures will no longer require recertification in all cases, but will be handled differently according to the corresponding update path, reducing unnecessary retesting.

[0021] Optionally, in S5, changes include at least one of component changes, process adjustments, and software version upgrades; the conformance verification outputs a conformance verification report, which records the conformance results between the product with the issued certification and the test report.

[0022] By adopting the above technical solutions, various changes during the mass production stage are incorporated into the consistency verification and the verification results are retained, supporting the continuous maintenance of the certificate status.

[0023] Optionally, in S2, reusable test items and test items to be retested are determined, including: For each test item required for certification in the target market, compare the limits, measurement methods, and boundary conditions on which the obtained test item data is based with the limits, measurement methods, and boundary conditions for the test items required for certification in the target market. When all three are equivalent, the test item is determined to be a reusable test item; If any of the three are not equivalent, the test item will be identified as a test item to be retested.

[0024] By adopting the above technical solution, the equivalence determination of limit values, measurement methods and boundary conditions is used instead of name-based reuse. This allows test items that are nominally the same but substantially unequal to be identified as those to be retested, thus avoiding the invalidation of certificates due to reuse.

[0025] Optionally, S4 includes parallel S4a, S4b, and S4c: S4a. In response to a failure event, limit adjustments are made by reviewing the test report of the referenced standard to determine whether the obtained test data are still acceptable under the adjusted limits.

[0026] S4b. In response to a failure event, a change in measurement method, a retest is triggered for the test items in the test report of the referenced standard that are affected by the change in measurement method, while the reuse relationship of the test items in the test report that are not affected remains unchanged.

[0027] S4c. In response to the failure event, the standard becomes invalid, triggering a reapplication for the certification certificate that references the standard.

[0028] By adopting the above technical solution, the failure is classified into three levels: limit adjustment, measurement method change and standard invalidation, according to the granularity of the failure. This ensures that the method change only triggers the retesting of the affected test items while retaining the reuse of the others, thus localizing the impact of the failure.

[0029] Optionally, in S5, determining the test items affected by the change includes: mapping the change to the product function affected by the change, and then mapping the affected product function to the affected test items; triggering consistency verification only for the affected test items, while the reuse relationship of the unaffected test items remains unchanged.

[0030] By adopting the above technical solution, the affected test items are located through a two-level mapping from change to function to test item, so that the consistency verification only applies to the affected part, avoiding the need for full verification.

[0031] Optionally, target market certifications include at least one of FCC certification, CE certification, 3C certification, and SRRC certification.

[0032] By adopting the above technical solution, the method can be adapted to certification in multiple markets such as North America, the European Union, and China, supporting cross-market reuse.

[0033] Optionally, the testing case is also associated with the customer level, service period, qualification stamp status and original record documents; after the report is issued, the certification certificate is delivered after confirmation by customer service.

[0034] By adopting the above technical solution, the business delivery process is integrated into the same process, so that the certificate delivery loop is completed after confirmation upon issuance.

[0035] Optionally, the above method is executed by a system including a data management module, a reuse engine, a workflow engine, a failure tracing module, and a consistency verification module, with the data management module, reuse engine, workflow engine, failure tracing module, and consistency verification module executing S1 to S5 respectively.

[0036] By adopting the above technical solution, each step is carried out in the corresponding module, so that the method can be implemented collaboratively by the corresponding modules of the laboratory information management system.

[0037] Optionally, there is a many-to-many relationship between the original records, test reports, and certification certificates. The reuse engine records the context of which certification certificate the test item data is valid for on each reused test item data. When updating a certain test item data, it only applies to the certification certificate pointed to by the context.

[0038] By adopting the above technical solution, test item data shared by multiple reports and multiple certificates will only affect the triggering certificate when updated, thus avoiding accidental modification of certificates in other markets.

[0039] Optionally, the test report records the reuse relationship with a reference pointer to the test item data on which it is based and a version identifier, rather than copying the test item data; when the test item data is corrected or the standard on which it is based is changed, a review mark is sent back to the test report that references the test item data along the reference pointer, and the corrected data is not used to overwrite the version on which the issued certification certificate is based.

[0040] By adopting the above technical solution, data copying is replaced by reference pointers and version identifiers, enabling source data correction to notify derived report review in reverse, without silently overwriting the version on which the issued certificate is based.

[0041] Optionally, when the correction of test item data stems from a systematic bias in the measurement method, the corrected test item data shall be cross-validated with independent second-source data before being used as the benchmark for propagation to other test reports; test items that fail cross-validation shall be downgraded and marked as requiring retesting.

[0042] By adopting the above technical solution, a second source of cross-validation is introduced when correcting systematic biases in the method, thus avoiding using data that is also affected by the bias as the propagation benchmark.

[0043] Optionally, when the impact of standard expiration, product change, and pending review mark on the same certification certificate overlaps in time, the test items involved in the overlapping impact are merged into a pending set and processed uniformly according to the stricter update path in document review and retesting; if online judgment cannot be completed, the certification certificate is marked as compliant and awaits manual adjudication, and the reuse relationship of the certification certificate is frozen.

[0044] By adopting the above technical solution, when multiple types of impacts overlap on the same certificate, they are merged and processed in one go according to a stricter path, and cases that cannot be determined online are frozen for manual adjudication.

[0045] Optionally, for the test items to be retested, calculate the union of the test items to be retested for multiple target market certifications, and generate a supplementary test plan that covers the certification gaps of multiple target markets in one retest.

[0046] By adopting the above technical solution, gap test items for multiple markets can be merged into a single supplementary test, further reducing redundant testing.

[0047] Optionally, if a report change for the same test report is initiated during the waiting period for report issuance, the report issuance is locked, and the revised test report version is used to re-enter the consistency verification.

[0048] By adopting the above technical solution, when issuance is pending and report changes occur concurrently, the updated version is used for re-verification, thus avoiding the issuance of an outdated version before the change.

[0049] Optionally, when test reports, certification certificates, or test item data are changed, the change records can be preserved in a tamper-proof manner.

[0050] By adopting the above technical solutions, changes to key objects are recorded in a tamper-proof manner, supporting post-event traceability.

[0051] In summary, this application includes at least one of the following beneficial technical effects: 1. Establish a calculable link between the test plan, original records, test reports, certification certificates and referenced standards, with the test cases as the root. Within a single system, report multi-role flow, cross-market test data reuse, standard expiration traceability and mass production change consistency are connected, so that the risks of duplicate testing and certificate expiration are identified and handled in the same process, reducing compliance costs and maintaining compliance throughout the entire life cycle.

[0052] 2. Reusable test items are determined by the equivalence of limit values, measurement methods, and boundary conditions. These items are reused while ensuring the validity of the certificate, and supplementary tests are generated for any gaps. Standard failures are triggered by limit value adjustments, measurement method changes, and standard invalidation, resulting in document review, retesting of affected items, or reapplication. Mass production changes are mapped from function to test items, and only affected items are retested, thus localizing the impact of failures and changes rather than processing the entire certificate.

[0053] 3. The reuse relationship is recorded by reference pointers to test item data and version identifiers, supplemented by the valid certificate context of the reused data, the reverse verification notification of source data correction, and the second source cross-validation under systematic deviation of the method. This ensures that the test report and certification certificate maintain consistent reference relationship and controllable compliance status when source data is corrected, standards are updated, and multiple impacts are superimposed. Attached Figure Description

[0054] Figure 1 This is a schematic diagram of the system architecture for a collaborative management method of test report certificates based on a laboratory information management system, provided in an embodiment of this application.

[0055] Figure 2 This is a flowchart illustrating the method provided in an embodiment of this application.

[0056] Figure 3 This is a schematic diagram illustrating the process of reusing test items as provided in the embodiments of this application.

[0057] Figure 4 This is a schematic diagram illustrating the process of test report circulation, issuance, and verification provided in the embodiments of this application.

[0058] Figure 5 This is a schematic diagram of the reporting standard failure tracing and classification process provided in the embodiments of this application.

[0059] Figure 6 This is a schematic diagram of the product change consistency verification process provided in the embodiments of this application. Detailed Implementation

[0060] The present application will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the application and are not intended to limit the scope of the application.

[0061] This application discloses a collaborative management method for test report certificates based on a laboratory information management system. This method uses test cases as the root, establishing a computable association between test plans, original records, test reports, and certification certificates within the laboratory information management system, thereby integrating data scattered across testing, reporting, certification, and standards. First, the association of the above four types of objects is established under the test case to form a data foundation. Then, based on the test items required for certification in each target market, the obtained test item data is reused, and report issuance and certificate numbering are completed through multi-role transfer. Finally, retrospective updates and consistency verification are triggered for the invalidation of referenced standards and changes to certified products, respectively. Thus, it is possible to simultaneously achieve multi-certificate reuse from a single test, reverse location of invalid reports and standards, and compliance consistency management throughout the product lifecycle within a single system, reducing duplicate testing, shortening the lag in certificate invalidation location, and reducing the risk of compliance failure.

[0062] The following section provides a detailed explanation of this application, focusing on relevant terminology, the overall process of methods, object association under testing cases, cross-market test item reuse, multi-role transfer and issuance of test reports, tracing the invalidation of report standards, and consistency verification of changes to certified products, in conjunction with specific scenarios.

[0063] The following is a description of several terms used in the embodiments of this application.

[0064] A testing case is a management unit that carries out a single testing and certification business. It can be associated with objects such as test plans, original records, test reports, and certification certificates.

[0065] Test item data refers to the test data obtained by executing tests according to the test plan, granularized at the test item level. Reusable test items and test items to be supplemented refer to test items that meet the certification requirements for a specific target market certification and do not need to be retested from the existing test item data, and test items that require supplementary testing because the corresponding data is not yet available.

[0066] A certification certificate is a compliance credential obtained by a product after it has passed relevant certifications for a specific target market, and it is linked to the test report that generated it.

[0067] The report standard expires when the standard cited in the test report is revised or becomes invalid, requiring a review of the compliance basis of the relevant report and certificate.

[0068] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence; "comprising," "having," and any variations thereof are intended to cover non-exclusive inclusion.

[0069] The following describes the application environment of this method. This method can be applied to laboratory information management systems that conduct testing and certification for multiple target markets, such as a scenario where a wireless charging product applies for both North American FCC and European Union CE-RED certifications sequentially. In systems that manage reports and certificates independently, the test data for RF emission, conducted interference, etc., completed during the FCC stage are fixed within that report. Even if there are many equivalent test items during the CE-RED stage, the operation still requires reorganizing the tests and issuing reports, making it difficult to reuse the existing data at the test item granularity for subsequent certifications. Furthermore, when a referenced standard is revised, the system cannot trace back to existing reports and certificates that previously referenced it from that standard. Identification of invalid products relies on manual investigation, which is lagging, and there is a lack of means to map changes to affected test items and certificates after product changes. This application addresses the above situations by establishing a computable correlation between test data, reports, certificates, and standards.

[0070] The overall process of this method is explained in detail below with reference to a specific scenario. This method includes steps S1 to S5. For the overall process of this method, please refer to [link to relevant documentation]. Figure 2 .

[0071] S1. Establish the link between test plans, original records, test reports and certification certificates in the case of testing.

[0072] As the root node of a testing and certification process, a testing case contains a test plan that describes the tests to be performed and the standards to be followed. The original records contain the testing data generated during the testing process. The test report is compiled from the original records, and the certification certificate is issued based on the test report after it is approved. These four types of objects are organized into a top-down chain under the testing case, so that any certification certificate can be traced back to the test report that generated it, the original records on which the report is based, and the test plan corresponding to the original records.

[0073] In the laboratory information management system, this connection is carried out through modules such as product library management, customer management, contract management, case management and report management. Test cases are established through case management and run through all stages of subsequent report management.

[0074] In some embodiments, the above associations are further refined as follows: the test report references the original record on which it is based; the certification certificate is bound to its corresponding test report, as well as the report number and certificate number of that report; the test case is associated with the product name, product model, customer category, and service details; the original record is associated with the test plan number of the test plan to which it belongs; and the test report is associated with its report type and current status. In this way, a computable association is formed between the test cases, test plans, original records, test reports, and certification certificates, mutually pointing to each other by number, facilitating field-based retrieval within the system and driving subsequent processes.

[0075] Optionally, testing cases can also be managed in the system using fields such as company name, customer level, customer category, required time, qualification stamp, service details, service cycle, case number, product name and product model. After the test report is signed and issued, the customer service confirmation process will take over the review of listing documents and delivery of certification certificates, thereby incorporating the business attributes and delivery loop of testing cases into the same system for management.

[0076] S2. Execute tests according to the test plan to obtain test item data; for certification in multiple target markets, determine reusable test items and test items to be supplemented based on the test items required for certification in each target market and the test item data already obtained, and generate corresponding test reports by reusing the test item data of reusable test items.

[0077] In testing and certification, certification standards for the same product targeting different markets often overlap or are equivalent in a large number of test items. For example, tests such as radio frequency emission and conducted interference are required in certifications in both North America and the European Union. If the entire report is managed at the granular level, this overlapping data cannot be used in subsequent certifications. However, by organizing the test item data at the granular level, the test items that meet the requirements can be screened out and reused in subsequent certifications, and only the test items for which data is not yet available can be supplemented, thereby reducing duplicate testing.

[0078] Following the scenario of wireless charging products first applying for FCC certification and then for CE-RED certification, the FCC stage involves executing tests according to the test plan, resulting in test item data at the granular level. In the CE-RED stage, the system compares the test items required for CE-RED certification with the obtained test item data item by item. Test items that already meet the CE-RED requirements are identified as reusable test items, while the rest are identified as test items to be supplemented. The reusable test item data is then reused, and only the test items to be supplemented are tested to generate the CE-RED test report. In this type of multi-market certification integration scenario, the test item reuse rate can reach approximately 60% through a single test and multiple certification reuse approach, correspondingly reducing the investment in redundant testing. In other embodiments, determining reusable test items is not limited to comparing each test item required for target market certification; it can also utilize a pre-established certification standard mapping table—which records the correspondence and equivalence relationships between different target market certification standards at the test item level—to directly determine the set of reusable test items for the target certification from the obtained test item data through mapping.

[0079] Optionally, S2 may further include sub-steps S21 to S24: S21. Determine the set of test items required for certification in each target market.

[0080] S22. Compare the obtained test item data with the test item set to determine the reusable test items and the test items to be supplemented.

[0081] S23. Generate supplementary test plans for the test items to be tested, and merge the test item data obtained by executing the supplementary test plans into the already obtained test item data.

[0082] S24. Reuse the test item data of reusable test items and generate a test report according to the report template of the corresponding target market certification.

[0083] Sections S21 to S24 provide a specific implementation of identifying reusable and supplementary test items in S2 and reusing them to generate a report: First, the target certification requirement boundary is defined by the test item set; then, reusable and supplementary test items are categorized by comparison; subsequently, supplementary testing is used to fill the gaps; finally, the reusable and supplementary test data are organized according to the report templates for each market certification to generate a test report. The process of reusing the above test items can be found in [reference needed]. Figure 3 .

[0084] In some embodiments, when determining reusable test items and test items to be supplemented in S2, for each test item required for target market certification, the limits, measurement methods and boundary conditions on which the obtained test item data is based are compared with the limits, measurement methods and boundary conditions for the test item for that target market certification. When all three are equivalent, the test item is determined to be a reusable test item; If any of the three are not equivalent, the test item is determined as a test item to be retested.

[0085] The aforementioned limits, measurement methods, and boundary conditions constitute the three elements for determining whether test item data can be reused across certifications: limits refer to the pass / fail threshold of the test item; measurement methods refer to the test procedures and instrument configurations used to obtain the test item data; and boundary conditions refer to the environmental and operating condition settings when the test is applied, such as temperature, voltage, and load. Only when the limits, measurement methods, and boundary conditions of a test item are equivalent on both the existing data side and the target certification side can the existing data be sufficient to support the target certification's conclusion on that test item and thus be reused; if any element is not equivalent, the existing data is insufficient for direct acceptance, and the test item is classified as requiring supplementary testing.

[0086] Let the three elements of a certain test item required for target certification be those obtained from the data side. , , The three elements on the target authentication side are: , , ,in, Indicates limit value, Indicates measurement method, This indicates the boundary condition, where the subscript 'e' represents the obtained data side and 't' represents the target authentication side; if and only if and equivalence, and Equivalent and and If all three equivalence criteria are met simultaneously, the test item is determined to be a reusable test item; otherwise, it is determined to be a test item to be supplemented. For example, following the aforementioned scenario of FCC to CE-RED conversion, if a conducted interference test item has the same limit frequency band and limit curve under both FCC and CE-RED, uses equivalent conducted interference measurement procedures in both methods, and has comparable power supply and load settings for boundary conditions, then the three factors are equivalent, and the test item is judged to be reusable. However, if a radiated interference test item has different measurement distance or frequency upper limit requirements under CE-RED compared to FCC, then the boundary conditions are not equivalent, and the test item is judged to be supplemented.

[0087] In other embodiments, the equivalence determination of the three elements is not limited to one-by-one comparison, but can also be determined by the version correspondence of standard clauses or the equivalence declaration of recognized test methods: when two certifications refer to the same version of the same standard clauses, or when the target certification has recognized the equivalence of existing measurement methods, the corresponding elements can be directly determined to be equivalent without having to recheck each item.

[0088] The aforementioned certifications for various target markets can cover FCC and UL in North America, CE, RoHS, and REACH in the European Union, and domestic standards such as 3C, SRRC, and GB. For different target markets, the system can register the differences in certification modes. For example, the FCCID mode and SDoC mode in North American wireless product certification differ in the scope of applicable products and the method of certification, so that the required test items and reports can be organized according to the corresponding mode.

[0089] In other embodiments, the original record, test report, and certification certificate have a many-to-many association. This means that test item data in the same original record can be referenced by multiple test reports, thus supporting multiple certification certificates. To precisely control the scope of data updates under this many-to-many association, the reuse engine records the context of which certification certificate the test item data is valid for on each reused test item data. When updating a test item data, it only affects the certification certificate pointed to by that context, without affecting other certificates not registered in the context. Therefore, when a test item data shared by multiple certificates is updated, the system can, based on the certificate context carried on the reuse edge, trigger subsequent processing only on the certificates that truly depend on the update, avoiding accidental triggering of irrelevant certificates.

[0090] To avoid the problem of outdated copies and silently distorted certificates after source data updates caused by recording reuse relationships through data duplication, in one optional implementation, the test report does not copy the test item data it reuses. Instead, it records the reuse relationship using a reference pointer pointing to the test item data it is based on and a version identifier. The reference pointer indicates the source location of the reused test item data in the system, and the version identifier indicates the specific version of the data when it was reused. When a test item data is corrected or the standard it is based on changes, the system sends a verification mark to all test reports that reference that test item data, prompting these reports and their corresponding certificates to be re-verified. At the same time, the system does not directly overwrite the version on which the issued certification certificate was based with the corrected data, but retains the issued version, ensuring that the compliance basis of the issued certificates remains traceable.

[0091] By combining reference pointers with version identifiers, on the one hand, any correction to the source data can be accurately propagated to all downstream reports without omission, and on the other hand, the historical version anchored to by the issued certificate is not silently rewritten by the new data. This ensures both the accessibility of the correction and the stability of the basis of the issued certificate, avoiding the silent distortion that occurs when the report shows that the correction has been made but the certificate is still issued with the old value without anyone noticing.

[0092] For example, if test item data is corrected during review, the system sends a review pending flag to multiple test reports referencing that data via a reference pointer. Reports with issued certificates retain their original version identifiers from the time of issuance, awaiting manual review and confirmation before a decision is made on whether to trigger a certificate update. As an alternative to reference pointers and reverse notifications, the aforementioned reuse relationship and correction propagation can also be implemented through an event subscription mechanism or a version snapshot mechanism: the reused test item data maintains a list of subscribed reports, and when data is corrected, a correction event is published to the reports in the list; or a version snapshot is created for the reused data each time it is reused, and the snapshot version is locked when the certificate is issued.

[0093] As an optional implementation, for test items to be supplemented, the system calculates the union of test items to be supplemented for multiple target market certifications and generates a supplementary test plan based on this union, which can cover the certification gaps of multiple target markets with a single supplementary test. When the same product applies for multiple target market certifications at the same time, and each certification has several test items to be supplemented, these test items often overlap. If supplementary tests are performed for each certification separately, overlapping test items will be executed repeatedly. However, by taking the union of the test items to be supplemented for each certification and arranging a unified supplementary test, the data gaps of multiple certifications can be filled at the same time. Test items that are required by multiple certifications only need to be tested once, thereby further reducing redundant testing in the supplementary testing process.

[0094] S3. The test report is circulated through multiple stages by multiple execution roles. The circulation stage includes report issuance. In the report issuance stage, the consistency of the test report, the original records referenced, and the certificate number to be assigned is verified. If the verification is successful, the report is issued and a certificate number is assigned.

[0095] After the test report is generated, it is not directly issued to the public. Instead, it is processed sequentially in the report management of the laboratory information management system by different execution roles such as preparation, review, and signing according to the established flow stages. The processing results of each stage determine whether the report enters the next stage. The report signing stage is the key node for assigning a certificate number and making the report the basis for issuing a certificate. Therefore, at this stage, the consistency verification is performed on the test report itself, the original records it references, and the certificate number to be assigned. Only when the verification is passed is the signing completed and a certificate number is assigned to it, so as to ensure that the signing result is consistent with the records and numbers on which it is based.

[0096] Optionally, in S3, the workflow stage includes report preparation, report review, report group review, customer service confirmation, report issuance, quality confirmation, and report distribution; in the report issuance stage, consistency verification includes: Verify the validity of the original records referenced in the test report; Verify whether the certificate number to be assigned is unique among the issued certification certificates; Verify that the current version of the test report is consistent with the version to be issued; If the consistency verification fails, the test report will be returned to the designated previous process stage with the reason for rejection.

[0097] The aforementioned report preparation, review, review by the report team, customer service confirmation, report issuance, quality confirmation, and distribution constitute an orderly workflow from report generation to distribution. Each stage is the responsibility of the corresponding role, and the reporting party proceeds to the next stage after the previous stage is successfully completed. The consistency verification during the report issuance stage addresses three aspects: First, verify the validity of the original records cited in the test report to ensure that the original data on which the issuance is based is authentic and usable; Secondly, verify whether the certificate number to be assigned is unique among the issued certification certificates to avoid duplicate certificate numbers; Third, verify whether the current version of the test report is consistent with the version to be issued, to prevent the issuance of a non-final version.

[0098] If any of the three verifications fails, the system will not issue a report. Instead, it will return the test report to the designated preceding stage of the process, along with the corresponding rejection reason. The report will then be corrected by the appropriate role and re-processed. This prevents issues such as invalid records, conflicting numbers, and version mismatches at the issuance stage. The process of test report circulation and issuance verification described above can be found in [link to relevant documentation]. Figure 4 .

[0099] In some embodiments, S3 also supports initiating report changes for test reports that have entered the circulation process: when a test report that is already in circulation needs to be revised, the system initiates a report change to obtain a revised test report, and returns the revised test report to the report preparation or report review stage for recirculation, so that the revised report also goes through the subsequent stages of processing and issuance, rather than bypassing the circulation process and taking effect directly.

[0100] In other embodiments, in cases where report issuance and report modification may occur concurrently, if a report modification is initiated on the same test report while the report is in the waiting period of the issuance stage, the system locks the issuance of the report and re-enters the consistency verification with the modified test report version. The report is then issued after the modified version passes the verification, thereby avoiding the issuance of the old version before the modification takes effect, or the conflict between the issuance result and the modification result.

[0101] S4. In response to the failure of standards referenced in the test report, retrieve test reports and certification certificates referencing the failed standards, generate a list of failed report standards, and trigger an update process. Test reports and certification certificates rely on specific versions of standards for compliance. When a standard is revised or repealed, resulting in a failure event, the compliance of all reports and certificates referencing that failed standard needs to be reviewed. Because reports and certificates are linked within the system under test cases, the system can retrieve all test reports and certification certificates referencing the failed standard, compile a list of failed report standards, and trigger the corresponding update process. This allows for centralized location and unified handling of existing reports and certificates affected by standard failures, without relying on manual, one-by-one checks.

[0102] In some embodiments, test reports and certification certificates in the reporting standard failure list are categorized by update path, which includes document review, retesting, and reapplication. The system triggers the corresponding update process for each report and certificate in the list according to its respective update path. Document review is applicable to situations where compliance can be confirmed by reviewing existing data without retesting; retesting is applicable to situations where the affected test items need to be retested; and reapplication is applicable to situations where the original certification basis no longer exists and a new application is required. The correspondence between different failure scenarios and the above update paths is further explained below in conjunction with the specific types of failure events.

[0103] Optionally, S4 may include S4a, S4b, and S4c in parallel, each corresponding to a different type of failure event: S4a. In response to a failure event and limit adjustment, review the test report execution document referencing the standard to determine whether the obtained test item data are still acceptable under the adjusted limits.

[0104] S4b. In response to a failure event, a change in measurement method, a retest is triggered for the test items in the test report that reference this standard that are affected by the change in measurement method, while the reuse relationship of the test items in the test report that are not affected remains unchanged.

[0105] S4c. In response to a failure event, the standard becomes invalid, triggering a reapplication for certification certificates that reference the standard.

[0106] The above-mentioned tiered processing is based on the degree of impact of the failure event on the validity of existing data: Limit adjustments only change the threshold for acceptance judgment without changing the data itself, so the test item data already obtained does not need to be retested; it can be re-judged under the new limit after document review, corresponding to the document review path; Changes in measurement methods may render data obtained by the old method unreliable, but the impact only extends to test items that rely on that measurement method, so only the affected test items need to be retested, and the reuse relationship of other test items is not affected, corresponding to the retesting path. This selective retesting is based on the data organization at the test item granularity; Standard invalidation renders the compliance basis of the original certification no longer exist, and the existing data cannot continue to support certification under the invalidated standard, so the corresponding certification certificate is re-applied for, corresponding to the re-application path.

[0107] For example, if a standard cited in a test report becomes invalid due to a change in measurement method, only a few test items that rely on that measurement method are triggered for retesting. The reuse relationships of the remaining test items in the report and other certificates supported by these test items remain unchanged. In this way, failure events are mapped to differentiated minimum necessary actions according to their nature, avoiding over-processing caused by indiscriminate retesting or reiteration.

[0108] In other embodiments, the scope of the failure impact is not limited to a general division based on the type of failure event. It can also be determined precisely which test items in the test report are affected by the failure of a specific clause in the failure standard by mapping the test items to those clauses. This allows for further limitation of retesting or review to the truly affected test items. The process of tracing and classifying failures in the aforementioned reporting standards can be found in [reference needed]. Figure 5 .

[0109] In one alternative implementation, when a correction to a test item's data stems from a systematic bias in the measurement method, considering that this bias may not be an isolated case but rather a common cause, and that directly propagating the correction to other reports might amplify the same bias, the system first performs cross-validation on the corrected test item data using independent second-source data. Only after successful cross-validation is the corrected data used as the benchmark for propagating to other test reports that reference this data. For test items that fail cross-validation, the system downgrades them and marks them as requiring retesting, rather than propagating unverified correction results. Thus, corrections stemming from systematic bias must be verified by an independent source before propagation, preventing common-cause bias from spreading to multiple reports and certificates along reuse relationships.

[0110] S5. In response to changes to products with issued certification certificates, determine the test items and certification certificates affected by the changes, trigger conformance verification, and update the status of the certification certificates based on the results of the conformance verification. After a product obtains a certification certificate and enters mass production, its components, processes, or software may change due to supply, improvement, or upgrades, and the original certification certificate was issued based on the product status before the change. To ensure that certified products remain compliant after changes, when a product with an issued certification certificate changes, the system determines the test items and certification certificates affected by the changes, triggers conformance verification for the affected parts, and updates the status of the corresponding certification certificates based on the results of the conformance verification, such as remaining valid, marking as requiring review, or invalidating, thereby incorporating product changes in the mass production stage into compliance closed-loop management.

[0111] Optionally, in S5, product changes include at least one of the following: component changes, process adjustments, and software version upgrades: component changes refer to the replacement or modification of key components constituting the product; process adjustments refer to changes in the manufacturing process; and software version upgrades refer to upgrades to the software or firmware installed on the product. Any of these changes may affect the consistency between the product and the status recorded in the original certification report. The conformity verification outputs a conformity verification report, which records the consistency results between the product with the issued certification certificate and the test report. This report serves as the basis for determining whether the product still conforms to the certification criteria after the change and for updating the certificate status accordingly.

[0112] In some embodiments, the test items affected by the change in S5 are determined using a two-level mapping: first, the product change is mapped to the product functions affected by the change; then, the affected product functions are mapped to the test items corresponding to verifying these functions. Subsequently, only the affected test items are triggered for consistency verification, while the reuse relationships of unaffected test items remain unchanged. The reason for using the intermediate layer of product functions is that a single change usually directly affects several product functions, and each function is verified by specific test items. Through the two-level mapping from change to function and from function to test item, the scope of the change's impact can be precisely converged along the causal chain to the truly relevant test items, avoiding the need to re-verify all test items when an intermediate mapping is lacking. For example, if a product's software version upgrade only modifies functions related to wireless communication, and the two-level mapping locates several test items verifying wireless communication functions, then only these test items are triggered for consistency verification, while the reuse relationships of functions in the product unrelated to this upgrade and their corresponding test items remain unchanged.

[0113] In other embodiments, the test items affected by the change can be determined without going through the product function intermediate layer, but through a pre-established direct dependency matrix between the change and the test items. This matrix registers the test items directly associated with various changes, and the set of affected test items can be directly retrieved from the change. The above product change consistency verification process can be found in [reference needed]. Figure 6 .

[0114] In other embodiments, when the three types of impacts on the same certification certificate—standard expiration, product change, and pending review mark—overlap in time, the system merges the test items involved in these overlapping impacts into a set to be processed. This set is then processed uniformly according to the stricter update path between document review and retesting to avoid conflicts or omissions caused by handling overlapping impacts separately for the same certificate. If the system cannot determine how to handle the situation online, the certification certificate is marked as compliant and awaits manual adjudication. The reuse relationship of the certification certificate is frozen so that it cannot be reused until the adjudication is completed. The freeze is lifted after the manual adjudication and the results are updated according to the adjudication.

[0115] In some embodiments, the above method is executed by a system including a data management module, a reuse engine, a workflow engine, a failure tracing module, and a consistency verification module: The data management module executes S1 to establish the association between test plans, original records, test reports, and certification certificates under each test case; The reuse engine executes S2 to determine reusable and supplementary test items and reuses them to generate a test report. The workflow engine executes S3, driving the detection report through multiple roles and stages for circulation and issuance; The failure tracing module executes S4, responds to standard failure events, retrieves affected reports and certificates, and triggers updates; The conformance verification module executes S5, responding to product changes by triggering conformance verification and updating the certificate status.

[0116] Each module is responsible for S1 through S5, working together to achieve collaborative management of test reports and certification certificates. The system architecture can be found in [reference needed]. Figure 1 .

[0117] In other embodiments, when test reports, certification certificates, or test item data are changed, the system stores the corresponding change records in an tamper-proof manner, such as recording the content, time, and subject of the change in the form of a hash chain or blockchain, so that each change leaves an unalterable trace, which facilitates the auditing and tracing of the change history of reports, certificates, and test item data afterward.

[0118] The same or similar parts in the various embodiments of this application may be referred to each other; the technical features of each embodiment may be combined with each other to form new embodiments without conflict.

[0119] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above.

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

Claims

1. A collaborative management method for test report certificates based on a laboratory information management system, characterized in that, include: S1. Establish a link between test plans, original records, test reports, and certification certificates for each test case; S2. Perform tests according to the test plan to obtain test item data; For certification in multiple target markets, based on the test items required for certification in each target market and the test item data already obtained, reusable test items and test items to be supplemented are determined, and the data of the reusable test items are reused to generate corresponding test reports; S3. The test report is circulated through multiple stages of multiple execution roles, including report issuance; in the report issuance stage, the consistency of the test report, the original records referenced, and the certificate number to be assigned is verified, and if the verification is successful, the report is issued and a certificate number is assigned. S4. In response to the failure event of the standard referenced in the test report, retrieve the test report and certification certificate that reference the standard, generate a report standard failure list and trigger the update process; S5. In response to a change in a product for which a certification certificate has been issued, determine the test items and certification certificate affected by the change, trigger a conformance verification, and update the status of the certification certificate based on the result of the conformance verification.

2. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, In step S1, the test report references the original record, and the certification certificate is bound to the test report and the certificate number. The test cases are associated with product name, product model, customer category and service details; the original records are associated with test plan number; and the test reports are associated with report type and status.

3. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, S2 includes the following sub-steps: S21. Determine the set of test items required for certification in each target market; S22. Compare the obtained test item data with the test item set to determine the reusable test items and the test items to be supplemented; S23. Generate a supplementary test plan for the test items to be tested, and merge the test item data obtained from the supplementary test plan into the already obtained test item data; S24. Reuse the test item data of the reusable test items and generate the test report according to the report template for the corresponding target market certification.

4. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, In S3, the workflow stage includes report preparation, report review, report group review, customer service confirmation, report signing, quality confirmation and report distribution; During the report issuance phase, the consistency verification includes: Verify the validity of the original records referenced in the test report; Verify whether the certificate number to be assigned is unique among the issued certification certificates; Verify whether the current version of the test report is consistent with the version to be issued; If the consistency verification fails, the test report shall be returned to the designated preceding process stage with the reason for rejection.

5. The collaborative management method for test report certificates based on a laboratory information management system according to claim 4, characterized in that, S3 also includes: Initiate a report change for a test report that has already entered the circulation process, obtain a revised test report, and return the revised test report to the stage of report preparation or report review for recirculation.

6. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, In S4, the test reports and certification certificates in the report standard failure list are classified according to the update path, which includes document review, retesting and reapplication. For the test reports and certification certificates in the report standard failure list, the corresponding update process is triggered according to their respective update paths.

7. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, In step S5, the change includes at least one of component change, process adjustment and software version upgrade; the conformance verification outputs a conformance verification report, which records the conformance results between the product with the issued certification certificate and the test report.

8. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, In step S2, determining the reusable test item and the test item to be retested includes: For each test item required for certification in the target market, compare the limits, measurement methods, and boundary conditions on which the obtained test item data is based with the limits, measurement methods, and boundary conditions for the test item for certification in the target market. When all three are equivalent, the test item is determined as the reusable test item; If any of the three are not equivalent, the test item is determined as the test item to be retested.

9. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, The S4 includes S4a, S4b, and S4c arranged in parallel: S4a. In response to the failure event, limit adjustment is performed on the test report document referencing the standard to determine whether the obtained test item data is still qualified under the adjusted limit. S4b. In response to the failure event being a change in measurement method, a retest is triggered for the test items in the test report referencing the standard that are affected by the change in measurement method, while the reuse relationship of the test items in the test report that are not affected remains unchanged; S4c. In response to the failure event being deemed invalid for the standard, a reapplication is triggered for the certification certificate referencing the standard.

10. The collaborative management method for test report certificates based on a laboratory information management system according to claim 1, characterized in that, In step S5, the test items for determining the impact of the change include: The changes are mapped to the product functions affected by the changes, and the affected product functions are then mapped to the affected test items; the consistency verification is triggered only for the affected test items, while the reuse relationships of the unaffected test items remain unchanged.