An electronic account management method based on standard cell groups

Abstract

The application discloses an electronic account management method based on a standard unit group. In order to solve the problem of inconvenient account management in the prior art, parts belonging to the same device component, having the same structure and function, using the same serial number on the drawing of the same device component, and the number of which exceeds a target number are recorded as standard part units of the same device component, and the standard part units and one or more accessories which are indivisible are recorded as a standard unit group as a whole. According to the selection and input information of a user, an account template of the standard unit group and an actual position distribution map of the standard unit group are established. In response to a viewing instruction of the unit group account of a first actual position by the user, general information of the standard unit group account template is displayed and provided to the user. In response to a modification request instruction of the unit group account of a second actual position by the user, an actual standard unit group account of the second actual position is generated. The application can effectively solve the problem of inconvenient account management.

Description

Technical Field

[0001] This application relates to an electronic ledger management method. Background Technology

[0002] In the power generation equipment, boiler heating surface headers and other equipment contain hundreds or thousands of identical parts (such as pipe fittings) with the same structure and function, distributed according to certain rules. These parts (pipe fittings) account for more than 95% of the total number of parts in the header structure. These structures are very simple, lack independent drawings, and cannot constitute elements in the equipment ledger; they can only be considered part units at the equipment level. During the power generation service life, some of these components require continuous inspection and modification, necessitating frequent changes to the part unit ledger for those locations. However, some locations do not require any inspection or modification during their service life, thus eliminating the need for any changes to the unit ledger.

[0003] Due to uncertainties in operating methods, usage environment, and equipment manufacturing, the specific location of an event is highly unpredictable. The exact location and location cannot be predicted. If hundreds or thousands of identical component units were all recorded in identical equipment unit ledgers, the number of ledgers would be enormous, resulting in extremely low efficiency. Conversely, if only unit ledgers are created for certain localized locations based on experience, no unit ledgers would be available when other locations require inspection or modification. Summary of the Invention

[0004] This application provides an electronic ledger management method based on standard unit groups, aiming to solve the problem of inconvenient ledger management in the prior art.

[0005] This application provides an electronic ledger management method based on standard unit groups, the method comprising:

[0006] Parts belonging to the same equipment component, having the same structure and function, using the same serial number on the drawings of the same equipment component, and exceeding the target quantity are recorded as standard part units of the same equipment component. Each standard part unit and one or more indivisible accessories are collectively recorded as a standard unit group. Based on user selections and input information, a ledger template and an actual location distribution map of the standard unit groups are created. The ledger template records the current general information of the standard unit group; the actual location distribution map of the unit group presents the actual locations of all units under that standard unit group.

[0007] In response to a user's command to view the unit group ledger at the first actual location, the ledger template of the standard unit group is invoked, the general information of the standard unit group ledger template is displayed and provided to the user; if an actual standard unit group ledger has already been formed, the actual standard unit group ledger is provided to the user.

[0008] In response to a user's request to modify the unit group ledger at the second actual location, the ledger template of the standard unit group is invoked to generate the actual standard unit group ledger at the second actual location. The initial information of the actual standard unit group ledger is the current general information of the standard unit group recorded in the ledger template. After the user makes modifications, the user's modifications are saved.

[0009] Optionally, in the above scheme, when a user views and modifies the unit group ledger, the human-computer interaction interface simultaneously displays the directory tree of the electronic ledger of the device or sub-device where the standard unit group is located, the ledger template, the actual standard unit group ledger, and the actual location distribution map of the unit group.

[0010] In the above scheme, optionally, the standard unit and the ordinary unit together constitute the equipment or sub-equipment of the next level. The ordinary unit is an independent part or part accessory that does not belong to the standard unit and whose quantity is less than the target quantity. The ordinary unit part and one or more indivisible accessories are collectively recorded as an ordinary unit group. The next level ledger of the equipment or sub-equipment includes the standard unit group ledger and the ordinary unit group ledger.

[0011] In the above scheme, optionally, the target quantity is 1.

[0012] Optionally, in the above scheme, the location information of the standard unit group is associated with the actual location distribution map of the unit group by numbering, and the numbering association is established by pre-automatic numbering association.

[0013] In the above scheme, optionally, a unit number is established for the standard unit group, and the standard unit group and the actual location distribution map of the unit group are associated by the unit number; the ledger template records the quantity information of the standard unit group on the actual location map of the unit group by the unit number, and after the actual standard unit group ledger is formed, the actual standard unit group ledger displays its specific location on the actual location distribution map of the unit group by the unit number.

