Data warehouse-in and warehouse-out management system for poeia library

Abstract

The invention relates to the technical field of data management, in particular to a data warehouse-in and warehouse-out management system for a poeia library, which comprises a standard storage module, a design terminal, a resource scheduling module and a data verification module. The specification storage module adopts a collaborative architecture of a dynamic storage unit and an archiving storage unit, and stores a power transmission line design specification and a specification traceability link; the design terminal receives the basic specification data and supplements design parameters to form enhanced specification data; and the resource scheduling module switches a complete storage mode, a core storage mode and a link storage mode according to the residual capacity threshold of the dynamic storage unit to realize intelligent adjustment of the storage granularity. Data states are migrated in order in the complete storage stage, the core storage stage and the link storage stage, and finally non-tampering archiving of standard traceability links is achieved through the block chain technology. According to the scheme, the problems of low storage efficiency, frequent version conflicts, verification strategy stiffness and the like of a traditional design library are solved, and full-life-cycle intelligent management of design specifications is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of data management, and in particular to a data entry and exit management system for a library. Background Art

[0002] A design database is a database system used to store and manage design specifications, standards, equipment information, and other data. In the power industry, this database is primarily used to store and manage standards and specifications for transmission line design, helping designers quickly locate and reference relevant design data during line design, improving design efficiency and accuracy.

[0003] In power design, the design library is mainly used in the following aspects:

[0004] Design specifications and standards: The Design Library stores various design specifications and standards. Designers can directly call these specifications for design, avoiding the inconvenience and errors caused by manual search and reference of specifications.

[0005] Equipment information: The design database contains detailed information on various equipment, such as the specifications, models, and materials of poles, towers, transformers, and other equipment. Designers can select appropriate equipment as needed and conduct material statistics.

[0006] Regional differences: Due to the different geographical, climatic and other conditions in different regions, the Design Library also supports regionally differentiated design information to ensure that the design plan meets the actual local needs.

[0007] In applications, database data must be regularly updated and maintained to ensure the accuracy and timeliness of the information. For example, a prior art method for transmitting and securing power engineering design data is disclosed. This method categorizes power engineering design data by engineering field and sets query permissions; cleans the power engineering design data to be uploaded; integrates the data packets to be transmitted; performs an integrity check on the compressed power engineering design data package and generates a check code α1; uploads the compressed power engineering design data package and the check code α1 to a public database; obtains the integrity check code α2; extracts the power engineering design data when α1 equals α2; synchronizes the power engineering design data; obtains integrity check codes β1 and β2; and when β1 does not equal β2, overwrites the power engineering design data in the public database with the power engineering design data in the backup database, performing data self-recovery and restoration. This method ensures the integrity, availability, and confidentiality of the power engineering design data in the public database.

[0008] Under the current technological landscape, while the integrity of the design database data is guaranteed through data verification mechanisms and self-healing and restoration functions, the management of design specifications in the power industry still faces the following technical bottlenecks: 1) Traditional storage models use fixed granularity to store data, making it difficult to cope with the dynamic balance between massive specification version iterations and limited storage resources; 2) The verification mechanism focuses only on data integrity and fails to establish correlation with the evolution of design parameters, making it impossible to implement a dynamic verification strategy based on the stability of specification versions; 3) There is a lack of a multi-version collaborative management mechanism when updating regionally differentiated specifications, resulting in version conflicts when cross-regional design projects reference specifications; 4) Specification traceability links and entity data are managed separately, making it difficult to maintain traceability of the association between specification data and supplementary design parameters when storage capacity is low. These shortcomings seriously restrict the adaptability of the design database to large-scale, multi-regional, and high-frequency specification update scenarios in smart grid construction. Summary of the Invention

[0009] To this end, the present invention provides a data entry and exit management system for a library, so as to overcome at least one of the above technical deficiencies.

[0010] To achieve the above-mentioned object, on the one hand, the present invention provides a data in-and-out management system for a design library, comprising a specification storage module for storing transmission line design specifications, equipment parameter sets and corresponding specification traceability links;

