An apparatus and method for fixed asset lifecycle management

Abstract

The application discloses a kind of equipment and fixed assets whole life cycle management system and method, specifically relates to equipment and fixed assets whole life cycle management technical field, including obtaining the historical record before current change of target asset, current composition record and current change record, according to component identification, installation location, responsible subject, account attribution and use state same item alignment is executed, output changes before object set, composition difference set and change item set;For each change before object, according to use continuation, maintenance continuation, value continuation and disposal continuation, extract corresponding record item, and according to remaining part, remove part, new part and replacement part, carry out disassembly, output continuation subitem set;By same item alignment, continuation disassembly, acceptance determination, result continuation and digital thread continuation to historical record, current composition record and current change record are executed, the management meaning acceptance relationship after equipment entity composition changes is constructed.

Description

Technical Field

[0001] This invention relates to the field of equipment and fixed asset lifecycle management technology, and more specifically, to an equipment and fixed asset lifecycle management system and method. Background Technology

[0002] In equipment and fixed asset management technology, existing solutions mainly revolve around how to connect the information of each stage of equipment from procurement, acceptance, account establishment, requisition, transfer, maintenance, modification, depreciation to scrapping. In engineering practice, fixed asset number, equipment code or ledger primary key are often used as the identification basis for corresponding objects. Purchase documents, acceptance records, maintenance records, parts replacement records, transfer records, inventory records and scrapping records are written into the same management link in chronological order to support accounting, usage management and accountability. Taking the long-term use scenarios of large-scale hospital examination equipment, high-value experimental equipment in universities, or key tooling in manufacturing sites as examples, such equipment often needs to undergo multiple rounds of major repairs, core assembly replacements, auxiliary unit replacements, and functional upgrades without interrupting the original accounting attribution. At the same time, it is also required that the existing usage relationship can be continued, the maintenance basis can be verified, the subsequent depreciation processing can be connected, and the scrapping judgment can correspond to the previous records. In this process, the existing processing method is prone to a recurring situation: the system and ledger continuously show the same fixed asset as continuously existing, and the on-site equipment is also kept in use or in a state of recovery, but its key components, performance basis, quality responsibility or value basis are significantly different from the entity corresponding to the initial account. Consequently, inconsistencies in interpretation occur in the stages of fault accountability, depreciation continuation, and scrap verification. This manifests as difficulty in reaching a consistent conclusion on whether the repaired object should still be regarded as the original asset, whether the currently used object still corresponds to the original value basis, and whether the scrapped object still points to the same management object as the previous record. The reason is that although the existing method records matters such as repair, replacement, and upgrade, it still uses the static numbering continuity as the basis for judging the continuity of the object, and lacks a processing mechanism to determine whether the management object continues after the equipment entity composition changes. The technical problem this application aims to solve is: how to accurately determine the continuity of the original asset management significance of the changed object when the physical composition of the equipment changes due to major repairs, replacements, dismantling, or upgrades during the entire life cycle management of equipment and fixed assets. Summary of the Invention

[0003] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a full lifecycle management system and method for equipment and fixed assets. By performing same-item alignment, continuation disassembly, succession determination, result continuation, and digital thread continuation on historical records, current composition records, and current change records, the management significance succession relationship after changes in the equipment entity composition is constructed, thereby solving the problems mentioned in the background art.

[0004] To achieve the above objectives, the present invention provides the following technical solution: a method for full lifecycle management of equipment and fixed assets, comprising: S1. Obtain the target asset's historical records, current composition records, and current change records before the current change. Perform same-item alignment by component identifier, installation location, responsible entity, accounting attribution, and usage status. Output the object set before the change, the composition difference set, and the change item set. S2. For each object before the change, extract the corresponding record items according to continued use, continued maintenance, continued value and continued disposal, and perform decomposition according to the retained part, removed part, added part and replaced part, and output the continued item set; S3. Match the continued sub-items set with the change item set item by item, and perform the comparison in the order of consistent component destination, continued installation location, responsible entity, account attribution, and continued usage status, and output the acceptance result set corresponding to each current object; S4. Based on the inherited result set, merge the continuation items that are inherited to the same current object, split the continuation items that are inherited to different current objects, mark the uninherited continuation items as terminated, write the corresponding number thread fragment, and output the current object set and the corresponding continuation result. S5. Write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, perform continuation on each digital thread segment, generate the updated digital thread, and output the maintenance traceability result, depreciation continuation result, transfer processing result, storage and activation result or scrapping judgment result.

[0005] In a preferred embodiment, S1 includes: S11. Expand the component identifier, installation location, responsible entity, accounting attribution and usage status in the historical record, current composition record and current change record according to a unified field order to generate a historical field sequence, a composition field sequence and a change field sequence, and establish an initial corresponding item set with record items that have the same component identifier and the same installation location. S12. For each record item in the initial corresponding item set, compare the responsible entity, accounting attribution, and usage status. Retain the record items with the same responsible entity, accounting attribution, and usage status as the direct corresponding item set. For record items with different responsible entities, accounting attribution, and usage status, split them before and after according to the values ​​before and after the change in the current change record to generate the split corresponding item set. S13. Merge the directly corresponding itemset and the split corresponding itemset according to the same field order, and output the object set before the change, the difference set, and the changed itemset. The object set before the change includes the continuous corresponding record items before the change, the difference set includes the newly added record items, the removed record items, and the replaced record items, and the changed itemset includes the field rewritten record items.

[0006] In a preferred embodiment, S2 includes: S21. For each object before the change, extract the record items corresponding to the use continuation, maintenance continuation, value continuation and disposal continuation from the historical records, expand them in a unified field order, and generate the continuation record group corresponding to each object before the change. S22. Match each continuation record group with the constituent difference set item by item. Based on the consistency of component identification, the continuity of installation position, whether the responsible entity is retained, whether the accounting attribution is continued, and whether the usage status has changed, determine the retained part, removed part, added part, and replaced part in each continuation record group, and output the disassembly result group corresponding to each object before the change. S23. Merge the retained, removed, added, and replaced parts belonging to the use continuation, maintenance continuation, value continuation, and disposal continuation in each dismantling result group, and output the continuation sub-set corresponding to each object before the change.

[0007] In a preferred embodiment, S3 includes: S31. Pair each continuation item in the continuation item set with each change item in the change item set according to a unified field order, and verify in turn whether the component destination is consistent, the installation location is continuous, the responsible entity takes over, the accounting is taken over, and the usage status is continuous. Only the paired items that have all the verifications are retained as candidate acceptance items. At the same time, the acceptance difference value corresponding to each candidate acceptance item is generated by summing the component position difference, location position difference, responsibility position difference, accounting position difference, and status position difference item by item. S32. Establish a connection graph with each continuing item and each current object as nodes on both sides and each candidate receiving item as connecting edge. For connecting edges that connect the same continuing item to multiple current objects or the same current object to multiple continuing items, sort and delete them in the order of receiving difference from small to large, number of items with consistent fields from large to small, and order of change position from front to back, and output the initial receiving edge set.

[0008] In a preferred embodiment, S3 further includes: S33. Perform continuity check on the initial receiving edge set. Count the continuous items of installation location, responsible entity, accounting attribution and usage status between adjacent connecting edges along the connecting edge sequence corresponding to each current object. If the number of continuous items is less than the number of continuous items of the previous connecting edge, delete the next connecting edge and recalculate the corresponding connecting edge sequence until the number of continuous items in each connecting edge sequence no longer changes. Output a stable receiving edge set. S34. Merge the connecting edges in each stable receiving edge set according to the current object to generate the receiving result set corresponding to each current object. Each receiving result set includes the receiving continuation item identifier, the corresponding change item identifier, the receiving order, and the receiving difference.