[0014] In the above scheme, optionally, the unit number includes status, serial number, category, column number, and row number; the status is used to distinguish between standard unit groups and ordinary unit groups; the serial number is used to distinguish between different part units, corresponding to the serial number used on the drawing of the equipment component; the category is used to record the type of part or accessory; the column number and row number respectively record the specific column number and row number of the actual standard unit group on the actual position distribution diagram of the unit group, which together constitute the specific position information of the actual standard unit group.

[0015] Optionally, in response to a user's command to view the standard unit group ledger template, a list of standard unit group locations of the standard unit group ledger template is displayed and provided to the user.

[0016] Optionally, in the above scheme, when the standard unit group is updated, the general information in the ledger template of the standard unit group is updated, while the actual ledger at the specific location that has been saved remains unchanged.

[0017] Optionally, in the above scheme, when performing the same operation on multiple standard unit group ledgers in the same standard unit group ledger template, batch operation on multiple standard unit groups can be achieved by batch selecting the standard unit group location list.

[0018] Compared with the prior art, this application has at least the following beneficial effects:

[0019] This application, based on further analysis and research into the problems of existing technologies, recognizes that if hundreds or thousands of identical parts on the same component were all recorded as identical unit ledgers, the number of ledgers would be enormous, resulting in extremely low efficiency. Conversely, if ledgers were only created for certain local locations based on experience, no ledgers would be available when other locations require inspection or modification. This application addresses this by naming parts with the same structure and function, along with their indivisible accessories, as standard unit groups within a device component. A ledger template for each standard unit group is created, and when viewing the ledger for a specific unit group on the device, this template is provided to the user. When an inspection or modification operation is performed on a unit group ledger, the actual standard unit group ledger for that location is generated. This solves the problem of making all locations of the ledger operable while avoiding the creation of actual ledger content that is not operable. Attached Figure Description

[0020] Figure 1 This is a flowchart illustrating an electronic ledger management method based on standard unit groups, provided as an embodiment of this application.

[0021] Figure 2 A schematic diagram of a standard unit group electronic ledger provided in one embodiment of this application.

[0022] Figure 3 This is a schematic diagram of a newly added standard unit group provided in one embodiment of this application.

[0023] Figure 4 This is a schematic diagram of general information for input standard unit groups provided in one embodiment of this application.

[0024] Figure 5 This is a schematic diagram showing the completed input standard unit group according to one embodiment of this application.

[0025] Figure 6 This is a schematic diagram of a standard unit group ledger template provided in one embodiment of this application.

[0026] Figure 7This is a schematic diagram illustrating the batch selection of standard unit groups to be operated according to one embodiment of this application.

[0027] Figure 8 This is a schematic diagram illustrating the formation of an actual standard unit group ledger after batch operations are completed, as provided in one embodiment of this application.

[0028] Figure 9 This is a schematic diagram illustrating batch operations on standard units that have already formed an actual standard unit group ledger and standard units that have not yet formed an actual standard unit group ledger, as provided in one embodiment of this application.

[0029] Figure 10 This is a schematic diagram illustrating the individual standard unit operation of an actual standard unit group ledger, provided as an embodiment of this application.

[0030] Figure 11 This is a schematic diagram illustrating the operation of a standard unit group ledger template provided in one embodiment of this application. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0032] In the description of this application: unless otherwise stated, "a plurality of" means two or more. The terms "first," "second," "third," etc., in this application are intended to distinguish the objects referred to and do not have any special meaning in terms of technical connotation (e.g., they should not be construed as an emphasis on importance or order). Expressions such as "including," "comprising," and "having" also mean "not limited to" (certain units, components, materials, steps, etc.).

[0033] In power generation equipment, boiler heating surface headers contain hundreds or even thousands of identical pipe fittings with identical structures and functions. These pipe fittings account for over 95% of the header's structural components. These structures are very simple, lack independent drawings, and cannot constitute elements of the equipment ledger; they are merely component units at the equipment level. During the power generation lifespan, some of these components require continuous inspection and modification, necessitating frequent changes to the component unit ledger for those locations. Other locations require no inspection or modification during their service life, thus eliminating the need for any changes to the unit ledger. Because it's impossible to predict which pipe fittings will develop defects, it's difficult to pinpoint specific locations for modification. If all hundreds or thousands of pipe fittings were documented according to actual conditions, the number of unit ledger entries for the header would be enormous, resulting in very low efficiency and difficulty in identification. Conversely, if only some localized locations are documented based on experience, there are no records available when repairs or modifications are needed in other locations.

