Global-oriented multi-language multi-time-zone power station management method and system

Abstract

The invention discloses a global-oriented multi-language multi-time-zone power station management method and system, and relates to the technical field of electric power digital management, and the method comprises the steps: collecting power station data, carrying out the standardized identification, and constructing a power station multistage coding identification main key; a multi-language mapping system is constructed by taking a multi-level coding identification main key of a power station as a drive, and time zone offset logic is constructed by using standardized identification; and performing hierarchical authority control based on the power station multi-level coding identification primary key prefix and generating a localized alarm prompt. According to the method, standardized identification of power station data is realized by constructing a unified power station multi-level coding main key; based on primary key driving multi-language mapping and time zone offset processing, accurate presentation and time consistency of data in a multi-language environment are guaranteed; authority control is achieved through primary key prefix division, multi-language alarm prompts are triggered in combination with signal coding, and a power station event management mechanism which is clear in alarm semantics, timely in response and controllable in boundary is achieved.

Description

Technical Field

[0001] This invention relates to the field of digital power management technology, specifically to a multilingual, multi-time zone power plant management method and system for global applications. Background Technology

[0002] With cross-border deployment, multilingual user participation, and time zone misalignment scheduling becoming the new normal for digital management in modern power enterprises, especially in the context of remote centralized monitoring, unified operation analysis, and refined operation and maintenance of various types of power plants such as hydropower, wind power, and photovoltaic power, the standardization of power plant data coding, multilingual adaptation, and localized response capabilities have become fundamental components in building a global power monitoring network. Current research focuses on building digital master stations, achieving visualized scheduling, and adapting to heterogeneous access, but there is still a lack of universal and engineering-adaptable underlying methods for unifying data identification structures and supporting multilingual and multi-time zone scheduling collaboration.

[0003] Existing power plant operation and maintenance management technologies have significant limitations when facing multilingual and multi-timezone scenarios. Regarding data identification, a unified and semantically transparent coding system has not yet been established, making it difficult to uniformly parse and access data from different countries and power plants. Although some projects support language switching at the interface level, the underlying data tags lack standardized binding decoupled from language, limiting multilingual displays to shallow interaction and failing to support in-depth analysis, alarms, and report generation. Regarding time management of power plant operation data, local time recording is commonly used, lacking a time unification and time zone conversion mechanism driven by country codes, making it difficult to meet the needs of cross-regional power plants for benchmarking analysis and response scheduling under the same time base. Current multi-level access control strategies are mostly based on static account and role configurations, failing to combine with the power plant coding structure to achieve dynamic access control and data tracking, making it difficult to handle cross-domain management scenarios at the group, regional, and site levels. Summary of the Invention

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

[0005] Therefore, the technical problem solved by this invention is that existing methods for cross-language and cross-time zone management of power plant data have problems such as inconsistent data encoding structures, inability to support multilingual semantic mapping, inability to standardize local offset processing of alarm and recording times, coarse access control precision and lack of dynamic parsing capabilities, and how to achieve multilingual data adaptation, time zone parsing and access control linkage based on a unified identifier primary key.

[0006] To address the aforementioned technical problems, this invention provides the following technical solution: a global, multilingual, multi-timezone power plant management method, comprising: collecting power plant data and standardizing its identification to construct a multi-level coded identification primary key for the power plant; constructing a multilingual mapping system using the multi-level coded identification primary key as the driver, and constructing time zone offset logic using the standardized identification; implementing hierarchical access control based on the multi-level coded identification primary key prefix of the power plant and generating localized alarm prompts; collecting power plant data and standardizing its identification includes: using the power plant identification to construct a unique identification combination for the power generation company, country, power plant, and generating unit; using equipment identification to distinguish between the overall plant code, system code, and equipment category and number; using signal identification to encode each measurement value or status value, distinguishing its type, source, and purpose; hierarchical access control includes: dividing the multi-level coded primary key prefix of the power plant into company-level, country-level, and power plant-level access ranges; filtering user permissions by binding the multi-level coded primary key range of the power plant; and constructing a multi-level record structure based on the multi-level coded primary key of the power plant for all operation logs and data audit records.

[0007] As a preferred embodiment of the global multilingual and multi-time zone power plant management method described in this invention, the power plant data includes power plant identification data, equipment structure and classification data, real-time measurement data, status monitoring data, event and alarm data, planning and reporting data, and operation and control command data.

