Data storage method and system for maintenance project construction cost

Abstract

The invention discloses a data storage method and system for maintenance project construction cost, and relates to the field of information technology and data management.The method comprises the steps that maintenance project construction cost data form a data set; establishing a data standard and a coding rule; establishing a power grid maintenance project construction cost database system; and encrypting the project cost data in the power grid maintenance project project cost database system. The security of data is effectively improved by introducing an advanced multi-level encryption and key management system, and meanwhile, the data recovery capability of the system in the case of faults or disasters is remarkably enhanced in combination with a flexible data backup and recovery strategy. In addition, data access control is greatly optimized through fine-grained user permission management, and it is ensured that operation permissions of different levels of users are accurately distributed and strictly executed. The design not only improves the efficiency and safety of power grid maintenance project construction cost management, but also enhances the real-time performance and accuracy of data processing.

Description

Technical Field

[0001] The present invention relates to the technical fields of information technology and data management technology, and particularly to a data storage method and system for the project cost of maintenance items. Background Art

[0002] In the fields of data management and security technology, especially in the design of database systems for the project cost of power grid maintenance items, the technological development has achieved a transformation from traditional manual records and simple spreadsheet management to more complex database management systems. Modern database technology provides powerful data storage, query, and analysis functions, which are crucial for managing large-scale and complex power grid maintenance projects. With the rise of cloud computing and big data technology, real-time processing and analysis of data have become possible, greatly improving the efficiency and accuracy of project management. In addition, data security technologies, including encryption and access control, have evolved from simple password protection to complex multi-factor authentication and role-based access control systems (RBAC) to address the growing cyber security threats.

[0003] Although the existing technologies have made remarkable progress in terms of functionality and security, there are still some deficiencies, especially in aspects such as data backup and recovery strategies, encryption management, and fine-grained permission control. Existing project cost management systems for power grid maintenance items often lack flexible and efficient data backup and disaster recovery mechanisms, which may lead to irrecoverable losses of important data in the face of data center failures or natural disasters. In addition, although data encryption technology has been adopted, the management of encryption keys is often not strict enough, failing to effectively implement the periodic replacement of keys or achieve hierarchical management of keys in multi-level systems, increasing the risk of data leakage. At the same time, existing systems often cannot finely control the access to each data table or record in terms of user permission management, which limits the flexibility and scalability of the system. To address these problems, our invention provides a solution that integrates advanced encryption technology, multi-level user permission control, and powerful data backup and recovery functions. The system design not only improves the security of data and the stability of the system, but also effectively enhances the operation efficiency of the system and the availability of data through optimized permission management and flexible backup strategies, solving the key technical bottlenecks existing in the prior art. Summary of the Invention

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

[0005] Therefore, the technical problem solved by the present invention is as follows: The present invention aims to solve the problems of data security, insufficient backup, and imprecise permission control existing in the project cost management of power grid maintenance projects. Specifically, the present invention implements a multi-level encryption and key management strategy to ensure the security of data during storage and transmission; introduces a flexible and efficient data backup and recovery mechanism to cope with the risks of data loss or system failures; and precisely manages the access and operation permissions of different-level users to data through a fine-grained user permission control system, thereby improving the accuracy of data management and the overall security of the system.

[0006] To solve the above technical problems, the present invention provides the following technical solutions: A data storage method for the project cost of maintenance projects, which includes the following steps,

[0007] Collect maintenance project cost data to form a data set; establish data standards and coding rules; establish a database system for the project cost of power grid maintenance projects; encrypt the project cost data in the database system for power grid maintenance projects.

[0008] As a preferred solution of a data storage method for the project cost of maintenance projects according to the present invention, wherein: The maintenance project cost data includes collecting data from the information system and screening out information related to the maintenance project from the data.

[0009] The formation of the data set includes cleaning incomplete, incorrect or inconsistent data entries, standardizing formats and units, merging the same type of data from different sources, converting unstructured data into structured data, defining attribute tags for each data point, establishing the relevance between data points, and integrating all processed data into a unified data set.