[0034] To resolve the aforementioned two types of contradictions, this application aims to utilize unit ledgers with connectors in any location while preventing the creation of actual ledgers without operable connectors, thereby reducing the actual number of unit ledgers, improving ledger utilization efficiency, and enhancing ledger identification. Embodiments of this application provide an electronic ledger management method based on standard unit groups, referencing... Figure 1 and Figure 2 The method includes:

[0035] Parts belonging to the same equipment component, having the same structure and function, using the same serial number on the drawings of the same equipment component, and exceeding the target quantity are recorded as standard part units of the same equipment component. This standard part unit and one or more indivisible accessories are collectively recorded as a standard unit group. Based on the user's selection and input information, a ledger template and a distribution map of the actual locations of the standard unit groups are established. The ledger template records the current general information of the standard unit group. The distribution map of the actual locations of the unit groups shows the actual locations of all units under the standard unit group.

[0036] In response to the user's command to view the unit group ledger at the first actual location, the ledger template of the standard unit group is invoked, the general information of the standard unit group ledger template is displayed and provided to the user; if an actual standard unit group ledger has already been formed, the actual standard unit group ledger is provided to the user.

[0037] In response to the user's request to modify the unit group ledger of the second actual location, the ledger template of the standard unit group is invoked to generate the actual standard unit group ledger of the second actual location. The initial information of the actual standard unit group ledger is the current general information of the standard unit group recorded in the ledger template. After the user makes modifications, the user's modifications are saved.

[0038] The boiler heating surface header is composed of hundreds or thousands of identical components (header pipe fittings). The standard unit group ledger is a form of equipment unit ledger formed using these hundreds or thousands of identical components as the carrier. Among the multiple identical components, there are both parts and indivisible accessories of parts; if a part or an accessory of a part is regarded as a standard unit, then at least one part and one accessory of that part can be regarded as a standard unit group. A standard unit group consists of two or more standard units; select any standard unit group as a template to establish the standard unit group ledger for that standard unit group, and attach a diagram showing the actual location distribution of the unit group.

[0039] Figures 3-5 This demonstrates the process of creating a standard unit group ledger template. After completing the creation of the unit group ledger template, refer to... Figure 5 or Figure 2 When viewing a component at a specific location, only the standard unit group template needs to be consulted. This template provides general information about the standard unit group. When operations are performed on a component at a specific location, such as modifications, a corresponding actual standard unit ledger for that location is generated. See details. Figure 2 .

[0040] exist Figure 2 In the system, the standard unit group template is distinguished from the ordinary unit group by the status "Z". The bold font indicates that the unit group is a standard unit group ledger template, and its column number and row number indicate the quantity range. When the actual unit group ledger is formed, the actual information is recorded in the lower row of the standard unit group ledger template in the equipment ledger to distinguish the content of the standard unit group ledger template.

[0041] In the actual standard unit group ledger, the unit name is named according to its actual location in the unit group's actual location distribution map. The row and column numbers of the actual standard unit group are also modified to match the row and column numbers in the actual location distribution map. For example... Figure 2 The row number and column number of “1 row 1 column fillet weld” are 1 and 1 respectively, representing the fillet weld unit in the first row and first column of the actual position distribution diagram of the unit group; the row number and column number of “1 row 2 column pipe seat” are 1 and 2 respectively, representing the pipe seat unit in the first row and second column of the actual position distribution diagram of the unit group.

[0042] In this embodiment, the application of standard unit groups can significantly reduce the number of ledgers that need to be managed. For example, if a set of equipment contains 400 standard units, these 400 standard units can form 200 standard unit groups (or 100 standard unit groups). In actual management, only 200 (or 100) ledgers need to be processed, instead of processing each of the 400 unit ledgers individually. Of course, in actual production processes, the situation will be more complex, but by setting up standard unit groups, the workload of users can still be greatly reduced.

[0043] In this embodiment, the first actual position and the second actual position are intended to describe a certain actual position in the two cases of viewing and modifying operations, respectively, and are not a special limitation on the actual position of the unit group; the unit group of the first actual position can be any unit group, and the unit group of the second actual position can also be any unit group. The unit group of the second actual position can be the same as the unit group of the first actual position, or it can be different.