[0011] The design terminal is connected to the specification storage module and receives the basic specification data output by the specification storage module. The designer supplements the design parameters and version identifier in the basic specification data to form enhanced specification data and transmits it back to the specification storage module.

[0012] The resource scheduling module is connected to the specification storage module and the design terminal respectively, dynamically adjusts the working mode of the specification storage module according to the remaining capacity of the storage unit, and sets the corresponding data verification cycle based on the enhanced specification data of each design project;

[0013] The data verification module is connected to the resource scheduling module to perform version consistency verification on the specification data in the design database according to the set data verification cycle;

[0014] The basic specification data include tower load parameters, conductor model parameters and insulator configuration parameters, and the design parameters include tower structure correction coefficients and material durability parameters.

[0015] As an optimal technical solution for the data in-and-out management system of the classic library, the resource scheduling module sets the complete storage mode, core storage mode and link storage mode of the standard storage module;

[0016] Among them, the complete storage mode stores enhanced specification data and associated files at the same time, the core storage mode only retains basic specification data, and the link storage mode only stores specification traceability links.

[0017] As an optimal technical solution for the data in and out management system of the design library, the standard storage module includes:

[0018] A dynamic storage unit that interacts with the design terminal to store enhanced specification data or basic specification data or specification traceability links;

[0019] The archiving storage unit stores the set of specification traceability links generated by the specification storage module after each work cycle.

[0020] As a preferred technical solution for the data in-and-out management system of the design library, the resource scheduling module sets a first capacity threshold and a second capacity threshold of the dynamic storage unit. When the remaining capacity of the dynamic storage unit is higher than the second capacity threshold, the full storage mode is activated; when the remaining capacity is between the first capacity threshold and the second threshold, the core storage mode is activated; and when the remaining capacity is lower than the first capacity threshold, the linked storage mode is activated.

[0021] The first capacity threshold is smaller than the second capacity threshold.

[0022] As an optimal technical solution for the data in-and-out management system of the design library, the resource scheduling module sends the basic specification data to the design terminal for parameter supplement in the complete storage mode, forming enhanced specification data for return storage; deletes the supplementary design parameters in the enhanced specification data in the core storage mode; deletes the basic specification data entity in the linked storage mode, retains the specification traceability link, and requests data from the design terminal through the link when it is needed.

[0023] As an optimal technical solution for the data in and out management system of the classic library, after completing a single working cycle of the specification storage module, the resource scheduling module transfers the specification traceability link set generated in the cycle to the archival storage unit; the working cycle includes the complete storage stage, the core storage stage and the link storage stage in sequence.

[0024] As a preferred technical solution for the data in-and-out management system of the design library, the resource scheduling module sets a standard duration for the link storage phase. After the standard duration is reached, the current work cycle ends, the standard traceability link is transferred to the archive storage unit, and the link record of the dynamic storage unit is cleared. The new work cycle restarts from the full storage mode.

[0025] The standard duration is determined by dynamic calculation based on the durations of the first two stages.

[0026] As a preferred technical solution for the data in-and-out management system of the design library, the resource scheduling module calculates the version stability coefficient of the specification data based on the structural correction coefficient and material durability parameter in the design parameters;

[0027] Among them, the version stability coefficient is negatively correlated with the structural correction amplitude and positively correlated with the material durability parameter.

[0028] As an optimal technical solution for the data in-and-out management system of the design library, the resource scheduling module determines the theoretical verification cycle of the corresponding specification data according to the version stability coefficient;

[0029] The theoretical verification period is negatively correlated with the version stability coefficient.

[0030] As an optimal technical solution for the data in and out management system of the design library, the resource scheduling module takes the design area as the unit, takes the weighted average of the theoretical verification cycles of each specification in the area as the actual verification cycle, and directs the data verification module to perform standard data verification according to the actual verification cycle within the working cycle.