[0010] As a preferred solution of a data storage method for the project cost of maintenance projects according to the present invention, wherein: The establishment of data standards and coding rules includes formulating unified data format, data type and data length standards according to the data types and business requirements in the data set.

[0011] The data format uses the ISO8601 standard format.

[0012] Determine the data type to be used for each field and set the corresponding length limit for each field.

[0013] The coding rule assigns a unique identifier to each record in the data set and establishes a hierarchical coding according to the business logic relationship.

[0014] As a preferred solution of the data storage method for the project cost of maintenance items described in the present invention, wherein: the establishment of the power grid maintenance project cost database system includes designing an entity-relationship model based on a standardized and coded data set, and identifying all entities and relationships.

[0015] Convert the entity-relationship model into a specific database model, design the table structure, and determine the primary key, foreign key, and index.

[0016] Select a database management system and design the physical storage structure of the table according to performance requirements.

[0017] Create a database in the selected database management system, establish data tables, and define fields and data types.

[0018] Import the standardized data into the database and create views and indexes.

[0019] Set user roles and permissions, encrypt the stored and transmitted data, formulate a data backup plan, and a data recovery process.

[0020] As a preferred solution of the data storage method for the project cost of maintenance items described in the present invention, wherein: the setting of user roles and permissions includes defining the role and permission hierarchy, assigning user permissions through roles, and each role has different data access and operation permissions according to the hierarchy division, and dynamically determines the access permissions according to user attributes, operation types, and data attributes.

[0021] The roles include a global administrator, a department key administrator, and a project manager.

[0022] The global administrator is responsible for generating and distributing the root key, which is used to encrypt other keys, and fully manages the root certificate and issued certificates of TLS / SSL.

[0023] The department key administrator manages the department-level keys, which are used to encrypt sensitive data within the department, and is responsible for performing key rotation and operating according to the guidance and policies of the global administrator.

[0024] The project manager can request to reset the data encryption key related to the project with the approval of the department key administrator, but cannot directly access the key and can only use the key through the encryption service.

[0025] When a user attempts to access sensitive data, the permission assignment module first checks the user's role and the permission level related to the requested operation.

[0026] If the user is a global administrator, access and operation of all data and functions are allowed, including the generation and distribution of encryption keys.

[0027] If the user is a department key administrator, the permission allocation module checks whether the requested data belongs to the department under their management.

[0028] If it belongs, data encryption operations and key rotation are allowed; if not, the request is rejected, and corresponding error logs or warning messages are generated.

[0029] If the user is a project manager and requests to reset the data encryption key, the permission allocation module automatically sends an approval request to the department key administrator.

[0030] If the department key administrator approves the request, the project manager indirectly uses the new encryption key through the encryption service. The project manager cannot directly access the key and uses the key through the existing encryption service interface.

[0031] If the department key administrator rejects the request, the project manager will not be able to access the new key and cannot perform encryption or decryption operations.

[0032] Record the user information, time, operation type, and result of each data operation.

[0033] Conduct system audits regularly to check whether the implementation of permissions complies with policies and regulations.

[0034] As a preferred solution of the data storage method for the project cost of maintenance items described in the present invention, wherein: the encryption of the stored and transmitted data includes that before the data is stored in the database, the data encryption and security module automatically checks the classification label of the data. If the data is marked as sensitive data, the AES encryption algorithm is triggered to encrypt the data;

[0035] During the data transmission process, the TLS / SSL protocol is uniformly used for encryption.

[0036] The global administrator sets the key rotation period according to the organization's security policy. The data encryption and security module automatically monitors the usage duration of the key. When the rotation period arrives, a key rotation task is automatically generated, and the global administrator is notified for review.

[0037] When the global administrator approves the key rotation, the department key administrator receives the rotation instruction. The department key administrator needs to evaluate the data scope and related business processes affected by the key rotation and execute the key rotation to re-encrypt all sensitive data.

[0038] After re-encryption, necessary tests are conducted to verify the availability and integrity of the data.