[0008] As a preferred embodiment of the global multilingual and multi-time zone power plant management method described in this invention, the construction of the multi-level power plant coding identifier primary key includes constructing a power plant coding identifier primary key, an equipment coding identifier primary key, and a signal coding identifier primary key; the power plant coding identifier primary key adopts a five-segment combination coding method, including company code, country code, power plant code, and unit type code; the equipment coding identifier primary key adopts a three-layer nested structure of plant-wide code, system code, and equipment code, where the three characters of the system code correspond to the hydropower plant system code, and the two characters of the equipment code (classification code and number) correspond to the power plant equipment code; the signal coding identifier primary key is composed of three parts: signal classification, signal name, and signal number.

[0009] As a preferred embodiment of the global multilingual and multi-time zone power plant management method described in this invention, the step of constructing a multilingual mapping system by using the power plant multi-level coded identifier primary key as the driver includes: according to the signal name index and naming rules, the power plant multi-level coded identifier primary key corresponds to a logical phrase; using signal codes as retrieval anchors, constructing a language tag table, and binding it according to Chinese tag examples and English tag examples, establishing a multilingual mapping system between the power plant multi-level coded identifier primary key and semantic description; for status value processing, classifying status abbreviations and comparing their Chinese and English meanings.

[0010] As a preferred embodiment of the global multilingual and multi-time zone power plant management method described in this invention, the step of constructing time zone offset logic using standardized identifiers includes: extracting the country code field to locate the power plant's time zone; automatically associating the corresponding standard time offset value based on the country code field in the power plant's multi-level coded identifier primary key; using UTC timestamps for recording during the storage and exchange of power plant data to eliminate comparison errors in cross-time zone data records; and converting UTC time to the target country's local time in scenarios where data time needs to be displayed, based on the country code field contained in the constructed power plant multi-level coded identifier primary key.

[0011] As a preferred embodiment of the global multilingual and multi-time zone power plant management method described in this invention, the following steps, including hierarchical permission control based on the power plant multi-level coded identifier primary key prefix and the generation of localized alarm prompts, include: power plant data management is divided into a three-level structure and mapped to the prefix field of the power plant multi-level coded identifier primary key; a permission judgment mechanism based on matching the power plant multi-level coded identifier primary key prefix is ​​constructed; language loading and time zone parsing are restricted to execution within the permission scope; if a user only has country code permissions, the system only loads the power plant's language tag and time zone mapping; for power plants without access permissions, language resources and time conversion logic are not loaded or displayed; the execution logic of multilingual and multi-time zone operations is subject to the prefix of the power plant multi-level coded identifier primary key. Access restrictions are implemented; combining the power plant multi-level coding identifier primary key structure, a power plant multi-level coding identifier primary key field is added to all operation behaviors or alarm data. Alarm content is classified according to the prefix of the power plant multi-level coding identifier primary key. The operation record is added with the operator's permission prefix and the target data power plant multi-level coding identifier primary key to form a tracking chain; the permission judgment mechanism includes determining whether the user has permission to access all data items with the company code in the power plant multi-level coding identifier primary key; if the permission is limited to the country code, access to all power plant data is allowed; if the permission is limited to the power plant code, data related to the accessed power plant site is read; all read and write operations are determined by prefix matching between the power plant multi-level coding identifier primary key prefix and the user's permission range.

[0012] As a preferred embodiment of the global, multilingual, and multi-timezone power plant management method described in this invention, the step of performing hierarchical access control based on the power plant's multi-level coded identifier primary key prefix and generating localized alarm prompts includes:

[0013] Status signal codes are identified to trigger alarm events. These status signals include start / stop signals, fault states, and protection actions. The coding structure begins with "DQ," and the signal name uses a standard abbreviation structure. The alarm event determination logic is as follows: if the status signal value reaches a threshold, an alarm is generated. After triggering an alarm event, the language description content corresponding to the signal code is called to construct the alarm text. The alarm trigger time is recorded in UTC time. During the alarm generation stage, based on the country code field in the power plant multi-level coding identifier primary key, the local time offset is extracted from the zone mapping relationship, and the time is localized. The alarm text construction includes restricting the visibility of alarm content within the authorized scope, classifying it according to the company code, country code, and power plant code contained in the power plant multi-level coding identifier primary key, and connecting it with the time zone offset logic. After generation, alarm information is pushed out. The pushed content uses the signal code as an index, dynamically outputs multi-language template text, and attaches the alarm time, alarm source device name, and current processing status.