[0044] In this embodiment, assuming that there are 198 units (unit groups) with the same serial number on a device component (drawing) that have the same structure and function, then it is not necessary to establish 198 unit groups at the beginning, but only to establish a ledger template; the actual ledger for that location will only be formed when the sub-device needs to be inspected or modified.

[0045] In one embodiment, when a user views and modifies the unit group ledger, the human-computer interaction interface simultaneously displays the directory tree of the electronic ledger of the device or sub-device where the standard unit group is located, the ledger template, the actual standard unit group ledger, and the actual location distribution map of the unit group.

[0046] In this embodiment, to ensure the responsiveness of the human-computer interaction interface, asynchronous loading and lazy loading techniques can be employed to ensure that core page functions (such as standard unit group ledger templates and actual standard unit group ledgers) can be presented to the user before all data is fully loaded. For non-critical data (such as detailed historical records), a lazy loading strategy can be used, loading this data only when explicitly requested by the user.

[0047] In one embodiment, front-end caching can also be introduced, utilizing the browser's local storage mechanisms (such as LocalStorage, SessionStorage) to cache frequently accessed data (such as the actual location distribution map of unit groups), reducing the number of server requests and improving access speed. For dynamically updated data, a reasonable cache expiration time is set to ensure data freshness, and the latest data changes are checked by periodic polling.

[0048] In one embodiment, standard units and ordinary units together constitute the next-level equipment or sub-equipment. Ordinary units are independent parts or parts that do not belong to standard units and whose quantity is less than the target quantity. Ordinary unit parts and one or more indivisible accessories are collectively referred to as ordinary unit groups. The next-level ledger of the equipment or sub-equipment includes the ledger of standard unit groups and the ledger of ordinary unit groups.

[0049] In boiler heating surface headers, in addition to multiple standard units and multiple standard unit groups, there are also multiple ordinary unit groups. Ordinary units are independent parts or parts accessories that do not belong to standard units and whose quantity is less than the target quantity. An ordinary unit part and one or more indivisible accessories are collectively recorded as an ordinary unit group. There are various types of unit ledgers at the equipment or sub-equipment level, including standard unit group ledgers and ordinary unit group ledgers. In the unit ledger, such as... Figure 2 As shown, ordinary units are distinguished by adding a "Z" before the unit number and by making the ledger font bold when displayed.

[0050] In one embodiment, the target quantity is 1.

[0051] In this embodiment, the target quantity can be any natural number other than 0. This application does not impose specific restrictions. In this embodiment, for ease of management, a unit group with a quantity exceeding 1 is usually defined as a standard unit group.

[0052] In one embodiment, the location information of the standard unit is associated with the actual location distribution map of the unit group by numbering, and the numbering association is established by pre-automatic numbering association.

[0053] In one embodiment, a unit number is established for the standard unit group, and the standard unit group and the actual location distribution map of the unit group are associated through the unit number; the ledger template records the quantity information of the standard unit group on the actual location map of the unit group through the unit number. After the actual standard unit group ledger is formed, the actual standard unit group ledger displays its specific location on the actual location distribution map of the unit group through the unit number.

[0054] In one embodiment, the unit number includes status, sequence number, category, column number, and row number; status is used to distinguish between standard unit groups and ordinary unit groups; sequence number is used to distinguish between different part units, corresponding to the sequence number used on the drawing of the equipment component; category is used to record the type of part or accessory; column number and row number respectively record the specific column number and row number of the actual standard unit group on the actual position distribution diagram of the unit group, which together constitute the specific position information of the actual standard unit group.

[0055] In this embodiment, reference Figure 2By associating the "Column Number" and "Row Number" columns of the "Unit Number" column in the actual standard unit group ledger with the specific location of that actual standard unit group ledger in the actual location distribution map of the unit group, for example, Figure 1 The “1 row 2 column fillet weld” with column number 2 and row number 1 corresponds to the fillet weld unit in the first row and second column of the actual position distribution diagram of the unit group.

[0056] In this embodiment, an initialization script or function can be triggered when the actual location distribution map of the sub-devices is first created or imported. This script will traverse all unit groups, assign a unique number to each unit group according to preset rules, and associate it with the corresponding entry in the directory tree path table. To ensure that the numbers and their associated information are correctly saved to the database, appropriate indexes are used to improve query efficiency. A dedicated number mapping table is established to store the relationship between numbers and unit groups.