[0039] After the key rotation is completed, the department key administrator needs to notify all affected project managers that the key has been updated.

[0040] When the project manager needs to reset the data encryption key related to the project, the data encryption and security module passes the request to the department key administrator for review.

[0041] If the department key administrator approves, the project manager will indirectly obtain a new encryption key through the encryption service to perform encryption and decryption operations on relevant data.

[0042] If the department key administrator does not approve the request, the project manager will not be able to perform any key-related operations.

[0043] During the encryption process, the data encryption and security module determines whether there is any abnormal activity related to key operations by comparing normal behavior patterns.

[0044] If there are abnormal login behaviors, abnormal data access models, unauthorized system operations, and abnormal network traffic patterns in the abnormal activities, it indicates the existence of abnormalities or potential security threats.

[0045] If there are malicious code attacks and system intrusions in the abnormal activities, it indicates the existence of security incidents.

[0046] When detecting abnormalities or potential security threats, the security monitoring module will immediately trigger an alarm and send relevant information to the system administrator.

[0047] When detecting a security incident, the current key will be automatically marked as a risk key, and relevant logs of key usage will be recorded, including user, operation type, operation time, and IP address information.

[0048] After triggering the alarm, immediately notify the global administrator of the risk status of the current key.

[0049] After receiving the alarm, the data encryption and security module provides a detailed risk report for the global administrator to review.

[0050] The global administrator evaluates the severity of the security incident based on the detailed information in the risk report.

[0051] For a single abnormal access attempt, the administrator can choose to temporarily suspend the use of the key for further review or perform key re-authentication, which is defined as low risk.

[0052] If the key is leaked or maliciously tampered with, the administrator needs to immediately take remedial measures, which is defined as high risk.

[0053] If the event is evaluated as high risk and the threat has been proven to exist, the administrator should immediately perform a key rotation operation.

[0054] If the system needs to restore the access rights of the original data after key rotation, the administrator will restore the access to sensitive data by restoring the backed-up key or through a re-encryption process.

[0055] As a preferred solution of the data storage method for the project cost of maintenance items described in the present invention, wherein: the formulation of the data backup plan includes selecting the corresponding backup type according to the different types and importance levels of the data, determining the backup frequency and specific time, and regularly performing recovery tests to verify the integrity of the backup data and the effectiveness of the actual recovery process.

[0056] Another object of the present invention is to provide a data storage system for the project cost of maintenance items, which can solve the problems of low efficiency, easy error and poor timeliness of existing manual data processing by implementing automated data integration and real-time analysis functions.

[0057] To solve the above technical problems, the present invention provides the following technical solution: A data storage system for the project cost of maintenance items includes a data integration module, a database design and management module, a permission allocation module, a data encryption and security module, and a data backup and recovery module.

[0058] The data integration module is responsible for collecting and organizing the relevant data of the maintenance project and standardizing and structuring the data.

[0059] The database design and management module is responsible for designing the table structure, data fields and indexes of the database and managing the storage, update and maintenance of the data.

[0060] The permission allocation module defines different user roles and corresponding permission levels, and controls the data access rights and operation rights of various users.

[0061] The data encryption and security module is responsible for the encryption protection of the data during storage and transmission.

[0062] The data backup and recovery module formulates and implements a data backup strategy, including full backup, incremental backup and differential backup, and designs and executes a data recovery process.

[0063] A computer device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of the data storage method for the project cost of maintenance items as described above are implemented.

[0064] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data storage method for the project cost of maintenance items as described above are implemented.

[0065] Advantages of the present invention: By introducing an advanced multi-level encryption and key management system, the data security is effectively improved. At the same time, combined with a flexible data backup and recovery strategy, the data recovery ability of the system in the face of failures or disasters is significantly enhanced. In addition, the fine-grained user privilege management greatly optimizes the data access control, ensuring that the operation privileges of users at different levels are accurately allocated and strictly enforced. These designs not only improve the efficiency and security of the project cost management of power grid maintenance projects, but also enhance the real-time performance and accuracy of data processing, thus providing a power grid company with an efficient, secure and easy-to-manage project cost information system, effectively supporting the high-quality completion of cost control and decision-making analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0067] Figure 1 FIG. is the overall flowchart of a data storage method for the project cost of maintenance projects provided by the first embodiment of the present invention.