[0014] Another objective of this invention is to provide a global, multilingual, multi-time zone power plant management system that can collect power plant data, standardize the identification, and construct a multi-level coded identification primary key for the power plant. This solves the problems of inconsistent data coding structures and the inability to support multilingual semantic mapping in current methods for managing power plant data across languages ​​and time zones.

[0015] As a preferred embodiment of the global multilingual and multi-time zone power plant management system described in this invention, it includes: a power plant multi-level coding primary key construction module, a multilingual and multi-time zone adaptation module, and an access control and multilingual alarm response module; the power plant multi-level coding primary key construction module is used to construct a unified primary key coding system composed of power plant identifiers, equipment identifiers, and signal identifiers; the multilingual and multi-time zone adaptation module is used to drive language tag mapping and time zone offset corresponding to country codes based on the primary key; the access control and multilingual alarm response module is used to implement hierarchical access control using primary key prefixes, and to trigger the generation, time stamping, and permission-based push of multilingual alarm content using signal encoding.

[0016] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program as steps to implement a global, multilingual, multi-time zone power plant management method.

[0017] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a globally oriented, multilingual, multi-time zone power plant management method.

[0018] The beneficial effects of this invention are as follows: The multilingual and multi-time zone power plant management method provided by this invention achieves a unified expression of power plant identifiers, equipment identifiers and signal identifiers by constructing a multi-level coded identifier primary key for power plants, laying the foundation for data structure standardization. On this basis, a multilingual mapping mechanism, time zone offset logic and access control system are established, forming a power plant management method that combines global adaptability and structure-driven approach. By establishing a multilingual mapping table anchored by the primary key, consistent presentation of technical content such as signals, fields, and status values ​​is achieved across language environments, improving the understandability and collaborative efficiency of operation and maintenance in multi-country and multilingual contexts. Time zone mapping logic is constructed using the country code field in the primary key, enabling unified UTC time storage and local time conversion during the display phase, effectively eliminating the problem of time sequence mismatch between cross-time zone data records and scheduling instructions. Data access permissions are defined using the primary key prefix, enabling dynamic data filtering and operation record traceability at the company, national, and power plant levels, ensuring fine-grained control of cross-domain permission boundaries. Furthermore, alarms are triggered by primary key signal encoding, generating multilingual alarm text, annotating local time, and visibility control, achieving a semantically consistent, timely, secure, and compliant multilingual alarm push mechanism. The overall approach forms a management closed loop centered on primary key encoding, covering language, time, permissions, and alarms, possessing significant advantages such as cross-regional compatibility, high compatibility, scalability, and user-friendly engineering deployment. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 The first embodiment of the present invention provides an overall flowchart of a global, multilingual, multi-time zone power plant management method.

[0021] Figure 2 This is a schematic diagram of a global multilingual and multi-time zone power plant management system provided for the third embodiment of the present invention. Detailed Implementation

[0022] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0023] Example 1, referring to Figure 1 As an embodiment of the present invention, a multilingual, multi-time zone power plant management method for global applications is provided, comprising:

[0024] S1: Collect power plant data, standardize and identify it, and construct a multi-level coding identifier primary key for the power plant.

[0025] Furthermore, firstly, for data from different countries and different types of power plants, a unique primary key identifier is established based on a unified three-category coding rule for subsequent data processing, language mapping, time zone control, and access management. This step specifically includes the following three sub-processes:

[0026] 1. Power plant signage construction:

[0027] The power plant identification uses a five-segment combination coding method, including the company code (C1), country code (U1), power plant code (U4), and unit type code (U8), etc., with the overall structure as follows: Figure 2 As shown, each power plant's primary key code can uniquely identify a power generation unit under a specific country and company, forming a basic unit for cross-language / cross-regional management and control.

[0028] 2. Equipment Identification System Construction:

[0029] The equipment identification adopts a three-layer nested structure of full factory code (H field), system code (S field), and equipment code (T field).

[0030] 3. Signal Identification Construction:

[0031] The signal identifier consists of three parts: signal category (status signal DQ / measurement signal AQ), signal name, and signal number. For example, DQ·GNStrStopProOp01 indicates "start-stop protection operation status signal No. 1", and AQ·SpdPct03 indicates "spindle speed percentage measurement signal No. 3".

[0032] Signal labels are categorized into hydropower, wind power, and photovoltaic power to ensure consistency in the basic framework for adapting to diverse languages.

[0033] It should be noted that the power plant data is categorized according to Table 1.

[0034] Table 1. Classification of Power Plant Data Dimensions