[0031] Compared with the existing technology, the beneficial effect of the present invention is that, by constructing a three-level storage system of complete storage mode, core storage mode and linked storage mode, combined with a dynamic capacity threshold control strategy, the present invention realizes intelligent adjustment of storage granularity. When the storage capacity is sufficient, the complete enhanced specification data is retained. When the capacity is tight, the supplementary parameters are gradually stripped away and only the core data is retained. In the low-capacity state, it is converted to lightweight linked storage, effectively balancing the contradiction between massive specification version iterations and limited storage resources. This mechanism enables the system to maintain efficient storage operation in high-frequency update scenarios, avoiding resource waste or performance bottlenecks caused by traditional fixed storage modes.

[0032] Furthermore, the system utilizes an innovatively designed collaborative architecture of dynamic and archival storage units, enabling orderly data state migration through a work cycle mechanism. The complete storage phase ensures real-time design collaboration, the core storage phase maintains the availability of foundational specifications, and the linked storage phase establishes lightweight data indexes. Finally, archival storage provides persistent storage for data links. This full-cycle management model ensures rapid access to the latest design data while fully preserving the historical traceability of specification revisions.

[0033] Furthermore, the system's early warning mechanism enhances real-time performance and robustness through closed-loop feedback and adaptive models. Feature importance analysis and incremental learning techniques, based on historical data training, dynamically adjust the fusion weights of multi-source features, enabling the model to adapt to seasonal changes, tree species differences, and environmental fluctuations. Furthermore, a multi-level risk classification mechanism generates graded early warning signals through comprehensive quantitative indicators. Combined with the ability to label risk area locations, this provides intuitive decision-making support for maintenance personnel, significantly improving the efficiency of problem location and resolution.

[0034] Furthermore, the system deeply integrates the evolution of design parameters with data verification by building a version stability coefficient model based on structural modification coefficients and material durability parameters. By quantitatively analyzing the stability characteristics of specification data, it dynamically generates differentiated theoretical verification cycles, combining intensive verification of frequently revised specifications with long-term verification of stable specifications. Incorporating a regional weighted algorithm to generate actual verification cycles not only meets the specific requirements of regional design specifications, but also avoids the resource mismatch caused by traditional fixed-cycle verification.

[0035] Furthermore, the present invention employs a storage mechanism that associates specification traceability links with entity data. In linked storage mode, data association is maintained through a collection of specification traceability links. When designing across regions, the system can quickly identify regional specification differences based on the multidimensional version map stored in the archive storage unit and automatically match compatible version combinations. This mechanism effectively prevents version reference conflicts caused by asynchronous regional specification updates, ensuring specification consistency in multi-regional collaborative design.

[0036] Furthermore, the present invention establishes a strong association between supplementary parameters and basic specifications during the design terminal feedback phase through an enhanced parameter supplementation mechanism and version identification system for specification data. This, in conjunction with the version consistency check of the data verification module, verifies the compliance of parameter supplementation in full storage mode, and verifies the validity of data associations through traceability links in linked storage mode. This creates a dual verification protection throughout the entire data entry and exit process, significantly improving the traceability and revision reliability of specification data. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 This is a structural block diagram of a data in-and-out management system for a database according to an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to make the objects and advantages of the present invention more clearly understood, the present invention is further described below in conjunction with embodiments; it should be understood that the specific embodiments described herein are merely used to explain the present invention and are not intended to limit the present invention.

[0039] The preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0040] It should be noted that, in the description of the present invention, terms such as "up", "down", "left", "right", "inside", and "outside" indicating directions or positional relationships are based on the directions or positional relationships shown in the accompanying drawings. This is only for the convenience of description and does not indicate or imply that the device or element must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation on the present invention.

[0041] Furthermore, it should be noted that, in the description of the present invention, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed connections, detachable connections, or integral connections; mechanical connections or electrical connections; direct connections or indirect connections through an intermediate medium; and internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0042] See also Figure 1 As shown, it is a structural block diagram of a data entry and exit management system for a design library in an embodiment of the present invention. The data entry and exit management system for a design library includes a specification storage module for storing transmission line design specifications, equipment parameter sets, and corresponding specification traceability links;