[0068] Figure 2 FIG. is the overall framework diagram of a data storage system for the project cost of maintenance projects provided by the second embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0069] To make the above objects, features and advantages of the present invention more obvious and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings of the specification. Obviously, the described embodiments are some embodiments of the present invention, rather than all embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of protection of the present invention.

[0070] Embodiment 1, referring to Figure 1 , which is an embodiment of the present invention, provides a data storage method for the project cost of maintenance projects, characterized in that:

[0071] S1: The project cost data of the maintenance project is formed into a data set.

[0072] The project cost data of the maintenance project includes collecting data from the information system and screening out the information related to the maintenance project from the data.

[0073] Forming a data set includes cleaning incomplete, incorrect, or inconsistent data entries, standardizing formats and units, merging the same type of data from different sources, converting unstructured data into structured data, defining attribute tags for each data point, establishing associations between data points, and integrating all processed data into a unified data set.

[0074] S2: Establish data standards and coding rules.

[0075] Establishing data standards and coding rules includes formulating unified data formats, data types, and data length standards according to the data types and business requirements in the data set.

[0076] The data format uses the ISO8601 standard format.

[0077] Determine the data types to be used for each field and set corresponding length limits for each field.

[0078] The coding rule assigns a unique identifier to each record in the data set and establishes a hierarchical coding based on business logic relationships.

[0079] The present invention aims at the systematic management of data. By formulating unified data formats (using the ISO8601 standard format), data types, and data length standards, it ensures the consistency and interoperability of data in the entire power grid system. In particular, the design of hierarchical coding assigns a unique identifier to each record in the data set, optimizing data tracking and management. The establishment of these standards and rules not only improves the standardization level of data processing but also enhances data security and maintainability.

[0080] S3: Establish a database system for the project cost of power grid maintenance projects.

[0081] Establishing a database system for the project cost of power grid maintenance projects includes designing an entity-relationship model based on the standardized and coded data set and identifying all entities and relationships.

[0082] Convert the entity-relationship model into a specific database model, design the table structure, determine the primary key, foreign key, and index.

[0083] Select a database management system and design the physical storage structure of the table according to performance requirements.

[0084] Create a database in the selected database management system, establish data tables, and define fields and data types.

[0085] Import the standardized data into the database and create views and indexes.

[0086] Set user roles and permissions, encrypt the data during storage and transmission, formulate a data backup plan and a data recovery process.

[0087] Setting user roles and permissions includes defining role and permission hierarchies, assigning user permissions through roles, where each role has different data access and operation permissions according to the hierarchical division, and dynamically determining access permissions based on user attributes, operation types, and data attributes.

[0088] Among them, the roles include global administrators, department key administrators, and project managers.

[0089] Global administrators are responsible for generating and distributing root keys, which are used to encrypt other keys, and have full authority to manage the root certificates of TLS / SSL and issue certificates.

[0090] Department key administrators manage keys at the department level, which are used to encrypt sensitive data within the department, and are responsible for performing key rotation, operating according to the guidance and policies of global administrators.

[0091] Project managers can request to reset project-related data encryption keys with the approval of department key administrators, but cannot directly access the keys and can only use the keys through encryption services.

[0092] When a user attempts to access sensitive data, the permission assignment module first checks the user's role and the permission level related to the requested operation.

[0093] If the user is a global administrator, access and operation of all data and functions are allowed, including the generation and distribution of encryption keys.

[0094] If the user is a department key administrator, the permission assignment module checks whether the requested data belongs to the corresponding managed department.

[0095] If it belongs, data encryption operations and key rotation are allowed; if not, the request is rejected, and corresponding error logs or warning messages are generated.