[0035] Dimension Data types 1. Time dimension Real-time data, historical data, planned data, event data 2. Content Dimension Status data, measurement data, alarm data, control commands 3. Spatial Dimension Company-level, national-level, power plant-level, equipment-level, signal-level 4. System Dimension Main system data, auxiliary system data, security system data 5. Type Dimension Data specific to hydropower, wind power, and photovoltaic power types

[0036] It should also be noted that the power station identification data includes the company code (e.g., 1085, representing Three Gorges International), the country code (e.g., 586, representing the country of origin), the power station code (e.g., 6045, representing a unique number for a power station), and the unit type code (e.g., 0116, representing hydropower / wind power / photovoltaic unit type). This is used to construct a multi-level coding identification primary key for power stations, which is integrated into data classification, access control, time zone mapping, and visualization.

[0037] Equipment structure and classification data include plant-wide codes (e.g., 01-99, representing a single or multiple units), system codes (e.g., MKA for generator system, MSA for outgoing line system), and equipment codes (e.g., BT001 for temperature sensor, QB004 for disconnector). System classifications include main transformer system, cooling system, speed control system, grid connection system, communication system, safety monitoring system, etc.

[0038] All devices are bound to the system architecture, which is subdivided into modules. Each device's data has a corresponding primary key and a set of collectable signals.

[0039] Real-time measurement data includes: voltage, current, frequency, active power, reactive power, power factor, temperature (oil temperature, water temperature, bearing temperature, etc.), pressure (guide vane oil pressure, inlet water pressure, lubricating oil pressure, etc.), water level (upper water level, tailwater level, surge tank water level, etc.), rotational speed (main shaft, fan, generator, etc.), and flow rate (needle flow rate, overflow rate, total output water volume, etc.). Each measurement signal is coded with "AQ·" as the first letter, and combined with the signal name and number to form a unique identifier. Status monitoring data includes: start / stop status, operating mode (grid-connected, islanded, phase-adjusted, etc.), fault alarm signs (such as temperature exceeding limits, vibration exceeding limits, abnormal water level), gate open / close position, electrical component status (circuit breaker, disconnector, grounding switch, etc.), and control authority (local / remote, manual / automatic). Status signal codes begin with "DQ·" and are used to drive the alarm system, logic judgment, and control response.

[0040] Event and alarm data include: alarm level (normal, early warning, emergency), alarm source device / signal (associated with DQ signal), alarm trigger time (with country code + time zone offset), alarm description (multi-language mapping available), alarm handling process, handling suggestions, confirmation status, etc. Alarm events are strongly bound to the measurement point signal code, making it an important data source for operational data analysis, statistical benchmarking, and intelligent recommendations.

[0041] The planned / reported data includes: power plant inspection plans, operation and maintenance reports (maintenance plans, material declarations), technical renovation / overhaul project progress data, technical ledgers and equipment information entry. This type of data is structured form data, usually filled out by people, and supports language switching and approval process-driven processing.

[0042] Operation and control command data include: remote / local control commands (closing / opening, starting / stopping, etc.), power / voltage / frequency control settings, dispatch command records, authorization confirmation and command feedback links. Control data is output action triggered by status signals and authorization fields, and its encoding structure depends on the aforementioned primary key system.

[0043] S2: By using the power station's multi-level coding identifier primary key as the driver to build a multilingual mapping system, and using standardized identifiers to build time zone offset logic.

[0044] Furthermore, each signal name is a logical phrase composed of standardized abbreviations (such as Spd, Tmp, Flw), which can be used to represent measurement or status information such as spindle speed, temperature, and flow rate.

[0045] To achieve language-independent expression logic, signal encoding (such as AQ·SpdPct, DQ·BrkOn) is used as the unique retrieval anchor point during data application. A language tag table is established, and the meanings of different languages ​​are bound according to the following structure: Chinese tag example: spindle speed percentage, brake function on; English tag example: Speed ​​Percentage, Brake Function On.

[0046] The constructed language mapping table is shown in Table 2.

[0047] Table 2 Language Mapping Table

[0048] Signal encoding (primary key) Chinese name English name French name (can be expanded) DQ·BrkOn Braking function activated Brake Function On Frein activé AQ·SpdPct Speed ​​percentage Speed ​​Percentage Pourcentage de vitesse

[0049] The field labels corresponding to the equipment code BT001 can be "Oil Temperature Sensor" (Chinese) or "Oil Temperature Sensor" (English); the field unit descriptions such as "℃" or "MPa" are also unrelated to the language, but the "Explanation" section can display "Celsius" or "Megapascals" depending on the language.