[0057] In one embodiment, a strict access control system can also be set up, allowing only users with administrative privileges to perform manual numbering adjustments. This ensures that only authorized personnel can change critical numbering information. After a user submits a manual adjustment, the system automatically verifies the uniqueness and correctness of the number, ensuring that no duplicate or invalid numbers are generated. Once confirmed, the new number is immediately locked to prevent further modifications until the next change cycle.

[0058] In one embodiment, in response to a user's command to view the standard unit group ledger template, a list of standard unit group locations of the standard unit group ledger template is displayed and provided to the user.

[0059] In this embodiment, reference Figure 6 Since the standard unit group ledger template carries hundreds or thousands of identical standard unit groups within equipment components, this embodiment also provides a function to further facilitate viewing and management. Specifically, when a user wants to further understand the establishment status of the ledgers for each actual standard unit group under a certain standard unit group template, they can click on the standard unit group ledger template to display a pop-up window showing the location list of the standard unit groups within the template. In addition to displaying the location list, this pop-up window also provides information on the number of locations for each standard unit group.

[0060] For example Figure 6The pop-up window displays a list of standard unit group locations for serial number 3. Within this list, the background color of the corresponding cells reflects the status of the standard unit group inventory for that specific location. For example, a dark gray background in row 2, column 8 indicates no unit location exists, corresponding to the absence of a standard unit group in row 2, column 8 in the actual unit group location distribution map. Conversely, a white background in row 1, column 1 indicates the existence of a unit location, but it has not yet been included in the actual standard unit group inventory. This corresponds to the presence of a standard unit group in row 1, column 1 in the actual unit group location distribution map, but this standard unit group remains in its factory condition and has not been modified or repaired.

[0061] In one embodiment, the ledger template of the standard unit group and the actual location distribution map of the unit group are stored in the local database and the system database; the actual ledger of the second actual location is stored in the local database and submitted for approval. After approval, the actual ledger is updated in the system database.

[0062] In this embodiment, when a standard unit group is created or updated, its corresponding ledger template (containing general information) and the actual location distribution map of the unit group are simultaneously stored in both the local database and the system database. This ensures data synchronization between the two databases and provides basic information for subsequent operations.

[0063] When a user requests modifications to the unit group ledger at the second physical location, the system generates a new physical ledger record based on the existing ledger template. This new physical ledger record is first stored in the local database, awaiting further processing. Once the physical ledger record is created and stored in the local database, it enters an approval process. The relevant responsible person or team needs to review these changes to ensure that all modifications are accurate and necessary.

[0064] If approved, the actual ledger record will be synchronized from the local database to the system database, completing the final data update. This ensures that only verified data is updated to the system-level database, thus maintaining the data consistency and reliability of the entire system. If approved, the change will be returned to the original author for correction or rejected outright.

[0065] To avoid data conflicts during synchronization, priorities are set, such as prioritizing local modifications or the system database, to ensure that the correct version is automatically selected when conflicts occur. For complex conflicts that cannot be resolved automatically, a manual intervention channel is provided, allowing the administrator to determine the final solution.

[0066] Different user permissions are assigned to ensure that only authorized personnel can perform specific operations. For high-risk operations (such as approval submissions), users are required to provide additional authentication information to enhance security.

[0067] Add operation logs to record in detail all operations involving data changes, including who performed the operation, when it was performed, and what specific changes were made. Regularly review the operation logs to identify potential security issues.

[0068] A state machine model is used to cover all possible approval states (such as pending, approved, rejected, etc.), ensuring that each stage has a clear identifier. The approval process is automatically advanced according to preset rules, reducing human intervention and improving efficiency. When a new approval request arrives, a notification is automatically sent to the relevant approvers, reminding them to handle it promptly. A complete history of each approval is saved, including approvers' comments, approval time, and results, facilitating subsequent queries and accountability. Different approval chains can be configured according to different types of ledgers or business needs to meet diverse management requirements.

[0069] In one embodiment, the general information in the ledger template of the standard unit group is updated, while the actual ledger at the specific location that has been saved retains its original information.

[0070] In this embodiment, when the standard unit group is updated, the general information of all standard units that have not yet formed an actual standard unit group ledger is updated by updating the standard unit group ledger template. The actual standard unit group ledgers at specific locations that have already been saved retain their original information. (Reference) Figure 11 The fillet weld unit of the standard unit group with unit number "Z003J018011" can have its "non-destructive testing" type updated for all standard units that have not yet formed an actual standard unit group ledger by changing its "non-destructive testing" type to "RT".