[0096] If the user is a project manager and requests to reset the data encryption key, the permission assignment module automatically sends an approval request to the department key administrator.

[0097] If the department key administrator approves the request, the project manager indirectly uses the new encryption key through the encryption service. The project manager cannot directly access the key and uses the key through the existing encryption service interface.

[0098] If the department key administrator rejects the request, the project manager will not be able to access the new key and will also be unable to perform encryption or decryption operations.

[0099] Record the user information, time, operation type, and result of each data operation.

[0100] Conduct system audits regularly to check whether the implementation of permissions complies with policies and regulations.

[0101] Furthermore, sensitive data includes, but is not limited to, personal or corporate privacy data such as employee information including, but not limited to, personal identity data such as employee names, contact information, ID numbers, salaries, positions, bank accounts, etc.

[0102] Supplier and contractor information, such as supplier names, contact information, contract details, payment information, etc., involves corporate trade secrets and information of business partners.

[0103] Engineering budget and cost data, including cost analysis of projects, cost estimates, actual expenditures, budget execution, etc.

[0104] Settlement data, including payment records, bills, payment details, etc. related to projects, which are crucial for the company's financial operations.

[0105] Profit and loss analysis: Involves financial statements, cost-benefit analysis, etc.

[0106] Engineering plans and schedules, including construction plans, schedules for maintenance projects, costs and resource allocations for each stage of the project.

[0107] Engineering technical data, including design drawings, technical parameters, equipment selection, construction plans, etc. of the project. These data contain technical details of the project, and leakage may lead to technology theft or project damage.

[0108] Encryption keys, including master keys, sub-keys for encrypting sensitive data, and keys generated during all encryption operations. Once these keys are leaked, it may lead to the leakage of all encrypted data.

[0109] Identity authentication information, such as usernames, passwords, tokens, etc. used for system access control. Leaking this data will result in unauthorized access to the system.

[0110] Furthermore, at this stage, the present invention realizes the precise design of the entity-relationship model through a data set based on standard purification and encoding. By converting the entity-relationship model into a specific database model, the present invention optimizes the table structure of the database, establishes primary keys, foreign keys, indexes, selects a suitable database management system, and designs the physical storage structure of the tables according to performance requirements. The establishment of this system not only improves the efficiency of data query, but also guarantees the structure and scalability of the data.

[0111] Furthermore, the innovation of the present invention is that by introducing a "data classification label" mechanism, before data storage, it automatically detects and marks whether the data is sensitive data. If the data is marked as sensitive data, automatic encryption will be triggered. This process not only targets the storage process but also involves the encryption of the data transmission process, using the unified TLS / SSL protocol for encryption, thus ensuring the security of the entire storage and transmission process.

[0112] The present invention introduces multi-level role management. In addition to the global administrator and project manager, the role of "department key administrator" is defined to specifically manage the encryption of sensitive data and key rotation. This role hierarchy not only refines the division of permissions but also dynamically adjusts access permissions according to different levels of roles, ensuring more precise security management of data.

[0113] S4: Encrypt the project cost data in the project cost database system for power grid maintenance projects.

[0114] Encrypting the stored and transmitted data includes that before the data is stored in the database, the data encryption and security module automatically checks the classification label of the data. If the data is marked as sensitive data, the AES encryption algorithm is triggered to encrypt the data;

[0115] During the data transmission process, the TLS / SSL protocol is uniformly used for encryption.

[0116] The global administrator sets the key rotation period according to the organization's security policy. The data encryption and security module automatically monitors the usage duration of the key. When the rotation period arrives, a key rotation task is automatically generated and the global administrator is notified for review.

[0117] When the global administrator approves the key rotation, the department key administrator receives the rotation instruction. The department key administrator needs to evaluate the data scope and related business processes affected by the key rotation and execute the key rotation to re-encrypt all sensitive data.

[0118] After re-encryption, necessary tests are carried out to verify the availability and integrity of the data.

[0119] After the key rotation is completed, the department key administrator needs to notify all affected project managers that the key has been updated.