[0009] In a preferred embodiment, S4 includes: S41. Expand the result set according to the current object identifier and the continued sub-item identifier, and construct a merge matrix group and a split matrix group. The matrix element in the merge matrix group is generated by the bitwise product of the installation location continuation value, the responsible entity continuation value, the accounting attribution continuation value and the usage status continuation value. The matrix element in the split matrix group is composed of the location change amount, the entity rewrite amount, the accounting transfer amount and the status transfer amount in a unified field order to form a cost vector. S42. Perform matrix chain multiplication and transitive closure on each merge matrix group to generate a succession reachability table for each current object. Perform dynamic programming on each succession reachability table in the succession order, retain the succession chain whose succession item count is equal to the first one. If the succession item count is the same, retain the succession chain whose cumulative cost vector is arranged in the order of position change, main body rewrite, accounting transfer, and state transfer, and whose lexicographical order is equal to the first one. Output the merge segment set corresponding to each current object.

[0010] In a preferred embodiment, S4 further includes: S43. Establish a continuous sub-item decomposition graph for each decomposition matrix group, construct the edge association matrix according to the acceptance order and perform maximum matching, delete conflicting connection edges that share the same acceptance result, and then perform prefix path accumulation and suffix path accumulation on the retained connection edges. Retain the decomposition path group whose sorting value of the number of covered acceptance results is equal to the first one and whose cumulative cost vector is lexicographically equal to the first one after being arranged in the order of position change, main body rewriting, accounting transfer, and status transfer. Output the decomposition segment set corresponding to each continuous sub-item. S44. Mark the continuation items that have not entered the merge segment set and the split segment set as termination items. Construct the result conflict matrix corresponding to the merge segment set, the split segment set and the termination items. Perform column-by-column resolution on the positions of multiple results corresponding to the same continuation item. Keep the result whose number of covered and received results is equal to the first one. If the number of covered and received results are the same, keep the result whose cumulative cost vector lexicographical order is equal to the first one. If the cumulative cost vector lexicographical order is the same, keep the result whose first item of the receiving order is equal to the first one. Update the result conflict matrix in a loop until all matrix elements in the result conflict matrix are zero. Then write the unique result into the corresponding digital thread segment and output the current object set and the usage continuation result, maintenance continuation result, value continuation result and disposal continuation result corresponding to each current object.

[0011] In a preferred embodiment, S5 includes: S51. Expand the current object set, corresponding continuation result, object set before change, lifecycle link and digital thread fragment in a unified field order, establish a thread continuation table based on the object identifier before change, the current object identifier, the succession order and the continuation type, and output the preceding chain segment, continuation chain segment and following chain segment corresponding to each object before change. S52. Perform chain segment splicing on the preceding chain segment, continuing chain segment, and following chain segment in the continuation table of each thread according to the continuation order. Among them, the continuing chain segment corresponding to the merge result is single chain insertion, the continuing chain segment corresponding to the split result is branch insertion, and the continuing chain segment corresponding to the termination result is terminated and written. Output the continuation thread group.

[0012] In a preferred embodiment, S5 further includes: S53. Construct the adjacency matrix and field fingerprint sequence for each continuation thread group. Perform chain-by-chain verification according to the rules of chain segment connection, continuous continuation order, corresponding field fingerprints, and unique branch destination. For continuation thread groups that do not meet the rules, delete the corresponding continuation chain segment and reconstruct the adjacency matrix. Output stable thread groups. S54. Write each stable thread group into the corresponding lifecycle link, generate the updated digital thread, and extract the corresponding chain segment from the updated digital thread according to the component identifier, responsible entity, accounting attribution, usage status and acceptance order, and output the maintenance traceability result, depreciation continuation result, transfer processing result, sealing and activation result or scrapping judgment result.

[0013] A lifecycle management system for equipment and fixed assets, the system comprising an alignment module, a dismantling module, a receiving module, a continuing subdivision module, and a continuing connection module: The alignment module is used to obtain the target asset's historical records, current composition records, and current change records before the current change. It performs alignment based on component identification, installation location, responsible party, accounting attribution, and usage status, and outputs the object set before the change, the composition difference set, and the change item set. The disassembly module is used to extract corresponding record items for each object before the change according to the continuation of use, maintenance, value and disposal, and to perform disassembly according to the retained part, removed part, added part and replaced part, and output the continuation sub-item set; The acceptance module is used to match the continuation sub-items set with the change item set item by item, and to perform comparison in the order of consistent component destination, installation location continuation, responsible entity acceptance, accounting attribution acceptance, and usage status continuation, and output the acceptance result set corresponding to each current object; The continuation module is used to merge continuation items that are inherited to the same current object, split continuation items that are inherited to different current objects, mark the uninherited continuation items as terminated, write the corresponding number thread fragment, and output the current object set and the corresponding continuation results based on the inherited result set. The continuation module is used to write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, perform continuation on each digital thread segment, generate the updated digital thread, and output maintenance traceability results, depreciation continuation results, transfer processing results, storage and activation results, or scrapping determination results.

[0014] The technical effects and advantages of this invention are as follows: 1. This solution aligns historical records, current composition records, and current change records, and further generates a set of objects before the change, a set of compositional differences, and a set of change items. This can transform the static numbering into a determination of object succession relationships, thereby relatively improving the problem of difficulty in confirming the continuity of managed objects after changes in the composition of equipment entities. 2. Extract the corresponding record items for continued use, continued maintenance, continued value, and continued disposal of the object before the change, and break them down into retained parts, removed parts, added parts, and replaced parts. This can refine the original change content into calculable continued sub-items, which can relatively improve the information confusion and unclear boundaries in the subsequent handover judgment. 3. By matching each item in the continuation sub-item set with the change item set, and performing comparisons according to the consistency of component destination, installation location continuation, responsibility entity acceptance, accounting attribution acceptance, and usage status continuation, a set of acceptance results corresponding to each current object can be formed, which relatively improves the consistency of the correspondence between the changed object and the original asset management meaning. 4. Based on the result set of the acceptance, the continuous sub-items are merged, split and terminated and written to the corresponding digital thread fragment. This can solidify the acceptance of the same current object, the split acceptance across current objects and the situation where acceptance is not possible, which can relatively alleviate the confusion of responsibility attribution after multiple rounds of maintenance, splitting and upgrading. 5. By continuing the current object set and its corresponding continuation results to the lifecycle link and generating an updated digital thread, the link segments before and after the change can maintain a verifiable connection relationship, which can relatively improve the consistency of interpretation between maintenance traceability, depreciation continuation, transfer processing, storage and activation and scrapping determination. Attached Figure Description

[0015] Figure 1 This is a flowchart outlining the method steps of the present invention; Figure 2 This is a schematic diagram of the system module structure of the present invention. Detailed Implementation

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