[0050] It should be noted that, in terms of language processing of state values, state classification abbreviations can be directly compared with their Chinese and English meanings.

[0051] For example: status abbreviation BrkOn → Chinese: “Brake Function On”, English: “Brake Function On”; status abbreviation FluwMax → Chinese: “Flow Reached Maximum”, English: “Flow Reached Maximum”.

[0052] It should also be noted that during subsequent processing or presentation, the country code information can be parsed to select a preset language for default language binding.

[0053] For example: when the country code is "156" (China), Chinese is displayed by default; when the country code is "250" (France), French or English is displayed by default.

[0054] The binding relationship between country codes and language preferences can be defined by a mapping table, which drives the initial display language of field labels and descriptions.

[0055] Furthermore, the power plant identification consists of a company code, a country code, a power plant code, and a unit type code, with each country corresponding to a unique three-digit number.

[0056] It should be noted that by constructing a mapping table from country code to standard time zone, the power station can automatically associate the corresponding standard time offset value based on the country code field in its primary key during data collection, processing, or presentation.

[0057] It should also be noted that all operational data records adopt the unified UTC time format. During the storage and exchange of power plant data, records should be made using UTC timestamps to eliminate comparison errors caused by cross-time zone data recording. For example, operational logs, event times, alarm trigger times, reporting times, control response times, etc., should be stored using the unified format "YYYY-MM-DD HH:MM:SSUTC".

[0058] Furthermore, based on the country code field contained in the primary key of the multi-level coded identifier of the power plant, in scenarios where data time needs to be displayed, the UTC time is converted to the local time of the target country: the offset value is added to the original UTC timestamp.

[0059] If a country observes daylight saving time, the daylight saving time rules can be found by referring to the country code and adjustments can be made accordingly.

[0060] When generating reports, graphs, and alarm texts, the local time format is automatically used to ensure local consistency in time expression.

[0061] Example: UTC record is 2025-05-16 08:00:00, country code is 250, local time is 2025-05-16 09:00:00.

[0062] S3: Implement hierarchical access control based on the primary key prefix of the multi-level coding identifier of the power station and generate local alarm prompts.

[0063] Furthermore, according to the project's hierarchical management architecture, power plant data management is divided into a three-tier structure: the group headquarters layer (company level), the regional company layer (national level), and the power plant layer (specific site level). This structure can be directly mapped to the prefix field of the power plant's primary key, as shown in Table 3.

[0064] Table 3 Primary Key Prefix Table

[0065] Management level Corresponding primary key field Example value Headquarters-level management Company Code 1085 Regional company management Country Code 250 Power plant level management Power station code 6045

[0066] It should be noted that, according to the management logic, permission checks during data access can be performed as follows:

[0067] Determine if a user has permission to access all data items in the power plant primary key where the company code is "1085"; if their permission is limited to the country code "250", they can access all data related to French power plants; if their permission is limited to the power plant code "6045", they can only read data related to that site; all read and write operations must be determined by prefix matching between the primary key prefix and the user's permission range.

[0068] It should also be noted that language pack loading and time zone conversion should be controlled by the permission domain: if a user only has permission for the country code "250", the system will only load the language tags and time zone mappings for the French power station; for power stations without access permissions, their language resources and time conversion logic will not be loaded or displayed; the execution logic for multiple languages ​​and multiple time zones is restricted by the primary key prefix permission to ensure that data cannot be accessed beyond the user's authority or misread.

[0069] Access control not only restricts "whether access is possible", but also constrains "whether it can be correctly presented in the local context".

[0070] Furthermore, by adding a primary key field to all operational actions or alarm data, the following can be achieved: alarm content can be categorized by primary key prefix; the operator's permission prefix and the target data's primary key can be added to the operation record to form a tracking chain; alarm pushes can only target the data range covered by the permissions (for example, a fault alarm from a power plant will not be sent to personnel outside the area).

[0071] To determine the priority of alarm text display and push under specific language, permissions, time, and time zone, and to achieve accurate and personalized alarm information management and display, an alarm text mapping function is constructed as follows:

[0072]