[0120] When the project manager needs to reset the data encryption key related to the project, the data encryption and security module will pass the request to the department key administrator for review.

[0121] If approved by the department key administrator, the project manager will indirectly obtain a new encryption key through the encryption service to perform encryption and decryption operations on the relevant data.

[0122] If the department key administrator does not approve the request, the project manager will not be able to perform any key-related operations.

[0123] During the encryption process, the data encryption and security module determines whether there is any abnormal activity related to key operations by comparing normal behavior patterns.

[0124] If there are abnormal login behaviors, abnormal data access models, unauthorized system operations, and abnormal network traffic patterns in the abnormal activities, it indicates the existence of abnormal or potential security threats.

[0125] If there are malicious code attacks and system intrusions in the abnormal activities, it indicates the existence of a security incident.

[0126] When an abnormal or potential security threat is detected, the security monitoring module will immediately trigger an alarm and send the relevant information to the system administrator.

[0127] When a security incident is detected, the current key will be automatically marked as a risky key, and the relevant logs of key usage will be recorded, including user, operation type, operation time, and IP address information.

[0128] After the alarm is triggered, the global administrator will be immediately notified of the risk status of the current key.

[0129] After receiving the alarm, the data encryption and security module provides a detailed risk report for the global administrator to review.

[0130] The global administrator evaluates the severity of the security incident based on the detailed information in the risk report.

[0131] If it is a single abnormal access attempt, the administrator can choose to temporarily suspend the use of the key and conduct further review, or perform key re-authentication, which is defined as low risk.

[0132] If the key is leaked or maliciously tampered with, the administrator needs to immediately take remedial measures, which is defined as high risk.

[0133] If the event is evaluated as high risk and the threat has been proven to exist, the administrator should immediately perform a key rotation operation.

[0134] If the original data access permissions need to be restored after key rotation, the administrator will restore the access to sensitive data by restoring the backup key or re-encryption process.

[0135] Furthermore, by introducing an automatic monitoring and management mechanism for the key rotation period and combining it with the system's data encryption and security module, the present invention can detect abnormal activities related to key operations in real time. When a potential security threat is detected, the security monitoring module will automatically mark the key as a "risk key" and send the relevant information to the global administrator for timely review and handling. This mechanism not only enhances the security of key management but also enables a rapid emergency response in case of a security incident, such as automatically triggering key rotation and other operations. It can not only detect abnormal behaviors (such as abnormal logins, abnormal data access, etc.) in real time but also automatically trigger alarms, mark risk keys, perform real-time key rotation, and take other emergency response measures according to the severity of the event. The response mechanism for security incidents is closely integrated with the key management system, realizing dynamic monitoring and handling of potential threats, reducing human intervention, and ensuring that the project manager can only indirectly use the key through the encryption service with the approval of the department key administrator and cannot directly access the key. This control mechanism effectively limits the risk of key abuse while ensuring that personnel at different levels can operate according to their authorized permissions, thus enhancing the overall security of the system.

[0136] Formulating a data backup plan includes selecting corresponding backup types according to different types and importance levels of data, determining the backup frequency and specific time, and regularly conducting recovery tests to verify the integrity of the backup data and the effectiveness of the actual recovery process.

[0137] Example 2, referring to Figure 2 , which is an embodiment of the present invention, provides a system for a data storage method of the project cost of maintenance projects, characterized in that it includes a data integration module 100, a database design and management module 200, a permission allocation module 300, a data encryption and security module 400, and a data backup and recovery module 500.

[0138] The data integration module 100 is responsible for collecting and organizing the relevant data of the maintenance project and standardizing and structuring the data.

[0139] The database design and management module 200 is responsible for designing the table structure, data fields, and indexes of the database and managing the storage, update, and maintenance of the data.

[0140] The permission allocation module 300 defines different user roles and corresponding permission levels, and controls the data access permissions and operation permissions of various users.

[0141] The data encryption and security module 400 is responsible for encrypting and protecting the data during storage and transmission.