[0017] Refer to the instruction manual appendix Figure 1-2 The present invention provides a method for full lifecycle management of equipment and fixed assets, comprising: S1. Obtain the target asset's historical records, current composition records, and current change records before the current change. Perform same-item alignment by component identifier, installation location, responsible entity, accounting attribution, and usage status. Output the object set before the change, the composition difference set, and the change item set. In this implementation, S1 is used to unify historical records, current constituent records, and current change records into a single field, and then distinguish between directly corresponding record items and record items that require splitting based on pre-change and post-change values, so as to output the pre-change object set, constituent difference set, and change item set; this implementation process includes the following steps: First, S11 is used to establish a unified comparison basis. The input includes the target asset's historical records before the current change, current composition records, and current change records. The processing actions are as follows: the three types of records are expanded into historical field sequences, composition field sequences, and change field sequences according to a unified field order. The unified field order is fixed as component identifier, installation location, responsible entity, accounting attribution, and usage status. If any field is missing, an empty code is written to the corresponding field position, and the field position is retained. Then, the records are sorted according to the change effective time, event number, and writing time. When they are in parallel, they are arranged according to the lexicographical order of the component identifier. Then, based on the condition that the component identifier is the same and the installation location is the same, an initial corresponding itemset is established between the historical field sequence, composition field sequence, and change field sequence. The output includes the historical field sequence, composition field sequence, change field sequence, and initial corresponding itemset, which are read by S12. If the same component identifier corresponds to multiple records at the same installation location, the records with the same responsible entity, accounting attribution, and usage status are merged, and all other records are retained in the initial corresponding itemset. If there is no corresponding item in the historical record, it is marked as an empty corresponding historical item and retained until S13. Secondly, S12 is used to distinguish between direct and continuous correspondence and split correspondence. The input includes the initial correspondence item set and the values ​​before and after the change in the current change record. The processing actions are as follows: for each record item in the initial correspondence item set, the responsible entity, accounting attribution, and usage status are compared in sequence. Record items with all three items are written into the direct correspondence item set. For record items with at least one item that is different, the values ​​before and after the change in the current change record are read, split into preceding and subsequent record items according to a unified field order, and written into the split correspondence item set. When the current change record only provides a single field modification, only that field is split, and the remaining fields retain the original field values. The output includes the direct correspondence item set and the split correspondence item set for S13 to read. If the value before or after the change is missing, an empty code is written to the corresponding field and a missing item mark is retained. If the same record item corresponds to multiple sets of values ​​before and after the change, the first set is retained in the order of change effective time, item number, and writing time, and the rest are written into the duplicate change record table. Finally, S13 is used to form the formal output of S1; the inputs include the direct corresponding itemset, the split corresponding itemset, the historical field sequence, the constituent field sequence, and the changed field sequence; the processing actions are as follows: merge the direct corresponding itemset and the split corresponding itemset according to the unified field order, using the same component identifier, installation location, responsible entity, accounting attribution, and usage status as the merging condition; extract the set of consecutive record items formed by the preceding record items from the merge result to generate the pre-change object set, where record items with the same component identifier, the same installation location, the same responsible entity, the same accounting attribution, and the same usage status are merged into one pre-change object; Then, perform difference classification. Records that exist in the constituent field sequence but not in the historical field sequence are written as new record items; records that exist in the historical field sequence but not in the constituent field sequence are written as removed record items; records that are removed from the original record item and replaced by a new record item are written as replacement record items; and records where the component identifier continues but the responsible entity, accounting attribution, or usage status is changed are written as field rewriting record items. Among them, new record items, removed record items, and replacement record items are included in the constituent difference set, and field rewriting record items are included in the change item set. The output includes the object set before the change, the constituent difference set, and the change item set, which are read by S2 and S3 respectively. If the same record item meets the conditions of both replacement record item and field rewriting record item, it is written as a replacement record item first, and the rewritten content is retained in the change item set. If the same object before the change corresponds to multiple mutually exclusive field combinations, lexicographical resolution is performed bit by bit according to the unified field order. If it still cannot be resolved, the record item written earlier is retained, and the rest are written to the conflict record table. Through the above processing, S1 produces an output result with unified field order, clear object boundaries, and unique difference classification, which can be directly read for subsequent continuous item breakdown and acceptance determination. In practical applications: when the target asset undergoes component replacement, the original component's corresponding record item and the new component's corresponding record item are first established with an initial correspondence based on the component identifier and installation location. Then, the directly corresponding items and the split corresponding items are distinguished according to the responsible entity, accounting attribution, and usage status. Finally, the original continuous part's pre-change object set, the component entry and exit corresponding constituent difference set, and the field rewriting corresponding change item set are output.

[0018] S2. For each object before the change, extract the corresponding record items according to continued use, continued maintenance, continued value and continued disposal, and perform decomposition according to the retained part, removed part, added part and replaced part, and output the continued item set; In this embodiment, S2 is used to decompose the continuous management significance of the object before the change in the historical record into basic units that can continue to determine the inheritance relationship, so that subsequent steps can determine the destination of continued use, continued maintenance, continued value, and continued disposal after the current change. The processing principle is to first extract the corresponding record items from the historical record according to the four types of continuation, then combine them to form a difference set to perform retention, removal, addition, and replacement classification on each record item, and finally merge them into a continuation sub-set according to the continuation type. This implementation process includes the following steps: First, S21 is used to extract four types of continuation records corresponding to each object before the change from the historical records. The input includes the set of objects before the change, the historical records, and the unified field order. The processing action is as follows: for each object before the change, the record items corresponding to the object before the change are retrieved from the historical records according to the component identifier, installation location, responsible entity, accounting attribution, and usage status. The record items corresponding to usage continuation, maintenance continuation, value continuation, and disposal continuation are extracted respectively. Among them, usage continuation corresponds to usage status, installation location, and responsible entity record items; maintenance continuation corresponds to repair items, maintenance responsible entity, and component replacement item record items; value continuation corresponds to accounting attribution, depreciation related field, and value transfer field record items; and disposal continuation corresponds to transfer, sealing, activation, and scrapping item record items. Next, expand the four types of record items according to the unified field order to form the continuation record group corresponding to each object before the change; the output includes the continuation record group corresponding to each object before the change for S22 to read; if a certain object before the change is missing any continuation record item, write an empty code in the corresponding field of that continuation type and retain the field position, and do not delete the object before the change; if the same object before the change corresponds to multiple record items under the same continuation type, sort them first by the change effective time, item number, and writing time, and then write them all into the same continuation record group in the sorting order, without deleting them in advance in this step; Secondly, S22 is used to break down the continuation record group into retained parts, removed parts, added parts, and replaced parts based on the constituent difference set; the input includes each continuation record group and the constituent difference set; the processing action is as follows: each continuation record group is matched with the constituent difference set item by item, first comparing whether the component identifier is consistent, then comparing whether the installation position is continuous, where continuous installation position means that the position code is the same, or the position code appears in the position mapping pair before and after the current change record declaration; then it is determined whether the responsible entity is retained, whether the accounting attribution is continued, and whether the usage status has changed, where whether the responsible entity is retained means that the responsible entity field is the same before and after, whether the accounting attribution is continued means that the accounting attribution field is the same before and after, and whether the usage status has changed means that the status code is different before and after; Records with consistent component identification, continuous installation locations, retained responsible entities, continued accounting attribution, and unchanged usage status are designated as retained entries; records existing in historical records but corresponding to components removed from the difference set are designated as removed entries; records existing in the difference set but without a preceding corresponding entry in the continuing record group are designated as newly added entries; records where the original entry is removed and a new entry is added, and a substitution relationship exists in the difference set, are designated as replaced entries; the output includes the disassembly result group corresponding to each object before the change, for S23 to read; if the same record meets both the removed and replaced entry conditions, it is written as the replaced entry first, and the removed entry relationship is written as the preceding field of the replaced entry into the disassembly result group; if the installation location mapping pair is missing, only records with the same location code are considered to have continuous installation locations, and records with different location codes are not included in the retained entries; Finally, S23 is used to group the dismantling result groups into a set of continuation sub-items that can be directly read for acceptance judgment according to four types of continuation; the input includes each dismantling result group; the processing action is as follows: first, the record items in each dismantling result group are grouped into usage continuation, maintenance continuation, value continuation and disposal continuation, and then within each group, they are further grouped into retained parts, removed parts, added parts and replaced parts; then, the record items with the same component identification, the same installation location, the same responsible entity, the same accounting attribution and the same usage status under the same continuation type are merged to generate corresponding continuation sub-items, among which, the retained parts under the same continuation type form retained continuation sub-items, the removed parts form removed continuation sub-items, the added parts form added continuation sub-items, and the replaced parts form replaced continuation sub-items; After merging, the data is written to the continuation item set in a unified field order. The continuation item set includes at least the continuation type identifier, partial type identifier, component identifier, installation location, responsible entity, accounting attribution, and usage status. The output includes the continuation item set corresponding to each object before the change, for S3 to read. If there are multiple record items with completely identical fields under the same continuation type, the merge is performed and the number of record item sources is accumulated. If there are record items with only partially identical fields under the same continuation type, they are kept as independent continuation items and no conflict resolution is performed in this step. Through the above processing, S2 decomposes the historical records corresponding to the object before the change into a set of continuation sub-items with clear boundaries, fixed types, and unified fields. This allows subsequent inheritance determination to no longer directly face the messy original historical records, but rather standardized inputs that have been separated according to management significance. In practical application: when the core component of the target asset is replaced, the original equipment's usage status, maintenance responsibility, accounting attribution, and sealing and activation matters in the historical records are first extracted into usage continuation record items, maintenance continuation record items, value continuation record items, and disposal continuation record items, respectively. Then, combined with the information of the original component's exit and the new component's access in the difference set, the parts that still maintain continuity in the original usage relationship are written as the retained part, the old component relationship that has been exited is written as the removed part, the new component relationship is written as the added part, and the substitution relationship between the old component and the new component is written as the replacement part. Finally, these are merged to form the corresponding usage continuation sub-items, maintenance continuation sub-items, value continuation sub-items, and disposal continuation sub-items, so that subsequent steps can continue to determine which management significance is inherited by the current object.