[0073] Where Ψ is the final alarm text mapping index, L is the target language code, S is the signal code, P is the user permission level, T is the alarm time (UTC format), Z is the time zone number corresponding to the country code, Γ is the semantic mapping strength between language and signal code, Θ is the adjustment weight of permission and signal mapping, Ω is the dynamic intervention factor of time and time zone, α is the language mapping contribution adjustment parameter, β is the permission mapping contribution adjustment parameter, γ is the time and time zone intervention adjustment parameter, and σ k For the weight adjustment of the k-th semantic dimension, χ k e is the distance amplification factor for the k-th semantic dimension. L Let v be the vector representation of language L. S Let d be the vector representation of signal S.E δ represents the Euclidean distance between semantic vectors. j Let φ be the weight of the j-th permission category. j (P) is the scoring function for the j-th permission level, τ j (S) represents the sensitivity of encoding the j-th signal, κ j Δ represents the intensity of the signal's adjustment to the permission response. Z ρ is the hour offset of time zone Z, and ρ is the dynamic adjustment constant of time zone.

[0074] The language-signal coding mapping function Γ(L,S) is expressed as:

[0075]

[0076] Among them, e L Let v be the semantic vector of language L. S d is the eigenvector of the signal encoding S. E Let σ be the Euclidean distance between the two. k , χ k These are the adjustment factors for each semantic dimension.

[0077] The permission-signal weight mapping function Θ(P,S) is expressed as:

[0078]

[0079] Where, δ j φ represents the weight of the j-th permission type. j (P) represents the score at the j-th permission level, τ j (S) represents the alarm sensitivity of the signal code S, κ j This indicates a regulatory factor.

[0080] The time-time zone dynamic intervention function Ω(T,Z) is expressed as:

[0081]

[0082] Where T represents UTC time, Δ Z ρ represents the UTC hour offset of time zone Z, and ρ represents the time zone adjustment constant.

[0083] It should be noted that the status signals include start / stop signals, fault status, protection actions, etc., and their encoding structure is as follows: starting with DQ·; the signal name adopts a standard abbreviation structure, such as DQ·GNStrStopProOp01 (representing start / stop protection action 1); the judgment logic of alarm events is: when the status signal value reaches a certain preset judgment condition (such as "1" being the trigger state), an alarm is triggered.

[0084] It should also be noted that after an alarm event is triggered, the language description content corresponding to the signal encoding is called to construct the alarm text as shown in Table 4.

[0085] Table 4 Alarm Text List

[0086] Fields Content Example (Chinese) Content Example (English) Signal encoding DQ·BrkFlt DQ·BrkFlt Alarm Title Brake Failure Alarm Brake Fault Alarm Alarm Description Brake malfunction detected, please check. Brake fault detected Alarm Level urgent Critical

[0087] Furthermore, the alarm trigger time is recorded in UTC time. During the alarm generation phase, based on the country code field in the power plant primary key, the local time offset is extracted from the established time zone mapping relationship, and the time is localized: UTC time: 2025-05-16 08:00:00; Country code: 250 (UTC+1); Alarm time is displayed as: 2025-05-16 09:00:00 (local time).

[0088] It should be noted that different levels can view alarm data within their corresponding ranges. The display, push, and attribution of alarm information must strictly refer to the company code, country code, power plant code, and other fields contained in the primary key of the data item for classification, and be aligned with the established access control mechanism: if the country code in the alarm primary key is 250, but the recipient's permission is limited to country code 818, then it will not be displayed; at the same time, the language description and time information in the alarm content will only load the content corresponding to the data within the permission range; the alarm response and processing records will be included in the power plant behavior record system bound to the permissions.

[0089] It should also be noted that after the alarm information is generated, it can be sent via SMS, email, mobile message, etc. The push content uses the signal code as an index to dynamically generate multilingual template text, and adds the following structural information: alarm time (local), alarm source device name (device code + signal description), alarm level, and current processing status (pending confirmation, processing, closed).

[0090] Example 2, refer to Figure 2 As an embodiment of the present invention, a multilingual and multi-time zone power plant management system for global use is provided, including a power plant multi-level coding primary key construction module (100), a multilingual and multi-time zone adaptation module (200), and an access control and multilingual alarm response module (300).

[0091] S4: Power Plant Multi-level Encoding Primary Key Construction Module (100) is used to collect structured management elements in the operation of the power plant, including company affiliation, national division, power plant identity, unit characteristics, equipment classification, signal type, etc. By constructing three types of encoding fields, namely power plant identifier, equipment identifier and signal identifier, a unified power plant multi-level encoding primary key is formed, which is used as a unique data anchor for subsequent language adaptation, permission judgment and alarm generation.