[0142] The data backup and recovery module 500 formulates and implements data backup strategies, including full backup, incremental backup, and differential backup, and designs and executes data recovery processes.

[0143] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs, etc., which can store program codes.

[0144] The logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as a definite sequence list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch instructions from the instruction execution system, apparatus, or device and execute the instructions), or in combination with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0145] More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection part with one or more wirings (electronic device), a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, then editing, interpreting, or processing it in other suitable ways when necessary, and then storing it in a computer memory.

[0146] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits with logic gate circuits for implementing logical functions on data signals, application specific integrated circuits with appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0147] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and they should all be covered by the scope of the claims of the present invention.

Claims

1. A data storage method for the project cost of maintenance items, characterized in that, Including: Maintenance project cost data to form a data set; Establish data standards and coding rules; Establish a power grid maintenance project cost database system; Encrypt the project cost data in the power grid maintenance project cost database system.

2. The data storage method for the project cost of maintenance items according to claim 1, characterized in that: The maintenance project cost data includes collecting data from the information system and screening out information related to the maintenance project in the data; The formation of the data set includes cleaning incomplete, incorrect or inconsistent data entries, standardizing formats and units, merging the same type of data from different sources, converting unstructured data into structured data, defining attribute tags for each data point, establishing associations between data points, and integrating all processed data into a unified data set.

3. The data storage method for the project cost of maintenance items according to claim 2, wherein: The establishment of data standards and coding rules includes formulating unified data format, data type and data length standards according to the data types and business requirements in the data set; The data format uses the ISO8601 standard format; Determine the data type to be used for each field and set the corresponding length limit for each field; The coding rule assigns a unique identifier to each record in the data set and establishes a hierarchical coding according to the business logic relationship.

4. The data storage method for the project cost of maintenance items as claimed in claim 3, characterized in that: The establishment of the power grid maintenance project cost database system includes designing an entity-relationship model based on the standardized and coded data set and identifying all entities and relationships; Converting the entity-relationship model into a specific database model, designing the table structure, determining the primary key, foreign key, and index; Selecting a database management system and designing the physical storage structure of the table according to the performance requirements; Creating a database in the selected database management system, establishing data tables, and defining fields and data types; Importing the standardized data into the database, creating views and indexes; Setting user roles and permissions, encrypting the stored and transmitted data, formulating a data backup plan and a data recovery process.

5. The data storage method for the project cost of maintenance items according to claim 4, characterized in that: The setting of user roles and permissions includes defining role and permission hierarchies, assigning user permissions through roles, and each role has different data access and operation permissions according to the hierarchical division. The access permissions are dynamically determined according to user attributes, operation types, and data attributes; Among them, the roles include global administrator, department key administrator, and project manager; The global administrator is responsible for generating and distributing the root key, which is used to encrypt other keys, and has full authority to manage the root certificate and issue certificates of TLS / SSL; The department key administrator manages the department-level keys, which are used to encrypt sensitive data within the department, and is responsible for performing key rotation and operating according to the guidance and policies of the global administrator; The project manager can request to reset the data encryption key related to the project with the approval of the department key administrator, but cannot directly access the key and can only use the key through the encryption service; When a user attempts to access sensitive data, the permission assignment module first checks the user's role and the permission level related to the requested operation; If the user is a global administrator, access and operation of all data and functions are allowed, including the generation and distribution of encryption keys; If the user is a department key administrator, the permission assignment module checks whether the requested data belongs to the corresponding managed department; If it belongs, data encryption operations and key rotation are allowed; if not, the request is rejected, and corresponding error logs or warning messages are generated; When a user is a project manager and requests to reset the data encryption key, the permission allocation module automatically sends an approval request to the department key administrator; If the department key administrator approves the request, the project manager indirectly uses the new encryption key through the encryption service. The project manager cannot directly access the key and uses the key through the existing encryption service interface; If the department key administrator rejects the request, the project manager will not be able to access the new key and will also be unable to perform encryption or decryption operations; Record the user information, time, operation type, and result of each data operation; Conduct a system audit regularly to check whether the implementation of permissions complies with policies and regulations.