[0019] S3. Match the continued sub-items set with the change item set item by item, and perform the comparison in the order of consistent component destination, continued installation location, responsible entity, account attribution, and continued usage status, and output the acceptance result set corresponding to each current object; In this implementation, S3 is used to establish a unique connection relationship between the continuing item set and the change item set, enabling each continuing item to be connected to the corresponding current object based on the continuity of component destination, installation location, responsible entity, accounting attribution, and usage status. The processing principle is to first generate candidate connection items that meet all connection conditions, then construct a connection correspondence diagram using these candidate items, subsequently perform continuity verification and conflict resolution on the connection correspondence diagram, and finally output the connection result set corresponding to each current object. This implementation process includes the following steps: First, S31 is used to filter out candidate acceptance items that meet the acceptance conditions from the continuation item set and the change item set, and calculate the acceptance difference of each candidate acceptance item. The input includes the continuation item set, the change item set, and the unified field order. The processing action is as follows: each continuation item and each change item are paired in pairs according to the unified field order, which is fixed as component identifier, installation location, responsible entity, accounting attribution, and usage status. For each pairing item, the consistency of component destination, the continuity of installation location, the acceptance of responsible entity, the acceptance of accounting attribution, and the continuity of usage status are checked in sequence. Among them, the consistency of component destination means that the component identifier in the continuation item corresponds to the current object to which the change item belongs in the destination field of the current change record. When the destination field is missing, the destination is determined by the common correspondence between the installation location and the responsible entity. The continuity of installation location means that the installation location code is the same, or the installation location code appears in the position mapping pair before and after the current change record declaration. The acceptance of responsible entity means that the responsible entity in the change item is equal to the responsible entity after the change, or equal to the responsible entity before the change and there is no responsibility transfer record. Accounting attribution refers to the accounting attribution in the change item being consistent with the accounting acceptance direction declared in the current change record; usage status continuation refers to the usage status in the change item being a permissible continuation status of the usage status before the change; only paired items that meet all five checks are retained as candidate acceptance items; then the component position difference, location position difference, responsibility position difference, accounting position difference, and status position difference are calculated, with the same value being 0 and different values ​​being 1, empty codes and empty codes being 0, and empty codes and non-empty codes being 1, and the five position differences are summed one by one to obtain the acceptance difference value; the output includes candidate acceptance items and their acceptance difference values, for S32 to read; if a certain continuation item does not meet all five checks with all change items, then the continuation item is recorded as a continuation item without candidate acceptance and is marked for subsequent termination judgment reading; if the same paired item has a contradiction between the destination field and the location mapping field, the destination field shall prevail, and the location mapping field is only used for installation location continuation check; Secondly, S32 is used to organize candidate acceptance items into an acceptance correspondence graph and form an initial acceptance edge set through sorting and deletion. The input includes candidate acceptance items, acceptance differences, and current object candidates formed by the change item set according to the current object identifier. The processing action is as follows: an acceptance correspondence graph is established with each continuation item and each current object as the two sides and each candidate acceptance item as the connecting edge. Each connecting edge records the continuation item identifier, current object identifier, corresponding change item identifier, and acceptance difference. For the connecting edges of the same continuation item connecting multiple current objects in the acceptance correspondence graph, sorting and deletion are performed in ascending order of acceptance difference, descending order of the number of consistent fields, and ascending order of change position, retaining the connecting edges that are sorted first. For the connecting edges of the same current object connecting multiple continuation items, sorting and deletion are also performed in ascending order of acceptance difference, descending order of the number of consistent fields, and ascending order of change position. The number of identical items in the fields is counted based on the number of identical items among the five categories: component identifier, installation location, responsible entity, accounting attribution, and usage status. The order of change location is sorted by the change effective time, item number, and write time. If multiple connecting edges are still completely identical after sorting the three categories, the connecting edge that appears earlier in the dictionary order of the continuing sub-item identifier is retained. The output includes the initial set of receiving edges for S33 to read. If the current object candidate has no connecting edges, the current object candidate will not be output as the current object for the time being, and will be added separately by subsequent newly added change items. Next, S33 is used to perform continuity verification on the initial acceptance edge set, delete connecting edges that cannot form a continuous acceptance sequence, and generate a stable acceptance edge set; the input includes the initial acceptance edge set; the processing action is as follows: divide the initial acceptance edge set into multiple connecting edge sequences according to the current object identifier, and sort each connecting edge sequence according to the acceptance order; for each connecting edge sequence, count the continuous items of installation location, continuous items of responsible entity, continuous items of accounting attribution, and continuous items of usage status for adjacent connecting edges respectively. Among them, if two adjacent connecting edges have the same corresponding fields or there is a continuity declaration in the current change record, it is recorded as a continuous item; otherwise, it is recorded as not valid. The sum of the number of valid four continuous items is recorded as the number of continuous items. If the number of consecutive items corresponding to the next connecting edge is less than the number of consecutive items corresponding to the previous connecting edge, then delete the next connecting edge, and re-sort the connecting edge sequence corresponding to the current object and recount the number of consecutive items. This rule is repeated until no connecting edge is deleted in a round of traversal, which is recorded as the number of consecutive items no longer changing. The output includes a stable set of connecting edges for S34 to read. If the same continuation item still corresponds to multiple connecting edges in the stable set of connecting edges, then uniquely retain them in ascending order of connecting edge difference, descending order of number of consecutive items, and ascending order of the first item of connecting edge, and delete the rest of the connecting edges. If the connecting edge sequence corresponding to a current object is empty after deleting a connecting edge, then the current object will not be output as a connecting result in this step. Finally, S34 is used to merge the stable acceptance edge set into the acceptance result set corresponding to each current object; the input includes the stable acceptance edge set; the processing action is as follows: merge the connection edges in the stable acceptance edge set according to the current object identifier, and write the connection edges belonging to the same current object into the same acceptance result set after sorting them according to the acceptance order; each acceptance result set includes at least the acceptance continuation item identifier, the corresponding change item identifier, the acceptance order, and the acceptance difference, wherein the acceptance order is determined according to the sorting position of the connection edge in the connection edge sequence of the current object; if there are multiple candidate acceptance result sets under the same current object, then lexicographical elimination is performed in the order of the number of acceptance continuation items, the sequence of acceptance difference, and the first item of the acceptance order, retaining a unique acceptance result set; the output includes the acceptance result set corresponding to each current object, for S4 to read; if a certain continuation item does not enter any acceptance result set, then a no-candidate acceptance continuation item mark is retained, for S4 to write the termination result; Through the above processing, S3 limits the inheritance relationship between the continuation item set and the change item set to an inheritance result set where the fields are verifiable, the order is recalculated, and the result is uniquely retained, thus avoiding the problems of non-unique inheritance objects, broken inheritance relationships, and unclear continuity of fields before and after. In practical applications: When the original control board continuation item, the new drive unit change item, and the original installation slot adjustment change item coexist in the target asset, candidate acceptance items are first screened out according to the consistency of component destination, installation location continuation, responsibility entity acceptance, accounting attribution acceptance, and usage status continuation. Then, conflicting connection edges on the same continuation item and the same current object are deleted according to the acceptance difference, the number of fields with the same consistency, and the order of change location. Subsequently, the installation location continuous item, responsibility entity continuous item, accounting attribution continuous item, and usage status continuous item statistics are performed on the remaining connection edges, and connection edges that cannot form a continuous acceptance sequence are deleted. Finally, the acceptance result set corresponding to the new control unit is output, so that subsequent steps can continue to merge continuation items accepted to the same current object and split continuation items accepted to different current objects.