[0043] The design terminal is connected to the specification storage module and receives the basic specification data output by the specification storage module. The designer supplements the design parameters and version identifier in the basic specification data to form enhanced specification data and transmits it back to the specification storage module.

[0044] The resource scheduling module is connected to the specification storage module and the design terminal respectively, dynamically adjusts the working mode of the specification storage module according to the remaining capacity of the storage unit, and sets the corresponding data verification cycle based on the enhanced specification data of each design project;

[0045] The data verification module is connected to the resource scheduling module to perform version consistency verification on the specification data in the design database according to the set data verification cycle;

[0046] The basic specification data includes tower load parameters, conductor model parameters, and insulator configuration parameters, while the design parameters include tower structure correction factors and material durability parameters. In the above embodiment, a basic data management architecture is constructed to enable dynamic interaction and intelligent verification of specification data. In this embodiment, the specification storage module uses distributed database technology to store transmission line design specifications, including tower load parameters, conductor model parameters, and insulator configuration parameters. Each data item is bound to a specification traceability link (a unique identifier combining a hash value and a timestamp in this embodiment). The design terminal connects to the specification storage module via an API interface. After receiving the basic specification data, the designer in this embodiment uses an interactive interface to supplement the tower structure correction factor (in this embodiment, the correction range is defined as ±10%) and material durability parameters (including corrosion resistance and fatigue life indicators), and adds a version identifier (in this embodiment, a three-level version number and region code combination format is used). The enhanced specification data is returned to the specification storage module in a structured data format. In this embodiment, the basic parameters, supplementary parameters, and version metadata are encapsulated in JSON format. In this embodiment, the resource scheduling module monitors the remaining capacity of dynamic storage units in real time, dynamically switches storage modes based on preset capacity thresholds, and simultaneously parses version identifiers and parameter change records in the enhanced specification data to generate a differentiated data verification period table. In this embodiment, the data verification module uses a differential verification algorithm to compare hash value changes between the current version and historical versions to detect whether parameter changes exceed preset tolerance thresholds.

[0047] Specifically, the resource scheduling module sets the complete storage mode, the core storage mode and the linked storage mode of the standard storage module;

[0048] Among them, the complete storage mode stores enhanced specification data and associated files at the same time, the core storage mode only retains basic specification data, and the link storage mode only stores specification traceability links. In detail, the above embodiment realizes dynamic hierarchical management of storage resources and ensures data integrity through multi-mode collaboration. In this embodiment, the complete storage mode is enabled when the remaining capacity of the dynamic storage unit is higher than the second capacity threshold, and stores enhanced specification data and its associated files (including design drawings and calculation book attachments in this embodiment). The data storage structure adopts a three-layer nested model of "basic parameter layer + supplementary parameter layer + version identification layer" in this embodiment. In this embodiment, the core storage mode is activated when the capacity drops between the first capacity threshold and the second capacity threshold, and executes the data stripping program: delete the supplementary design parameters and retain the minimum available set of basic specification data (retain the pole tower load parameters and conductor model parameters in this embodiment). The stripped supplementary parameters are converted into encrypted cache files in this embodiment and a temporary access token is generated. In this embodiment, the link storage mode is started when the capacity is lower than the first capacity threshold, and the basic specification data entity is replaced with a specification traceability link (in the form of a verifiable short chain in this embodiment). In this embodiment, only an index table containing the link ID, version number and last access time is maintained in the dynamic storage unit. When data is called, the link redirection mechanism is used to pull data from the design terminal in real time and verify the digital signature.

[0049] As an optimal technical solution for the data in and out management system of the design library, the standard storage module includes:

[0050] A dynamic storage unit that interacts with the design terminal to store enhanced specification data or basic specification data or specification traceability links;

[0051] The archiving storage unit stores the set of specification traceability links generated by the specification storage module after each work cycle.