6. The data storage method for the project cost of maintenance items as described in claim 5, characterized in that: The encryption of the stored and transmitted data includes that before the data is stored in the database, the data encryption and security module automatically checks the classification label of the data. If the data is marked as sensitive data, the AES encryption algorithm is triggered to encrypt the data; During the data transmission process, the TLS / SSL protocol is uniformly used for encryption; The global administrator sets the key rotation period according to the organization's security policy. The data encryption and security module automatically monitors the usage duration of the key. When the rotation period is reached, a key rotation task is automatically generated, and the global administrator is notified for review; When the global administrator approves the key rotation, the department key administrator receives the rotation instruction. The department key administrator needs to evaluate the data scope and related business processes affected by the key rotation and execute the key rotation to re-encrypt all sensitive data; After re-encryption, necessary tests are conducted to verify the availability and integrity of the data; After the key rotation is completed, the department key administrator needs to notify all affected project managers that the key has been updated; When a project manager needs to reset the data encryption key related to the project, the data encryption and security module will pass the request to the department key administrator for review; If the department key administrator approves, the project manager will indirectly obtain the new encryption key through the encryption service and perform encryption and decryption operations on the relevant data; If the department key administrator does not approve the request, the project manager will not be able to perform any operations involving the key; During the encryption process, the data encryption and security module judges whether there is abnormal activity related to key operations by comparing the normal behavior pattern; If there are abnormal login behaviors, abnormal data access models, unauthorized system operations, and abnormal network traffic patterns in the abnormal activities, it indicates that there are abnormalities or potential security threats; If there are malicious code attacks and system intrusions in the abnormal activities, it indicates that there are security incidents; When an abnormality or potential security threat is detected, the security monitoring module will immediately trigger an alarm and send the relevant information to the system administrator; When a security incident is detected, the current key will be automatically marked as a risky key, and the relevant logs of the key usage will be recorded, including user, operation type, operation time, and IP address information; After the alarm is triggered, the global administrator is immediately notified of the risk status of the current key; After the global administrator receives an alert, the data encryption and security module provides a detailed risk report for the global administrator to review; The global administrator assesses the severity of the security incident based on the details in the risk report; For a single abnormal access attempt, the administrator can choose to temporarily suspend the use of the key and conduct further review, or perform key re-authentication, which is defined as a low risk; If the key is leaked or maliciously tampered with, the administrator needs to take immediate remedial measures, which is defined as a high risk; If the event is evaluated as a high risk and the threat has been proven to exist, the administrator shall immediately execute the key rotation operation; If the access permission to the original data needs to be restored after key rotation, the administrator will restore the access to sensitive data by restoring the backup key or the re-encryption process.

7. The data storage method for the project cost of maintenance items according to claim 6, characterized in that: The formulation of the data backup plan includes selecting the corresponding backup type according to the different types and importance levels of the data, determining the backup frequency and specific time, and regularly conducting recovery tests to verify the integrity of the backup data and the effectiveness of the actual recovery process.

8. A system adopting a data storage method for the project cost of maintenance items as described in any one of claims 1 to 7, characterized in that: Including a data integration module (100), a database design and management module (200), a permission allocation module (300), a data encryption and security module (400), and a data backup and recovery module (500); The data integration module (100) is responsible for collecting and organizing the relevant data of the maintenance project and standardizing and structuring the data; The database design and management module (200) is responsible for designing the table structure, data fields, and indexes of the database and managing the storage, update, and maintenance of the data; The permission allocation module (300) defines different user roles and corresponding permission levels, and controls the data access permissions and operation permissions of various users; The data encryption and security module (400) is responsible for the encryption protection of data during storage and transmission; The data backup and recovery module (500) formulates and implements a data backup strategy, including full backup, incremental backup, and differential backup, and designs and executes a data recovery process.

9. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of a data storage method for the project cost of a maintenance item described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of a data storage method for the project cost of a maintenance item described in any one of claims 1 to 7.

Images