[0020] S4. Based on the inherited result set, merge the continuation items that are inherited to the same current object, split the continuation items that are inherited to different current objects, mark the uninherited continuation items as terminated, write the corresponding number thread fragment, and output the current object set and the corresponding continuation result. In this embodiment, S4 is used to further transform the inherited result set into a structured result that can be directly written into a digital thread segment. This allows continuation items inherited to the same present object to form a merge result, continuation items inherited to different present objects to form a split result, and continuation items without a continuation relationship to form a termination result. Based on this, a set of present objects with a unique affiliation relationship and their corresponding continuation results are output. The processing principle is to first construct a merge matrix group and a split matrix group respectively, then obtain the merge segment set and the split segment set using matrix reachability and path coverage relationships, and finally resolve the multiple result cases corresponding to the same continuation item through a result conflict matrix. This implementation process includes the following steps: First, S41 is used to convert the acceptance result set into a merge matrix group and a split matrix group that can be calculated subsequently. The input includes the acceptance result set, the unified field order, and the acceptance order. The processing action is as follows: expand the acceptance result set according to the current object identifier and the continuation item identifier, classify the acceptance results pointing to the same current object into the same merge matrix group, and classify the acceptance results corresponding to the same continuation item but pointing to different current objects into the same split matrix group. For any two acceptance results in the merge matrix group, calculate the installation location continuation value, the responsible entity acceptance value, the accounting attribution acceptance value, and the usage status continuation value respectively. Among them, the value is 1 when the preceding and following fields are the same or there is a continuation declaration, and 0 otherwise. Then multiply the four values ​​bit by bit to generate the corresponding matrix element. For any two acceptance results in the split matrix group, calculate the position change amount, main body rewriting amount, accounting transfer amount, and status transfer amount respectively. Among them, the same is 0, different is 1, empty code and empty code are 0, empty code and non-empty code are 1. Then, form a cost vector according to the unified field order and write it into the corresponding matrix element. The output includes the merge matrix group and the split matrix group, which are read by S42 and S43. If a merge matrix group contains only one acceptance result, a single merge matrix group is directly generated and retained in S42. If a split matrix group contains only one acceptance result, it is not entered into the split matrix group operation, and the acceptance result is retained for S44 to participate in the result summary before the termination judgment. Secondly, S42 is used to obtain the set of consecutively inherited merge segments within the same current object; the input includes merge matrix groups and the inheritance order; the processing action is as follows: perform matrix multiplication on each merge matrix group according to the inheritance order, and only retain the product of matrix elements that can be inherited from the previous inheritance result to the next inheritance result during matrix multiplication, and then perform transitive closure solution on the multiplication result to generate a succession reachability table, where the rows and columns of the succession reachability table correspond to the inheritance results in the merge matrix group, and a matrix element of 1 indicates that the row corresponding inheritance result can be continuously reached from the column corresponding inheritance result, and a matrix element of 0 indicates that it cannot be continuously reached; then perform dynamic programming on the succession reachability table according to the inheritance order, and the dynamic programming state includes at least the current inheritance result identifier, the current number of succession items, the cumulative cost vector, and the predecessor inheritance result identifier, where the current number of succession items is the number of inheritance results covered from the initial inheritance result to the current inheritance result, and the cumulative cost vector is the result of digit-by-digit accumulation of the cost vector corresponding to each matrix element on the path; Subsequently, each dynamic programming state is sorted. First, it is sorted by the number of successive items. The successive chain with the first ranking value is selected as a candidate merge chain. Then, among the candidate merge chains, they are sorted lexicographically in the order of position change, main body rewrite, accounting transfer, and state transfer in the cumulative cost vector. The successive chain with the first ranking value is retained as the merge segment set corresponding to the current object. The output includes the merge segment set corresponding to each current object for S44 to read. If multiple successive chains are the same in both the successive item ranking value and the cumulative cost vector lexicographical ranking value, the successive chain with the first ranking value is retained according to the succession order. If no successive chain with a length greater than 1 is formed after a round of dynamic programming, the single succession result is written as a single merge segment into the merge segment set. Secondly, S43 is used to obtain the set of segments when the same continuation item corresponds to multiple current objects. The input includes the set of segments and the order of acceptance. The processing is as follows: a continuation segmentation graph is built for each set of segments. The nodes in the continuation segmentation graph are the acceptance results, and the connecting edges are the candidate connecting edges that satisfy the previous and next relationship and do not share the same current object. Then, the edge association matrix is ​​constructed according to the order of acceptance. The rows and columns of the edge association matrix correspond to the candidate connecting edges. When two candidate connecting edges share the same acceptance result, the corresponding matrix element is 1, otherwise it is 0. The maximum matching is performed on the edge association matrix to delete conflicting connecting edges that share the same acceptance result and retain the set of non-conflicting connecting edges. Then, the prefix path accumulation and suffix path accumulation are performed on the retained connecting edges respectively. The prefix path accumulation accumulates from the first item of the path to the next edge to cover the number of acceptance results and the cumulative cost vector. The suffix path accumulation accumulates from the last item of the path to the next edge to cover the number of acceptance results and the cumulative cost vector. Then, the prefix path accumulation result and the suffix path accumulation result are concatenated to generate the complete path result. The complete path results are first sorted by the number of coverage acceptance results, and the split path group with the first sort value is retained. Then, the split path group is sorted lexicographically according to the position change, main body rewriting, accounting transfer, and status transfer in the cumulative cost vector, and the split path group with the first sort value is retained as the split segment set corresponding to the continuation item. The output includes the split segment set corresponding to each continuation item for S44 to read. If multiple split path groups are the same in both the number of coverage acceptance results and the lexicographical sort value of the cumulative cost vector, the split path group with the first sort value is retained according to the order of the first item acceptance. If no connecting edge is retained after deleting conflicting connecting edges, the continuation item does not form a split segment set and is retained until S44 performs the termination decision. Finally, S44 is used to perform unified resolution on the merge set, split set, and terminating item, and writes the unique result to the corresponding numeric thread segment; the input includes the merge set, split set, continuation items that did not enter the merge set and split set, and the current object identifier; the processing action is as follows: first, the continuation items that did not enter the merge set and split set are marked as terminating items, and the termination reasons are written according to four categories: no candidate successor, merge conflict deletion, split conflict deletion, and consistency resolution deletion; then, the merge set, split set, and terminating item are constructed. The result conflict matrix corresponds to each item, where rows and columns of the result conflict matrix correspond to the result items. When two result items involve the same continuation item, the matrix element is set to 1; otherwise, it is set to 0. The result conflict matrix is ​​resolved column by column. First, the result whose number of covered and inherited results is equal to the first one is retained. Then, among the results with the same number of covered and inherited results, the result whose cumulative cost vector lexicographical order is equal to the first one is retained. Then, among the results with the same cumulative cost vector lexicographical order, the result whose first inherited item is equal to the first one is retained. The remaining results are deleted. Each time a result item is deleted, the corresponding row and column of the result conflict matrix are updated synchronously, and the conflict relationship with the remaining result items is recalculated. The above resolution is performed repeatedly until all matrix elements in the result conflict matrix are zero. Then, the unique results that are retained are written to the corresponding digital thread segments according to the current object identifier. The merge result is written with the merge start and end result identifier and merge order, the split result is written with the split path identifier and split order, and the termination result is written with the termination position and termination reason. Finally, the digital thread segments are summarized according to the current object identifier, and the current object set with unique ownership relationship and the usage continuation result, maintenance continuation result, value continuation result and disposal continuation result corresponding to each current object are output for S5 to read. If a current object has no retained result items after resolution, but there are new write items in the change item set, the new write item is generated into a new current object and written to the corresponding digital thread segment. If multiple result items with the same continuation order appear for the same current object after the digital thread segment is written, they are resolved step by step according to the result type, cumulative cost vector lexicographical order and writing order, and only one item is retained. Through the above processing, S4 transforms the inherited result set into three unique results: merged result, split result, and terminated result, and completes the writing of digital thread fragments. This gives the current object set and its corresponding continuation results clear structural boundaries, unique ownership relationships, and directly continuable fragment forms, avoiding the problems of the same continuation item corresponding to multiple results at the same time, the breakage of the inheritance chain within the same current object, and the conflict between splitting paths. In practical applications: When the original control board continuation item in the target asset is transferred to the current host object, the original communication unit continuation item is transferred to the current standby machine object, and the original heat dissipation component continuation item has not formed a candidate for transfer, first construct a merge matrix group and a split matrix group according to the current object identifier and the continuation item identifier. Then, obtain the merge segment set corresponding to the current host object through matrix multiplication, transitive closure and dynamic programming. Obtain the split segment set corresponding to the communication unit through the continuation item split graph, edge association matrix, maximum matching and path accumulation. Then, write the heat dissipation component continuation item as the termination item. Finally, delete the conflict results on the same continuation item through the result conflict matrix. Write the retained merge result, split result and termination result into the corresponding digital thread segment respectively, so that subsequent steps can directly complete the life cycle link continuation based on the digital thread segment.