[0092] It should also be noted that the power plant multi-level coding primary key construction module (100) completes the format verification and structure classification of each level of coding fields: the power plant identification field includes the company code, country code, power plant code, and unit type code; the equipment identification field includes the plant-wide code, system code, and equipment type code; the signal identification field includes the signal category, signal name, and sequence number. The completed primary key structure will be passed to the multi-language and multi-time zone adaptation module (200) as driving parameters and provided to the access control and multi-language alarm response module (300) to perform primary key matching.

[0093] S5: Multilingual and multi-timezone adaptation module (200) is used to construct multilingual tag mapping and national timezone offset control logic based on the input power plant multi-level coded primary key. This module extracts signal codes and retrieves their logical phrase names. By establishing a mapping relationship between the coded field and the multilingual term table, it dynamically binds semantic tags for languages ​​such as Chinese and English, and passes the language mapping structure into the subsequent alarm description and field display process for invocation.

[0094] It should also be noted that the multilingual and multi-timezone adaptation module (200) simultaneously extracts the country code field from the primary key, finds the mapping relationship between the country code and the UTC offset, and uniformly uses UTC time recording when performing time tagging, alarm generation, and event recording on the running data. In the display and push stages, it is converted to the local time format for output according to the offset rules. The generated language tag set and local time data will be referenced by the access control and multilingual alarm response module (300).

[0095] S6: The access control and multilingual alarm response module (300) receives the encoded primary key, language label, and local time information, and performs permission boundary determination and alarm response output operations. This module identifies the company code, country code, and power plant code in the primary key prefix to perform multi-level permission matching and judgment, which is used to filter the data access scope and control the language resource loading boundary.

[0096] It should also be noted that after recognizing the status signal code, the access control and multilingual alarm response module (300) triggers an alarm generation action according to the judgment logic, calls the language template content and time information that match the signal code to construct the alarm text; then, according to the access control rules, the alarm is pushed to the user with the access rights, and is accompanied by information such as primary key field, time interval, signal status, language content, and processing status label; at the same time, the execution record, alarm status and multilingual description results are bound and written to the log field for tracking, auditing and secondary analysis. If there is a permission conflict or language loading abnormality, the multilingual and multi-time zone adaptation module (200) performs language completion or the power plant multi-level encoding primary key construction module (100) relocates the encoding primary key.

[0097] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the 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 cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0098] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0099] More specific examples (a non-exhaustive list) of computer-readable media include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0100] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc. It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A global, multilingual, multi-time zone power plant management method, characterized in that: include: Collect power plant data, standardize and label it, and construct a multi-level coding identifier primary key for the power plant; A multilingual mapping system is constructed by using the primary key of the power plant's multi-level coding identifier as the driver, and time zone offset logic is constructed using standardized identifiers; Hierarchical access control is implemented based on the primary key prefix of the multi-level coding identifier of the power station, and local alarm prompts are generated. The standardized identification of collected power plant data includes using power plant identifiers to construct a unique identifier combination for the power generation company, country, power plant, and unit; using equipment identifiers to distinguish between the whole plant code, system code, and equipment category and number; and using signal identifiers to encode each measurement value or status value to distinguish its type, source, and purpose. The hierarchical access control includes dividing the multi-level coding primary key prefix of the power station into company-level, national-level, and power station-level access scopes. User permissions are filtered by binding the multi-level coding primary key range of the power station. All operation logs and data audit records are based on the multi-level coding primary key of the power station, thus constructing a multi-level record structure.

2. The global multilingual and multi-time zone power plant management method as described in claim 1, characterized in that: The power station data includes, Power plant identification data, equipment structure and classification data, real-time measurement data, status monitoring data, event and alarm data, planning and reporting data, and operation and control command data.

3. The global multilingual and multi-time zone power plant management method as described in claim 2, characterized in that: The construction of the power plant multi-level coded identifier primary key includes: Construct primary keys for power plant coding identifiers, equipment coding identifiers, and signal coding identifiers; The power plant coding identifier primary key adopts a five-segment combination coding method, including company code, country code, power plant code, and unit type code; Construct a primary key for equipment coding identification, adopting a three-layer nested structure of plant code, system code, and equipment code. The three characters of the system code correspond to the hydropower station system code, and the two characters of the equipment code, the classification code and the number, correspond to the power station equipment code. Construct a primary key for signal encoding identification, which consists of three parts: signal category, signal name, and signal number.