[0052] It is understood that by building a data lifecycle management system, it is possible to achieve traceable archiving of standard versions. In this embodiment, the dynamic storage unit adopts a hybrid storage architecture of in-memory database and SSD. In the complete storage mode, data is stored in a columnar storage structure (in this embodiment, storage is divided into columns by parameter type). In the core storage mode, a data compression algorithm is enabled (in this embodiment, the Zstandard compression protocol is used). In the linked storage mode, the index table integrates a Bloom filter to optimize query efficiency. In this embodiment, the archival storage unit builds a version archive based on blockchain technology. At the end of each work cycle, the standard traceability link set in the dynamic storage unit is packaged into a block (in this embodiment, the block includes a period identifier and a timestamp hash chain), and cross-node synchronization is achieved through a consensus algorithm (in this embodiment, a practical Byzantine fault tolerance algorithm is used). In this embodiment, the work cycle is divided into three phases: the complete storage phase allows concurrent writes and adopts optimistic locking conflict control (in this embodiment, the duration is set to 72 hours); the core storage phase switches to read-only mode (in this embodiment, it lasts for 48 hours); the linked storage phase freezes data modifications and starts archiving preprocessing (in this embodiment, it lasts for 24 hours); after the cycle ends, the dynamic storage unit in this embodiment performs data clearing and new cycle initialization operations.

[0053] Specifically, the resource scheduling module sets a first capacity threshold and a second capacity threshold of the dynamic storage unit, and enables the full storage mode when the remaining capacity of the dynamic storage unit is higher than the second capacity threshold, enables the core storage mode when the remaining capacity is between the first capacity threshold and the second threshold, and enables the linked storage mode when the remaining capacity is lower than the first capacity threshold;

[0054] Among them, the first capacity threshold is less than the second capacity threshold. In detail, the first capacity threshold and the second capacity threshold of the dynamic storage unit are set (in this embodiment, the first capacity threshold is 30% of the total capacity of the dynamic storage unit, and the second capacity threshold is 60%). When the remaining capacity of the dynamic storage unit is higher than the second capacity threshold, in this embodiment, the full storage mode is enabled to retain all enhanced specification data; when the remaining capacity is between 30%-60%, it switches to the core storage mode and performs data reduction operations; when the remaining capacity is lower than 30%, the linked storage mode is activated and the lightweight storage strategy is started. In this embodiment, a dynamic capacity detection algorithm is adopted (the storage status is polled every 10 seconds), and a mapping relationship table between the capacity threshold and the storage mode is established to achieve millisecond-level response of mode switching.

[0055] Specifically, in the complete storage mode, the resource scheduling module sends the basic specification data to the design terminal for parameter supplementation, forming enhanced specification data for return storage; in the core storage mode, the supplementary design parameters in the enhanced specification data are deleted; in the link storage mode, the basic specification data entity is deleted, the specification traceability link is retained, and the data is requested from the design terminal through the link when it is needed. It should be understood that this embodiment stipulates data processing rules under multiple modes. In the complete storage mode, the resource scheduling module in this embodiment encapsulates the basic specification data into a standardized data packet (Protobuf protocol is used in this embodiment) and sends it to the design terminal. The enhanced specification data formed after the designer supplements the parameters is returned for storage through a two-way verification mechanism in this embodiment (including digital signature verification and format compliance check). In the core storage mode, the parameter stripping program is executed in this embodiment: the supplementary design parameter field (JSON node marked as "ext_param" in this embodiment) is identified by the data parsing engine, removed from the enhanced specification data, and a stripping log is generated. In the linked storage mode, the data entity replacement process is started in this embodiment: the basic specification data is converted into a specification traceability link (a short link in Base64 encoding is used in this embodiment), and on-demand data requests are realized through the link resolution service (a RESTful API interface is deployed in this embodiment). The request must be accompanied by a version identifier and an identity authentication token.