[0021] S5. Write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, perform continuation on each digital thread segment, generate the updated digital thread, and output the maintenance traceability result, depreciation continuation result, transfer processing result, sealing and activation result or scrapping judgment result. In this implementation, S5 is used to formally write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, and to continue the digital thread segment into the updated digital thread, thereby outputting results that can be directly used for maintenance traceability, depreciation continuation, transfer processing, storage activation, and scrapping determination. Its processing principle is to first establish a thread continuation table, clarify the connection relationship between the preceding chain segment, the continuation chain segment, and the following chain segment, then perform chain segment splicing according to the result type, and then verify the continuation result through the preceding and following adjacency matrix and field fingerprint sequence. Finally, the stable thread group is written into the lifecycle link and the corresponding chain segment is extracted according to the result type. This implementation process includes the following steps: First, S51 is used to unify the current object set, corresponding continuation result, object set before change, lifecycle link, and digital thread segment into a reproducible structure. The input includes the current object set, corresponding continuation result, object set before change, lifecycle link, digital thread segment, and unified field order. The processing action is as follows: expand each input object according to the unified field order, which is fixed as component identifier, installation location, responsible entity, accounting attribution, usage status, succession order, and continuation type. Establish a thread continuation table with the object identifier before change, the current object identifier, the succession order, and the continuation type as connection fields. Among them, the chain segment in the lifecycle link that is before the current change is recorded as the preceding chain segment, the chain segment in the digital thread segment that is consistent with the corresponding continuation result is recorded as the continuation chain segment, and the chain segment in the lifecycle link that is after the current change is recorded as the following chain segment. The preceding, continuing, and following segments are written to the predecessor, current, and successor fields of the thread continuation table, respectively. The output includes the preceding, continuing, and following segments corresponding to each object before the change, for S52 to read. If an object before the change has no historical preceding segment, it is written to the thread continuation table as a preceding empty segment. If a current object only corresponds to a newly added item, a thread continuation table is generated using preceding and following empty segments. If the same object before the change corresponds to multiple continuing segments, all segments are retained and written to the thread continuation table in order of succession. Secondly, S52 is used to concatenate the preceding chain segment, the continuing chain segment, and the following chain segment into a continuation thread group based on the thread continuation table; the input includes the preceding chain segment, the continuing chain segment, and the following chain segment in each thread continuation table; the processing actions are as follows: sort each thread continuation table according to the order of succession, and perform chain segment concatenation in sequence; when the continuing chain segment corresponds to the merge result, perform single chain insertion on a preceding chain segment, a continuing chain segment, and a following chain segment according to the order of succession to generate a single chain continuation result; when the continuing chain segment corresponds to the split result, perform branch insertion on a preceding chain segment and multiple continuing chain segments according to the order of succession, and then connect each continuing chain segment to the corresponding following chain segment to generate a branch continuation result; When a continuation segment corresponds to a termination result, the preceding segment is connected to the termination write segment, and the subsequent segment is not connected. The termination position and termination reason are written in the termination write segment. The above single-chain continuation results, branch continuation results, and termination write results are respectively assigned to the continuation thread group. The output includes the continuation thread group for S53 to read. If the same preceding segment corresponds to both single-chain insertion and branch insertion, the single-chain insertion result is written first, followed by the branch insertion result, in the order of continuation. If the subsequent segment is missing, the continuation segment is retained as the terminal segment, and the subsequent segment is not reconstructed. Next, S53 is used to perform chain-by-chain verification on the continuation thread group, delete continuation chain segments that do not meet the continuation rules, and output a stable thread group; the input includes the continuation thread group; the processing action is as follows: construct the preceding and following adjacency matrix and field fingerprint sequence for each continuation thread group, where the rows and columns of the preceding and following adjacency matrix correspond to each chain segment, the matrix element is 1 when two chain segments can be connected, otherwise it is 0; the field fingerprint sequence is generated by concatenating the component identifier, responsible entity, accounting attribution, and usage status in a unified field order and then performing hash mapping, the hash input order is fixed. Unchanged; chain-by-chain verification is performed according to the rules of chain segment connection, succession order, field fingerprint correspondence, and branch destination uniqueness. Among them, when the tail identifier of the previous chain segment is equal to the head identifier of the next chain segment, the chain segment connection is considered to be established. When the succession order of the next chain segment is equal to the succession order of the previous chain segment plus one, the succession order is considered to be established. When adjacent chain segments share the same field fingerprint or are in the rewrite relationship of the current change record declaration, the field fingerprint correspondence is considered to be established. When the starting point of the same branch does not repeatedly point to the same current object, the branch destination uniqueness is considered to be established. For a continuation thread group that does not meet any of the rules, delete the corresponding continuation chain segment and only reconstruct the adjacent matrix elements of the previous and next adjacent segments that are adjacent to the deleted continuation chain segment; perform chain-by-chain verification in a loop until no continuation chain segment is deleted in a round of verification, and output a stable thread group for S54 to read; if a continuation thread group only has the previous chain segment after reconstruction, then the continuation thread group is retained as the terminated thread group; if the main diagonal of the previous and next adjacent matrix has a reachable value, it is determined that there is a chain loop, the last written continuation chain segment is deleted and the previous and next adjacent matrix is ​​reconstructed; Finally, S54 is used to write stable thread groups into the lifecycle link, generate updated digital threads, and extract five types of results. The input includes stable thread groups, lifecycle links, and result extraction fields. The processing actions are as follows: each stable thread group is written back to the corresponding lifecycle link according to the object identifier before the change. Among them, the single chain continuation result is written to the main chain position, the branch continuation result is written to the branch chain position, and the terminated thread group is written to the link termination position. After writing, the updated digital thread is generated. Then, the corresponding chain segments are extracted from the updated digital thread according to the component identifier, responsible entity, accounting attribution, usage status, and acceptance order. Among them, the chain segment corresponding to the maintenance continuation result is extracted as the maintenance traceability result, the chain segment corresponding to the value continuation result is extracted as the depreciation continuation result, the chain segment corresponding to the rewriting of the responsible entity and installation location is extracted as the allocation processing result, the chain segment corresponding to the rewriting of the sealed and activated status in the usage status chain segment is extracted as the sealed and activated result, and the chain segment corresponding to the termination result and the disposal continuation result is extracted as the scrapping judgment result. The output includes updated digital threads, maintenance traceability results, depreciation continuation results, transfer processing results, storage and activation results, and scrapping determination results. If the current change record corresponds to only one type of result, only the corresponding result item will be output. If the same chain segment meets the extraction conditions for multiple types of results at the same time, the corresponding result items will be copied and written in the order of maintenance continuation results, value continuation results, responsible entity rewriting results, usage status rewriting results, and termination results, without deleting the original chain segment. Through the above processing, S5 formally connects the current object set and corresponding continuation results to the life cycle link, forming an updated digital thread with a complete structure, clear branches, and complete verification. This ensures that maintenance traceability, depreciation continuation, transfer processing, storage activation, and scrapping determination all have clear chain segment sources, avoiding problems such as unclosed continuation relationships, non-unique branch destinations, and unclear result extraction boundaries. In practical applications: When a target asset undergoes a change involving simultaneous control board takeover, communication unit split takeover, and heat dissipation component termination, a thread continuation table is first established using the object identifier before the change, the current object identifier, the takeover order, and the continuation type. Then, the continuation chain segment corresponding to the control board is inserted into the main chain as a single chain, the continuation chain segment corresponding to the communication unit is inserted into the branch chain as a branch chain, and the termination chain segment corresponding to the heat dissipation component is written to the termination position. Subsequently, an adjacency matrix and field fingerprint sequence are constructed to delete continuation chain segments that do not satisfy the conditions of head-to-tail connection and continuous takeover order, resulting in a stable thread group. Finally, the stable thread group is written into the lifecycle link to form an updated digital thread, and the maintenance traceability results corresponding to the control board, the depreciation continuation results corresponding to the accounting continuation, the transfer processing results corresponding to the change of responsible entity, the sealing and activation results corresponding to the status rewriting, and the scrapping judgment results corresponding to the termination of the heat dissipation component are extracted respectively.