4. The global multilingual and multi-time zone power plant management method as described in claim 3, characterized in that: The method of constructing a multilingual mapping system by using the power station's multi-level coded identifier primary key as the driving force includes... Based on the signal name index and naming rules, the power station's multi-level coding identifier primary key corresponds to the logical phrase; Using signal encoding as the retrieval anchor, a language tag table is constructed and bound according to Chinese tag examples and English tag examples to establish a multilingual mapping system between the power station's multi-level coded identifier primary key and semantic description; For state value processing, state classification abbreviations are compared with their Chinese and English meanings.

5. The global multilingual and multi-time zone power plant management method as described in claim 1, characterized in that: The logic for constructing the time zone offset includes, Extract the country code field to locate the power station's time zone, and automatically associate the corresponding standard time offset value based on the country code field in the power station's multi-level coding identifier primary key; During the storage and exchange of power plant data, UTC timestamps are used for recording to eliminate comparison errors of data records across time zones; Based on the country code field contained in the primary key of the constructed power plant multi-level coding identifier, UTC time is converted to the local time of the target country when the data time needs to be displayed.

6. The global multilingual and multi-time zone power plant management method as described in claim 5, characterized in that: The method of hierarchical access control based on the primary key prefix of the power plant multi-level coding identifier and generating local alarm prompts includes... The power plant data management is divided into a three-level structure and mapped to the prefix field of the power plant's multi-level coded identifier primary key, thus constructing an access control mechanism for matching the prefix of the power plant's multi-level coded identifier primary key. Restrict language loading and timezone resolution to be performed within the scope of permissions; If a user only has permission for the country code, the system will only load the language tag and time zone mapping of the station. For stations without permission, language resources and time conversion logic will not be loaded or displayed. The execution logic for multiple languages ​​and time zones is subject to permissions restrictions imposed by the primary key prefix of the power plant's multi-level coding identifier. By combining the power plant multi-level coding identifier primary key structure, a power plant multi-level coding identifier primary key field is added to all operation behaviors or alarm data. The alarm content is classified according to the power plant multi-level coding identifier primary key prefix. The operation record is added with the operator's permission prefix and the target data power plant multi-level coding identifier primary key to form a tracking chain. The permission determination mechanism includes determining whether a user has permission to access all data items in the multi-level coding identifier primary key of the power station where the company code is; If the access is restricted to the country code, then access to all power plant data is permitted; If the access is limited to the power station code, then read the data related to accessing the power station site; All read and write operations are determined by prefix matching between the power station's multi-level coding identifier primary key prefix and the user's permission range.

7. The global multilingual and multi-time zone power plant management method as described in any one of claims 5 and 6, characterized in that: The method of hierarchical access control based on the primary key prefix of the power plant multi-level coding identifier and generating local alarm prompts includes... Identify status signal codes to trigger alarm events. Identify status signals, including start / stop signals, fault status, and protection actions. The coding structure begins with DQ, and the signal name uses a standard abbreviation structure. The alarm event determination logic is as follows: if the status signal value reaches the threshold, an alarm is triggered. After an alarm event is triggered, the language description content corresponding to the signal encoding is called to construct the alarm text; The alarm trigger time is recorded in UTC time. During the alarm generation stage, the local time offset is extracted from the area mapping relationship based on the country code field in the primary key of the power plant's multi-level coding identifier, and the time is localized. The construction of alarm text includes restricting the visibility of alarm content within the authorized scope, classifying it according to the company code, country code, and power plant code contained in the primary key of the power plant multi-level coding identifier, and connecting it with the time zone offset logic: Alarm information is pushed out after it is generated. The push content is indexed by the signal code, dynamically outputs multilingual template text, and includes the alarm time, alarm source device name, and current processing status.

8. A global multilingual and multi-time zone power plant management system, employing the global multilingual and multi-time zone power plant management method as described in any one of claims 1 to 7, characterized in that: It includes a power plant multi-level coding primary key construction module (100), a multi-language and multi-time zone adaptation module (200), and an access control and multi-language alarm response module (300); The power plant multi-level coding primary key construction module (100) is used to construct a unified primary key coding system composed of power plant identifier, equipment identifier and signal identifier; The multi-language and multi-time zone adaptation module (200) is used to drive the language label mapping and the time zone offset corresponding to the country code based on the primary key; The access control and multilingual alarm response module (300) is used to implement hierarchical access control using primary key prefixes, and to trigger the generation, time stamping and push of multilingual alarm content within permissions using signal encoding.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the global multilingual multi-time zone power plant management method as 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 the global multilingual multi-time zone power plant management method as described in any one of claims 1 to 7.

Images