[0071] In this embodiment, when the actual standard unit group ledger is modified, in response to the user's modification command, the ledger of the standard unit or standard unit group that needs to be modified is directly modified, referring to... Figure 10 , Figure 10 The last line shows the modification status of the standard unit in the actual standard unit group ledger.

[0072] When general information about a standard unit group (such as specifications and model) changes, these changes are first reflected in the standard unit group's ledger template. The ledger template serves as the source of basic information for all standard unit groups of the same type. Because the ledger template contains general information about the standard unit group, any modifications to the template are automatically applied to all ledgers based on that template that have not yet formed actual standard unit groups. This means that all standard unit group records not yet specified to a particular location will immediately reflect the latest changes.

[0073] For actual ledgers that have already saved specific location information, even if the general information in the ledger template changes, these actual ledgers for specific locations will still retain the original information. This ensures that the information of on-site installed or deployed equipment is not accidentally changed due to updates to the backend information. It also guarantees the integrity of historical data, allowing users to view the accurate configuration and status at any specific point in time.

[0074] In one embodiment, the overall update of individual location unit groups in the electronic ledger of equipment is achieved by updating the actual location distribution map of the unit groups.

[0075] In this embodiment, the overall update of individual unit groups in the electronic ledger is achieved by updating the actual location distribution map of the unit groups. When the information of a unit group at a specific location changes, the relevant electronic ledger information can be updated synchronously by modifying the actual location distribution map of that unit group. This ensures data consistency and accuracy and can efficiently reflect changes in physical equipment.

[0076] When a standard unit group in the equipment needs to be replaced, repaired, or upgraded, or its location changes, the unit group's actual location distribution map will be updated. First, the specific location requiring updating is determined, i.e., which unit group has changed. Then, the user edits the unit group's actual location distribution map for that location according to the actual situation. This includes adding new units, removing old units, and changing the position of existing units. Once the unit group's actual location distribution map is updated, the system automatically updates the corresponding equipment electronic ledger. All records related to a specific location (such as parts information, accessory information, maintenance history, etc.) will be adjusted according to the new location distribution map.

[0077] In this embodiment, any changes to the actual location distribution map of the unit group require approval.

[0078] In one embodiment, when performing the same operation on multiple standard unit group ledgers in the same standard unit group ledger template, batch operation on multiple standard unit groups can be achieved by batch selecting the standard unit group location list.

[0079] refer to Figures 5-8 , Figures 5-8 This demonstrates how to batch generate actual standard unit group ledgers using the standard unit group ledger template; you can also refer to... Figure 9 , Figure 9 The diagram illustrates the batch operation of standard units that have already formed actual standard unit group ledgers and those that have not yet formed actual standard unit group ledgers.

[0080] When performing the same operation on multiple actual standard unit group ledgers within a standard unit group, the desired unit group locations can be selected in batches from the standard unit group location list, enabling batch operations on multiple unit groups. (See reference diagram.) Figures 5-8 and Figure 9 .

[0081] Database transactions can be used to ensure that all related ledger records are processed as a whole during updates. If any step fails, the entire update operation is rolled back, maintaining data consistency.

[0082] In ledger management, due to the need to record and store large amounts of data, such as equipment information, operation records, and approval processes, and the potential for multiple users to operate simultaneously (e.g., multiple approvers approving ledgers at the same time, or multiple administrators querying data simultaneously), a multi-node system can be adopted in the ledger management system. This involves introducing a distributed locking mechanism to prevent data inconsistency caused by concurrent updates. This ensures that only one process can perform update operations on a specific unit group at a time. For complex update operations across multiple databases or systems, a two-phase commit protocol is used to ensure that all participants agree to and execute the update, or cancel it entirely, avoiding data inconsistency caused by partial successful updates.

[0083] Once the update is complete, a data verification process will be initiated immediately to confirm that the updated information has been correctly synchronized to all relevant ledger records. If any discrepancies are found, a correction process will be automatically triggered.

[0084] In one embodiment, the standard unit group specifically includes inlet and outlet headers for the heating surface of a power generation equipment boiler, modular water-cooled wall tube banks, and wall-mounted tube banks.

[0085] In one embodiment, a computer program product is also provided, including a computer program / instructions that, when executed by a processor, implement the steps of the methods described in the embodiments above.