[0022] Furthermore, the present invention also includes a full lifecycle management system for equipment and fixed assets, the system comprising an alignment module, a dismantling module, a receiving module, a continuing subdivision module, and a continuing connection module: The alignment module is used to obtain the target asset's historical records, current composition records, and current change records before the current change. It performs alignment based on component identification, installation location, responsible party, accounting attribution, and usage status, and outputs the object set before the change, the composition difference set, and the change item set. The disassembly module is used to extract corresponding record items for each object before the change according to the continuation of use, maintenance, value and disposal, and to perform disassembly according to the retained part, removed part, added part and replaced part, and output the continuation sub-item set; The acceptance module is used to match the continuation sub-items set with the change item set item by item, and to perform comparison in the order of consistent component destination, installation location continuation, responsible entity acceptance, accounting attribution acceptance, and usage status continuation, and output the acceptance result set corresponding to each current object; The continuation module is used to merge continuation items that are inherited to the same current object, split continuation items that are inherited to different current objects, mark the uninherited continuation items as terminated, write the corresponding number thread fragment, and output the current object set and the corresponding continuation results based on the inherited result set. The continuation module is used to write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, perform continuation on each digital thread segment, generate the updated digital thread, and output maintenance traceability results, depreciation continuation results, transfer processing results, storage and activation results, or scrapping determination results.

[0023] Working principle: This solution first aligns historical records, current composition records, and current change records under the same field order, distinguishing which content is continuously retained from the original and which content is newly added, moved out, replaced, or rewritten. Then, it breaks down the pre-change objects into four categories of continuation items: usage continuation, maintenance continuation, value continuation, and disposal continuation, and matches each item with the current change content to determine which current object these continuation items should be attached to. Subsequently, content attached to the same current object is merged, content attached to different current objects is split, and content that cannot be attached is terminated and written to the corresponding digital thread fragment. Finally, these digital thread fragments are continued into the original lifecycle link to form an updated digital thread, from which maintenance traceability results, depreciation continuation results, allocation processing results, storage and activation results, and scrapping determination results are extracted. The key to this approach is that it no longer simply relies on asset numbers to determine if it is the same object, but rather determines which management significance is continued, split, or terminated based on the actual attachment relationship before and after the change. For example, a hospital's large imaging equipment undergoes a core detection component replacement during use, while the original communication unit is removed and installed on a backup device, and the original heat dissipation assembly is decommissioned. In this scenario, this solution first comprehensively analyzes the imaging equipment's historical records, current hardware configuration, and current change records to identify the records corresponding to the original detection component, the new detection component, the communication unit removal record, and the heat dissipation assembly decommissioning record. Then, it breaks down the original equipment's usage relationships, maintenance responsibilities, accounting value, and disposal status into continuation items. It then determines whether the detection component-related continuation items continue to be handled by the current main equipment, the communication unit-related continuation items are transferred to the backup device, and the heat dissipation assembly-related continuation items are no longer handled and are terminated. These results are then written into digital thread segments and reconnected to the original lifecycle link. In this way, the system can not only see what was replaced, removed, and decommissioned, but also further clarify which responsibilities still belong to the original equipment, which values ​​continue, which components have been transferred to other equipment, and which content has been terminated. This provides a clear and consistent basis for subsequent maintenance inquiries, depreciation processing, asset allocation, and scrapping audits.

[0024] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for full lifecycle management of equipment and fixed assets, characterized in that, include: S1. Obtain the target asset's historical records, current composition records, and current change records before the current change. Perform same-item alignment by component identifier, installation location, responsible entity, accounting attribution, and usage status. Output the object set before the change, the composition difference set, and the change item set. S2. For each object before the change, extract the corresponding record items according to continued use, continued maintenance, continued value and continued disposal, and perform decomposition according to the retained part, removed part, added part and replaced part, and output the continued item set; S3. Match the continued sub-items set with the change item set item by item, and perform the comparison in the order of consistent component destination, continued installation location, responsible entity, account attribution, and continued usage status, and output the acceptance result set corresponding to each current object; S4. Based on the inherited result set, merge the continuation items that are inherited to the same current object, split the continuation items that are inherited to different current objects, mark the uninherited continuation items as terminated, write the corresponding number thread fragment, and output the current object set and the corresponding continuation result. S5. Write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, perform continuation on each digital thread segment, generate the updated digital thread, and output the maintenance traceability result, depreciation continuation result, transfer processing result, storage and activation result or scrapping judgment result.

2. The method for full lifecycle management of equipment and fixed assets according to claim 1, characterized in that: S1 includes: S11. Expand the component identifier, installation location, responsible entity, accounting attribution and usage status in the historical record, current composition record and current change record according to a unified field order to generate a historical field sequence, a composition field sequence and a change field sequence, and establish an initial corresponding item set with record items that have the same component identifier and the same installation location. S12. For each record item in the initial corresponding item set, compare the responsible entity, accounting attribution, and usage status. Retain the record items with the same responsible entity, accounting attribution, and usage status as the direct corresponding item set. For record items with different responsible entities, accounting attribution, and usage status, split them before and after according to the values ​​before and after the change in the current change record to generate the split corresponding item set. S13. Merge the directly corresponding itemset and the split corresponding itemset according to the same field order, and output the object set before the change, the difference set, and the changed itemset. The object set before the change includes the continuous corresponding record items before the change, the difference set includes the newly added record items, the removed record items, and the replaced record items, and the changed itemset includes the field rewritten record items.