[0056] Specifically, after completing a single work cycle of the specification storage module, the resource scheduling module transfers the specification traceability link set generated in the cycle to the archive storage unit; the work cycle includes a complete storage stage, a core storage stage, and a link storage stage in sequence. In detail, the work cycle is divided into three stages: the complete storage stage allows data writing and supplementation (in this embodiment, it lasts until the capacity of the dynamic storage unit drops to the second threshold), the core storage stage freezes data addition and only allows queries (in this embodiment, it lasts until the capacity drops to the first threshold), and the link storage stage prohibits data modification and starts archiving preparation. In this embodiment, the resource scheduling module sorts the specification traceability link set by version number at the end of the work cycle (in this embodiment, a semantic version sorting algorithm is used), packages it into an archive data unit (in this embodiment, it is encapsulated as a ZIP compressed package and attached with a metadata description file), and transfers it to the archive storage unit through a secure transmission channel. In this embodiment, the trigger condition for the end of the cycle is set to the link storage stage duration reaching a preset value (set to 24 hours in this embodiment) or the storage unit load exceeds a critical value (in this embodiment, it is defined that the CPU usage rate is greater than 85% for 5 minutes).

[0057] Specifically, the resource scheduling module sets a standard duration for the link storage phase, ends the current work cycle after the standard duration is reached, transfers the standard traceability link to the archival storage unit, clears the link record of the dynamic storage unit, and restarts the new work cycle from the full storage mode;

[0058] Among them, the standard duration is dynamically calculated and determined based on the duration of the first two stages. Specifically, the sum of the durations of the complete storage stage and the core storage stage is multiplied by the dynamic adjustment coefficient. In this embodiment, the dynamic adjustment coefficient is set to a floating point value in the range of 0.5 to 1.2. When the link storage stage reaches the standard duration, the cycle end process is automatically triggered in this embodiment: the standard traceability link set is batch transferred to the archive storage unit through the data pipeline, the link index table of the dynamic storage unit is cleared, and the storage mode is reset to the complete storage mode to start a new working cycle. In this embodiment, a sliding time window algorithm is used to dynamically update the adjustment coefficient, and the calculation accuracy is optimized based on historical cycle data.

[0059] Specifically, the resource scheduling module calculates the version stability coefficient of the specification data based on the structural correction coefficient and material durability parameter in the design parameters. Specifically, the version stability coefficient is equal to the standard value of the material durability parameter divided by the absolute offset of the structural correction coefficient. In this embodiment, the material durability parameter is a weighted sum of the corrosion resistance level and fatigue life, and the structural correction coefficient offset is calculated by comparing the difference between the current version and the baseline version. The calculation process in this embodiment uses normalization, mapping the results to a range of 0 to 1, with higher values ​​representing more stable versions.

[0060] Specifically, the resource scheduling module determines the theoretical verification period of the corresponding specification data according to the version stability coefficient;

[0061] The theoretical verification period is negatively correlated with the version stability coefficient. Specifically, the theoretical verification period is equal to the basic verification period multiplied by the negative exponential power of the stability coefficient. In this embodiment, the basic verification period is set to 30 days. When the version stability coefficient is greater than 0.8, a long-period verification task is generated. When it is less than 0.3, a high-frequency verification mode is triggered. During the calculation process, a smoothing factor is introduced in this embodiment to prevent sudden changes in the period value and ensure the stability of verification task scheduling.

[0062] Specifically, the resource scheduling module takes the design area as a unit, takes the weighted average of the theoretical verification periods of each specification in the area as the actual verification period, and directs the data verification module to perform specification data verification according to the actual verification period within the working cycle. In the above embodiment, the resource scheduling module in this embodiment uses the geographic code of the design area as the grouping basis, and performs weighted average calculation on the theoretical verification period of each specification. The weight value in this embodiment is determined according to the frequency of specification references in the area and the level of the design project. In this embodiment, the weighted average value uses a rounding-up algorithm to generate the actual verification period. For example, when the calculated result is 23.6 days, it is rounded to 24 days. In this embodiment, the data verification module creates a timed task queue according to the actual verification period. During execution, this embodiment uses a distributed lock mechanism to ensure the coordination of multi-node verification, and completes consistency verification through version snapshot comparison technology.