[0086] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. An electronic ledger management method based on standard unit groups, characterized in that, include: Parts belonging to the same equipment component, having the same structure and function, using the same serial number on the drawings of the same equipment component, and exceeding the target quantity are recorded as standard part units of the same equipment component. The standard part unit and one or more indivisible accessories are recorded as a standard unit group. Based on the user's selection and input information, a ledger template for standard unit groups and a distribution map of the actual locations of standard unit groups are established. The ledger template records the current general information of the standard unit group; the actual location distribution map of the unit group shows the actual location of all units under the standard unit group. In response to a user's command to view the unit group ledger at the first actual location, the ledger template of the standard unit group is invoked, the general information of the standard unit group ledger template is displayed and provided to the user; if an actual standard unit group ledger has already been formed, the actual standard unit group ledger is provided to the user. In response to a user's request to modify the unit group ledger of the second actual location, the ledger template of the standard unit group is invoked to generate the actual standard unit group ledger of the second actual location. The initial information of the actual standard unit group ledger is the current general information of the standard unit group recorded in the ledger template. After the user makes modifications, the user's modifications are saved. That is, when viewing a component at a certain location, only the standard unit group template needs to be viewed, which provides the general information of the standard unit group. When an operation is performed on a component at a specific location, the actual standard unit ledger corresponding to that actual location is generated. When a standard unit group is created or updated, its corresponding ledger template containing general information and the actual location distribution map of the unit group will be stored in both the local database and the system database. When a user requests to modify the ledger of the unit group at the second actual location, the system will generate a new actual ledger record based on the existing ledger template. This new actual ledger record will first be stored in the local database.

2. The electronic ledger management method based on standard unit groups according to claim 1, characterized in that, Also includes: When a user views and modifies the unit group ledger, the human-computer interaction interface simultaneously displays the directory tree of the electronic ledger of the device or sub-device where the standard unit group is located, the ledger template, the actual standard unit group ledger, and the actual location distribution map of the unit group.

3. The electronic ledger management method based on standard unit groups according to claim 1, characterized in that, The standard units and ordinary units together constitute the equipment or sub-equipment of the next level. Ordinary units are independent parts or parts that do not belong to the standard units and whose quantity is less than the target quantity. Ordinary unit parts and one or more indivisible parts are collectively recorded as ordinary unit groups. The next level ledger of the equipment or sub-equipment includes the ledger of standard unit groups and the ledger of ordinary unit groups.

4. The electronic ledger management method based on standard unit groups according to claim 1 or 3, characterized in that, The target quantity is 1.

5. The electronic ledger management method based on standard unit groups according to claim 1, characterized in that, Also includes: The standard unit group is associated with the actual location distribution map of the unit group by numbering, and the numbering association is established by pre-automatic numbering.

6. The electronic ledger management method based on standard unit groups according to claim 5, characterized in that, Also includes: A unit number is established for the standard unit group, and the standard unit group and the actual location distribution map of the unit group are associated through the unit number; The ledger template records the quantity information of standard unit groups on the actual location map of the unit groups through the unit number. After the actual standard unit group ledger is formed, the actual standard unit group ledger displays its specific location on the actual location distribution map of the unit groups through the unit number.

7. The electronic ledger management method based on standard unit groups according to claim 6, characterized in that, Also includes: The unit number includes status, serial number, category, column number, and row number; the status is used to distinguish between standard unit groups and ordinary unit groups; the serial number is used to distinguish between different part units, corresponding to the serial number used on the drawings of equipment components; the category is used to record the type of part or accessory; the column number and row number respectively record the specific column number and row number of the actual standard unit group on the actual position distribution diagram of the unit group, which together constitute the specific position information of the actual standard unit group.

8. The electronic ledger management method based on standard unit groups according to claim 1, characterized in that, Also includes: In response to a user's command to view the standard unit group ledger template, a list of standard unit group locations in the standard unit group ledger template is displayed and provided to the user.

9. The electronic ledger management method based on standard unit groups according to claim 1, characterized in that, Also includes: When the standard unit group is updated, the general information in the ledger template of the standard unit group is updated, while the actual ledgers in the specific locations that have been saved retain the original information.

10. The electronic ledger management method based on standard unit groups according to claim 1, characterized in that, Also includes: When performing the same operation on multiple standard unit group ledgers in the same standard unit group ledger template, batch operations on multiple standard unit groups can be achieved by selecting the standard unit group location list in batches.

Images