3. The method for full lifecycle management of equipment and fixed assets according to claim 2, characterized in that: S2 includes: S21. For each object before the change, extract the record items corresponding to the use continuation, maintenance continuation, value continuation and disposal continuation from the historical records, expand them in a unified field order, and generate the continuation record group corresponding to each object before the change. S22. Match each continuation record group with the constituent difference set item by item. Based on the consistency of component identification, the continuity of installation position, whether the responsible entity is retained, whether the accounting attribution is continued, and whether the usage status has changed, determine the retained part, removed part, added part, and replaced part in each continuation record group, and output the disassembly result group corresponding to each object before the change. S23. Merge the retained, removed, added, and replaced parts belonging to the use continuation, maintenance continuation, value continuation, and disposal continuation in each dismantling result group, and output the continuation sub-set corresponding to each object before the change.

4. The method for full life-cycle management of equipment and fixed assets according to claim 3, characterized in that: S3 includes: S31. Pair each continuation item in the continuation item set with each change item in the change item set according to a unified field order, and verify in turn whether the component destination is consistent, the installation location is continuous, the responsible entity takes over, the accounting is taken over, and the usage status is continuous. Only the paired items that have all the verifications are retained as candidate acceptance items. At the same time, the acceptance difference value corresponding to each candidate acceptance item is generated by summing the component position difference, location position difference, responsibility position difference, accounting position difference, and status position difference item by item. S32. Establish a connection graph with each continuing item and each current object as nodes on both sides and each candidate receiving item as connecting edge. For connecting edges that connect the same continuing item to multiple current objects or the same current object to multiple continuing items, sort and delete them in the order of receiving difference from small to large, number of items with consistent fields from large to small, and order of change position from front to back, and output the initial receiving edge set.

5. The method for full lifecycle management of equipment and fixed assets according to claim 4, characterized in that: S3 also includes: S33. Perform continuity check on the initial receiving edge set. Count the continuous items of installation location, responsible entity, accounting attribution and usage status between adjacent connecting edges along the connecting edge sequence corresponding to each current object. If the number of continuous items is less than the number of continuous items of the previous connecting edge, delete the next connecting edge and recalculate the corresponding connecting edge sequence until the number of continuous items in each connecting edge sequence no longer changes. Output a stable receiving edge set. S34. Merge the connecting edges in each stable receiving edge set according to the current object to generate the receiving result set corresponding to each current object. Each receiving result set includes the receiving continuation item identifier, the corresponding change item identifier, the receiving order, and the receiving difference.

6. The method for full lifecycle management of equipment and fixed assets according to claim 5, characterized in that: S4 includes: S41. Expand the result set according to the current object identifier and the continued sub-item identifier, and construct a merge matrix group and a split matrix group. The matrix element in the merge matrix group is generated by the bitwise product of the installation location continuation value, the responsible entity continuation value, the accounting attribution continuation value and the usage status continuation value. The matrix element in the split matrix group is composed of the location change amount, the entity rewrite amount, the accounting transfer amount and the status transfer amount in a unified field order to form a cost vector. S42. Perform matrix chain multiplication and transitive closure on each merge matrix group to generate a succession reachability table for each current object. Perform dynamic programming on each succession reachability table in the succession order, retain the succession chain whose succession item count is equal to the first one. If the succession item count is the same, retain the succession chain whose cumulative cost vector is arranged in the order of position change, main body rewrite, accounting transfer, and state transfer, and whose lexicographical order is equal to the first one. Output the merge segment set corresponding to each current object.

7. The method for full lifecycle management of equipment and fixed assets according to claim 6, characterized in that: S4 also includes: S43. Establish a continuous sub-item decomposition graph for each decomposition matrix group, construct the edge association matrix according to the acceptance order and perform maximum matching, delete conflicting connection edges that share the same acceptance result, and then perform prefix path accumulation and suffix path accumulation on the retained connection edges. Retain the decomposition path group whose sorting value of the number of covered acceptance results is equal to the first one and whose cumulative cost vector is lexicographically equal to the first one after being arranged in the order of position change, main body rewriting, accounting transfer, and status transfer. Output the decomposition segment set corresponding to each continuous sub-item. S44. Mark the continuation items that have not entered the merge segment set and the split segment set as termination items. Construct the result conflict matrix corresponding to the merge segment set, the split segment set and the termination items. Perform column-by-column resolution on the positions of multiple results corresponding to the same continuation item. Keep the result whose number of covered and received results is equal to the first one. If the number of covered and received results are the same, keep the result whose cumulative cost vector lexicographical order is equal to the first one. If the cumulative cost vector lexicographical order is the same, keep the result whose first item of the receiving order is equal to the first one. Update the result conflict matrix in a loop until all matrix elements in the result conflict matrix are zero. Then write the unique result into the corresponding digital thread segment and output the current object set and the usage continuation result, maintenance continuation result, value continuation result and disposal continuation result corresponding to each current object.

8. The method for full lifecycle management of equipment and fixed assets according to claim 7, characterized in that: S5 includes: S51. Expand the current object set, corresponding continuation result, object set before change, lifecycle link and digital thread fragment in a unified field order, establish a thread continuation table based on the object identifier before change, the current object identifier, the succession order and the continuation type, and output the preceding chain segment, continuation chain segment and following chain segment corresponding to each object before change. S52. Perform chain segment splicing on the preceding chain segment, continuing chain segment, and following chain segment in the continuation table of each thread according to the continuation order. Among them, the continuing chain segment corresponding to the merge result is single chain insertion, the continuing chain segment corresponding to the split result is branch insertion, and the continuing chain segment corresponding to the termination result is terminated and written. Output the continuation thread group.

9. A method for full lifecycle management of equipment and fixed assets according to claim 8, characterized in that: S5 also includes: S53. Construct the adjacency matrix and field fingerprint sequence for each continuation thread group. Perform chain-by-chain verification according to the rules of chain segment connection, continuous continuation order, corresponding field fingerprints, and unique branch destination. For continuation thread groups that do not meet the rules, delete the corresponding continuation chain segment and reconstruct the adjacency matrix. Output stable thread groups. S54. Write each stable thread group into the corresponding lifecycle link, generate the updated digital thread, and extract the corresponding chain segment from the updated digital thread according to the component identifier, responsible entity, accounting attribution, usage status and acceptance order, and output the maintenance traceability result, depreciation continuation result, transfer processing result, sealing and activation result or scrapping judgment result.

10. A lifecycle management system for equipment and fixed assets, used to implement the lifecycle management method for equipment and fixed assets as described in any one of claims 1-9, the system comprising an alignment module, a disassembly module, a receiving module, a continuing sub-module, and a continuing module, characterized in that: The alignment module is used to obtain the target asset's historical records, current composition records, and current change records before the current change. It performs alignment based on component identification, installation location, responsible party, accounting attribution, and usage status, and outputs the object set before the change, the composition difference set, and the change item set. The disassembly module is used to extract corresponding record items for each object before the change according to the continuation of use, maintenance, value and disposal, and to perform disassembly according to the retained part, removed part, added part and replaced part, and output the continuation sub-item set; The acceptance module is used to match the continuation sub-items set with the change item set item by item, and to perform comparison in the order of consistent component destination, installation location continuation, responsible entity acceptance, accounting attribution acceptance, and usage status continuation, and output the acceptance result set corresponding to each current object; The continuation module is used to merge continuation items that are inherited to the same current object, split continuation items that are inherited to different current objects, mark the uninherited continuation items as terminated, write the corresponding number thread fragment, and output the current object set and the corresponding continuation results based on the inherited result set. The continuation module is used to write the current object set and corresponding continuation results into the lifecycle link corresponding to each object before the change, perform continuation on each digital thread segment, generate the updated digital thread, and output maintenance traceability results, depreciation continuation results, transfer processing results, storage and activation results, or scrapping determination results.

Images