[0063] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the devices, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based device that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0064] Thus far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art may make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will fall within the scope of protection of the present invention.

[0065] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that the present invention is susceptible to various modifications and variations. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A data in and out management system for a library, characterized in that: include: Specification storage module, used to store transmission line design specifications, equipment parameter sets and corresponding specification traceability links; The design terminal is connected to the specification storage module and receives the basic specification data output by the specification storage module. The designer supplements the design parameters and version identifier in the basic specification data to form enhanced specification data and transmits it back to the specification storage module. The resource scheduling module is connected to the specification storage module and the design terminal respectively, dynamically adjusts the working mode of the specification storage module according to the remaining capacity of the storage unit, and sets the corresponding data verification cycle based on the enhanced specification data of each design project; The data verification module is connected to the resource scheduling module to perform version consistency verification on the specification data in the design database according to the set data verification cycle; The basic specification data include tower load parameters, conductor model parameters and insulator configuration parameters, and the design parameters include tower structure correction coefficients and material durability parameters.

2. The data in and out management system for a library according to claim 1 is characterized in that: The resource scheduling module sets the complete storage mode, core storage mode and link storage mode of the standard storage module; Among them, the complete storage mode stores enhanced specification data and associated files at the same time, the core storage mode only retains basic specification data, and the link storage mode only stores specification traceability links.

3. The data in and out management system for a library according to claim 2 is characterized in that: The specification storage module includes: A dynamic storage unit that interacts with the design terminal to store enhanced specification data or basic specification data or specification traceability links; The archiving storage unit stores the set of specification traceability links generated by the specification storage module after each work cycle.

4. The data in and out management system for a library according to claim 3 is characterized in that: The resource scheduling module sets a first capacity threshold and a second capacity threshold of the dynamic storage unit, and enables a full storage mode when the remaining capacity of the dynamic storage unit is higher than the second capacity threshold, enables a core storage mode when the remaining capacity is between the first capacity threshold and the second threshold, and enables a linked storage mode when the remaining capacity is lower than the first capacity threshold; The first capacity threshold is smaller than the second capacity threshold.

5. The data in and out management system for a library according to claim 4 is characterized in that: In the complete storage mode, the resource scheduling module sends the basic specification data to the design terminal for parameter supplementation to form enhanced specification data for return storage; in the core storage mode, the supplementary design parameters in the enhanced specification data are deleted; in the linked storage mode, the basic specification data entity is deleted, the specification traceability link is retained, and data is requested from the design terminal through the link when it is needed.

6. The data in and out management system for a library according to claim 5 is characterized in that: After completing a single working cycle of the specification storage module, the resource scheduling module transfers the specification traceability link set generated in the cycle to the archival storage unit; the working cycle includes a complete storage stage, a core storage stage and a link storage stage in sequence.

7. The data in and out management system for a library according to claim 6 is characterized in that: The resource scheduling module sets a standard duration for the link storage phase, ends the current work cycle after the standard duration is reached, transfers the standard traceability link to the archival storage unit, clears the link record of the dynamic storage unit, and restarts the new work cycle from the complete storage mode; The standard duration is determined by dynamic calculation based on the durations of the first two stages.

8. The data in and out management system for a library according to claim 7 is characterized in that: The resource scheduling module calculates the version stability coefficient of the specification data based on the structure correction coefficient and the material durability parameter in the design parameters; Among them, the version stability coefficient is negatively correlated with the structural correction amplitude and positively correlated with the material durability parameter.

9. The data in and out management system for a library according to claim 8, characterized in that: The resource scheduling module determines the theoretical verification period of the corresponding specification data according to the version stability coefficient; The theoretical verification period is negatively correlated with the version stability coefficient.

10. The data in and out management system for a library according to claim 9, characterized in that: The resource scheduling module takes the design area as a unit, takes the weighted average of the theoretical verification cycles of each specification in the area as the actual verification cycle, and directs the data verification module to perform standard data verification according to the actual verification cycle within the working cycle.

Images