Automatic conversion method and system from power system model data to ETAP software, computer equipment and storage medium

Abstract

The invention discloses an automatic conversion method and system for power system model data to ETAP software, computer equipment and a storage medium. The method comprises the steps that CIM / E XML and an associated SVG file are analyzed and loaded; extracting element entities of the power system and association relationships thereof; according to a predefined mapping rule base, mapping the CIM / E entity attributes into element parameters corresponding to the ETAP software; the compatibility problem of model difference and missing data is solved; and finally generating a data file which can be directly identified and imported by the ETAP software. According to the method, seamless data connection between a power grid general standard and professional simulation software is realized, and the efficiency and accuracy of simulation modeling of a power system are greatly improved.

Description

Technical Field

[0001] This invention relates to the field of power system simulation and data processing technology, and in particular to an automatic conversion method, system, computer equipment, and storage medium for power system model data to ETAP software. Background Technology

[0002] CIM / E is an abbreviation for CIM (Common Information Model) / Energy, specifically referring to a common information model defined in the power energy field based on the IEC 61970 and IEC 61968 series of international standards. Its core objective is to achieve interoperability between different application software in power systems. IEC 61970 is the Energy Management System (EMS) Application Programming Interface (API) standard, which defines a common vocabulary for describing the physical and logical structure of power systems, primarily focusing on transmission networks and generation. Examples include core power equipment such as generators, transformers, transmission lines, circuit breakers, and busbars, and their interconnections. IEC 61968 is the Distribution Management System (DMS) API standard, which, building upon 61970, adds numerous classes and attributes needed to describe distribution networks, the consumer side, and asset management, such as models of distribution transformers, distribution feeders, meters, and customers. CIM / E documents provide a detailed description of the power system model through components and relationships.

[0003] ETAP (Electrical Transient Analysis Program) is a globally used power system simulation and analysis software developed by ETAP Corporation, Inc. It is widely used in the design, analysis, optimization, and operation and maintenance management of power systems, covering multiple fields such as power generation, transmission, distribution, and industrial power systems. In ETAP, XML format is used to define the input file for the power system model, containing information such as equipment parameters, connection relationships, and simulation configuration. The equipment parameters also include the size and location of components.

[0004] In power system modeling, CIM / E and ETAP employ different data representation methods, resulting in significant differences in syntax, semantics, and model granularity. These differences complicate direct data conversion, requiring specialized mapping rules and conversion algorithms. Structurally, CIM / E is based on a loosely linked collection of objects referenced by URIs, while ETAP is based on a flattened table. Regarding data association, CIM / E uses rdf:ID and rdf:resource references, while ETAP uses IID (internal ID) and direct association via FromElement / ToElement in CONNECT. CIM / E's ConnectivityNode requires additional parsing to map to ETAP's BUS. Furthermore, CIM / E and ETAP differ in device naming, parameter definition, unit systems, and topology representation. In terms of models, for example, CIM / E's transformer model uses PowerTransformer and multiple TransformerWinding objects, while ETAP directly defines high and low voltage side parameters using a single class, XFORM2W. Regarding line parameters, CIM / E suffers from missing zero-sequence parameters.

[0005] In the field of power system modeling, data conversion between CIM / E and ETAP still faces many challenges. Currently, most conversion methods rely on manual methods, which suffer from low efficiency, error-proneness, and poor scalability. Summary of the Invention

[0006] The purpose of this invention is to provide an automatic conversion method, system, computer equipment, and storage medium for power system model data to ETAP software, which solves the technical problems of most existing conversion methods relying on manual operation, resulting in low efficiency, error susceptibility, and poor scalability.

[0007] To achieve the above objectives, the present invention is implemented through the following technical solutions.

[0008] An automatic conversion method for power system model data to ETAP software includes:

[0009] The file input module receives CIM / E standard format XML files and corresponding SVG graphic files.

[0010] The parsing module parses the XML file to construct a power system component object model based on the CIM standard, and simultaneously parses the SVG file to obtain the spatial coordinate information of each component.

[0011] The conversion engine module calls the predefined mapping rules in the mapping rule library to map and match the elements in the CIM standard component objects with the elements in the ETAP software database. The mapping rules define the correspondence between CIM types and ETAP component types, and between CIM attributes and ETAP parameters.

[0012] The topology processing engine module reconstructs the electrical connection topology required by ETAP based on the relationship between Terminal and ConnectivityNode in CIM / E, automatically converts ConnectivityNode into BUS element in ETAP, and generates the corresponding connection relationship.

[0013] The file output module generates and outputs a data file that can be recognized by the ETAP software based on the matching results. The data file format is either the ETAP XML project file format or a data format that can be imported in batches via API.

[0014] The aforementioned automatic conversion method from power system model data to ETAP software involves, if the file input module receives multiple sets of CIM / E files, performing element coordinate calibration and merging processing on the multiple network topologies formed therefrom to generate a unified ETAP model.

[0015] The aforementioned automatic conversion method from power system model data to ETAP software, wherein the element coordinate calibration and merging process for the resulting multiple network topologies includes:

[0016] Assign a separate coordinate space offset to each individual CIM / E file to avoid overlapping of component graphics during merging.

[0017] For elements with the same rdf_ID in all files, merge their attributes and take the minimum or average value of all coordinate points of that element in all files.

[0018] The aforementioned automatic conversion method from power system model data to ETAP software uses a predefined mapping rule table; the mapping rules include:

[0019] The AC line segment in the CIM model is mapped to the CABLE and XLINE models in ETAP based on the PSRType attribute.

[0020] The Substation, BusbarSection, and ConnectivityNode in the CIM model are uniformly mapped to the BUS model in ETAP.

[0021] In the CIM model, Breaker, LoadBreakSwitch, and Disconnector are converted to switch models in ETAP according to their voltage levels. Breakers of 10kV and above are converted to HVCB (High Voltage Circuit Breaker), and Breakers of 10kV and below are converted to LVCB (Low Voltage Circuit Breaker).

[0022] The PowerTransformer (transformer) and its contained PowerTransformerEnd (transformer winding) in the CIM model are converted into the XFORM2W (two-winding transformer) model in ETAP.

[0023] The EnergyConsumer (access point load) in the CIM model will be converted into the LUMPEDLOAD (load) model in ETAP.

[0024] The aforementioned automatic conversion method from power system model data to ETAP software further includes rules for handling model differences, which include:

[0025] When the line ACLineSegment in the CIM model provides a text description of linetype and length, the preset line impedance parameter calculation subsystem queries and calculates the required resistance, reactance, zero-sequence resistance, and zero-sequence reactance parameters in ETAP.

[0026] When the parameters in the CIM model do not have direct corresponding parameters in ETAP, the default values ​​or the values ​​are derived and assigned using formulas based on electrical calculation principles. For example, a default proportional rated capacity simulation load is automatically added to the transformer model, and the default capacity and simulation load are set for the transformers used in the substation.

[0027] When there are components in the CIM model that are not supported by ETAP, a strategy of ignoring them or replacing them with the closest equivalent component is adopted.

[0028] The aforementioned automatic conversion method from power system model data to ETAP software, wherein the topology processing engine module reconstructs the topology structure, includes:

[0029] Iterate through all ConnectivityNode objects and categorize the devices they connect to into bus devices and non-bus devices.

[0030] If a connection point is associated with a bus device, all connections of that connection point are aggregated to that bus device, and a unique pin number is assigned to each connection.

[0031] If a connection point is not associated with any bus device, a new ETAP bus is created with its average coordinates, and all devices under that connection point are connected to the new bus.

[0032] An automatic conversion system for power system model data to ETAP software includes:

[0033] The file input module is used to receive CIM / E XML (model) and SVG (graphic) files.

[0034] The parsing module is used to parse XML and build a CIM object model, while also parsing SVG (graphics) files to obtain component coordinates.

[0035] The mapping rule base is used to store the mapping relationship between CIM and ETAP.

[0036] The topology processing engine module is used to reconstruct the connection topology based on the relationship between Terminal and ConnectivityNode, and to handle the coordinate space allocation when merging multiple files.

[0037] The transformation engine module is used to perform mapping and generate ETAP data.

[0038] The file output module is used to output the converted ETAP project file and the component rdf_ID mapping table;

[0039] The output of the file input module is connected to the parsing module, the output of the parsing module is connected to the conversion engine module, the output of the conversion engine module is connected to the topology processing engine module, and the output of the topology processing engine module is connected to the file output module.

[0040] The aforementioned automatic conversion system from power system model data to ETAP software includes a pre-installed line impedance parameter calculation subsystem in the mapping rule database, comprising:

[0041] A line impedance database for storing parameters of positive-sequence resistance, positive-sequence reactance, zero-sequence resistance, and zero-sequence reactance per unit length for common cable or conductor models at different cross-sectional areas.

[0042] A model parsing submodule is used to extract cable model and cross-sectional area information from the cable model string provided in the CIM file using regular expressions.

[0043] A parameter query submodule is used to query and return the corresponding impedance parameters from the line impedance database based on the extracted model and cross-sectional area, and then populate the ETAP cable model.

[0044] A computer device includes a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method.

[0045] A computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implement the steps of the method.

[0046] The beneficial effects of this invention are as follows: This invention provides an automatic conversion method, system, computer equipment, and storage medium for power system model data to ETAP software. This solves the problems of low efficiency, error susceptibility, and poor scalability inherent in most existing conversion methods, which rely on manual processes. It achieves seamless data integration between general power grid standards and professional simulation software, greatly improving the efficiency and accuracy of power system simulation modeling. Furthermore, this invention deeply integrates CIM / E's XML (model) and SVG (graphics) parsing, implementing a Terminal-ConnectivityNode-based automatic topology reconstruction algorithm, a multi-CIM / E file coordinate space allocation and model merging mechanism, and an automatic electrical parameter mapping database. This enables fully automatic, high-fidelity conversion from CIM / E to ETAP, reducing manual reconstruction workload and supporting complex power grid models, thus possessing industrial application value. Attached Figure Description

[0047] Figure 1 This is a schematic diagram illustrating the principle of an automatic conversion method from power system model data to ETAP software according to Embodiment 1 of the present invention.

[0048] Figure 2 This is a schematic diagram of the structure of an automatic conversion system from power system model data to ETAP software according to Embodiment 2 of the present invention;

[0049] Figure 3 This is a simplified power system model diagram in Embodiment 3 of the present invention. Detailed Implementation

[0050] The technical solution of the present invention will be further described below with reference to the accompanying drawings and specific embodiments.

[0051] Example 1: As Figure 1 As shown, this embodiment provides an automatic conversion method for power system model data to ETAP software, including:

[0052] Step 1: The file input module receives an XML file in CIM / E standard format and the corresponding SVG graphic file.

[0053] Step 2: The parsing module parses the XML file to construct a power system component object model based on the CIM standard, and at the same time parses the SVG file to obtain the spatial coordinate information of each component.

[0054] Step 3: The conversion engine module calls the predefined mapping rules in the mapping rule library to map and match the elements in the CIM standard component objects with the elements in the ETAP software database. The mapping rules define the correspondence between CIM types and ETAP component types, and between CIM attributes and ETAP parameters.

[0055] Step 4: The topology processing engine module reconstructs the electrical connection topology required by ETAP based on the relationship between Terminal and ConnectivityNode in CIM / E, automatically converts ConnectivityNode into BUS element in ETAP, and generates the corresponding connection relationship.

[0056] Step 5: The file output module generates and outputs a data file that can be recognized by the ETAP software based on the matching results. The data file format is either the ETAP XML project file format or a data format that can be imported in batches via API.

[0057] In step three, the mapping rule is a configurable mapping rule table, including:

[0058] The ACLineSegment in the CIM model is mapped to the CABLE (cable) and XLINE (transmission line) models in ETAP according to the PSRType attribute;

[0059] The Substation, BusbarSection, and ConnectivityNode in the CIM model are uniformly mapped to the BUS model in ETAP;

[0060] In the CIM model, Breaker, LoadBreakSwitch, and Disconnector are converted into switch models in ETAP according to their voltage levels. 10kV and above are converted into HVCB (High Voltage Circuit Breaker), and 10kV and below are converted into LVCB (Low Voltage Circuit Breaker).

[0061] The PowerTransformer (transformer) and its contained PowerTransformerEnd (transformer winding) in the CIM model are converted into the XFORM2W (two-winding transformer) model in ETAP.

[0062] Convert the EnergyConsumer (access point load) in the CIM model into the LUMPEDLOAD (load) model in ETAP.

[0063] In step three, the mapping rules also include rules for handling model differences, including:

[0064] When the line ACLineSegment in the CIM model provides a text description of linetype and length, the required resistance (R), reactance (X), zero-sequence resistance (R0), and zero-sequence reactance (X0) parameters in ETAP are queried and calculated through the preset line impedance parameter database (as described in claim 7).

[0065] When parameters in the CIM model do not have direct corresponding parameters in ETAP, default values ​​or values ​​derived from formulas based on electrical calculation principles are used. For example, a simulated load with a default proportion of rated capacity is automatically added to the transformer model. For instance, default capacity and simulated load are set for all transformers used in a substation.

[0066] When there are components in the CIM model that are not supported by ETAP, a strategy of ignoring them or replacing them with the closest equivalent component is adopted.

[0067] In step four, the topology reconstruction specifically includes: traversing all ConnectivityNode objects and classifying the devices they connect to into two categories: bus devices (BusbarSection, StationZB) and non-bus devices; if a connection point is associated with a bus device, then all connections of that connection point are aggregated to that bus device, and a unique pin number is assigned to each connection; if a connection point is not associated with any bus device, then a new ETAP bus is created with its average coordinates, and all devices under that connection point are connected to the new bus.

[0068] In step five, if the file input module receives multiple sets of CIM / E files, the element coordinates of the multiple network topologies formed by them are calibrated and merged to generate a unified ETAP model.

[0069] The multi-file merging process includes: assigning an independent coordinate space offset (deltaX, deltaY) to each independent CIM / E file to avoid overlapping of component graphics during merging; merging the attributes of components with the same rdf_ID in all files, and taking the minimum or average value of all coordinate points of the component in all files.

[0070] Example 2: As Figure 2As shown, this embodiment provides an automatic conversion system for power system model data to ETAP software, including:

[0071] The file input module is used to receive CIM / E XML and SVG files.

[0072] The parsing module is used to parse XML and build a CIM object model, and also parse SVG files to obtain component coordinates.

[0073] The mapping rule base is used to store the mapping relationship between CIM and ETAP.

[0074] The topology processing engine module is used to reconstruct the connection topology based on the relationship between Terminal and ConnectivityNode, and to handle the coordinate space allocation when merging multiple files.

[0075] The transformation engine module is used to perform mapping and generate ETAP data.

[0076] The file output module is used to output the converted ETAP project file and component ID mapping table.

[0077] The output of the file input module is connected to the parsing module, the output of the parsing module is connected to the conversion engine module, the output of the conversion engine module is connected to the topology processing engine module, and the output of the topology processing engine module is connected to the file output module.

[0078] The mapping rule database is pre-configured with a line impedance parameter calculation subsystem, including:

[0079] A line impedance database for storing parameters of positive-sequence resistance, positive-sequence reactance, zero-sequence resistance, and zero-sequence reactance per unit length for common cable or conductor models at different cross-sectional areas;

[0080] A model parsing submodule is used to extract cable model and cross-sectional area information from the cable model string provided in the CIM file using regular expressions;

[0081] A parameter query submodule is used to query and return the corresponding impedance parameters from the line impedance database based on the extracted model and cross-sectional area, and then populate the ETAP cable model.

[0082] Example 3: As Figure 3 As shown, this embodiment aims to demonstrate the workflow of the conversion method step by step using a simplified power system model, including a busbar, a circuit breaker, a transformer, and a load. The described steps essentially correspond to the method claims in the claims section.

[0083] Step 1: Parse the input file.

[0084] Receive and parse XML files and SVG files in CIM / E format. The following provides a simplified XML code snippet showing how to define components such as BusbarSection (busbar), Breaker (circuit breaker), PowerTransformer (transformer), EnergyConsumer (load), ConnectivityNode (connection point), and Terminal (terminal) and their associated relationships using the CIM standard. At the same time, parse the SVG file to obtain the spatial coordinates of these components.

[0085] <!-- Busbar -->

[0086] <cim:busbarsection rdf:id="BusbarSection_1">

[0087] <cim:IdentifiedObject.mRID>BusbarSection_1< / cim:IdentifiedObject.mRID>

[0088] <cim:IdentifiedObject.name>10kV Bus< / cim:IdentifiedObject.name>

[0089] <cim:Equipment.EquipmentContainer rdf:resource="#VoltageLevel_1" / >

[0090] <!-- Other attributes... -->

[0091] < / cim:busbarsection>

[0092] <!-- Circuit breaker -->

[0093] <cim:breaker rdf:id="Breaker_1">

[0094] <cim:IdentifiedObject.mRID>Breaker_1< / cim:IdentifiedObject.mRID>

[0095] <cim:IdentifiedObject.name>CB1< / cim:IdentifiedObject.name>

[0096] <cim:Switch.open>false< / cim:Switch.open>

[0097] <cim:Switch.normalOpen>false< / cim:Switch.normalOpen>

[0098] <cim:Equipment.EquipmentContainer rdf:resource="#VoltageLevel_1" / >

[0099] <!-- Other attributes... -->

[0100] < / cim:breaker>

[0101] <!-- Transformer -->

[0102] <cim:powertransformer rdf:id="Transformer_1">

[0103] <cim:IdentifiedObject.mRID>Transformer_1< / cim:IdentifiedObject.mRID>

[0104] <cim:IdentifiedObject.name>TR1< / cim:IdentifiedObject.name>

[0105] <cim:PowerTransformer.vectorGroup>YDn11< / cim:PowerTransformer.vectorGroup>

[0106] <cim:PowerTransformer.ratedS>500< / cim:PowerTransformer.ratedS>

[0107] <cim:Equipment.EquipmentContainer rdf:resource="#VoltageLevel_1" / >

[0108] <!-- Other attributes... -->

[0109] < / cim:powertransformer>

[0110] <!-- Load -->

[0111] <cim:energyconsumer rdf:id="Load_1">

[0112] <cim:IdentifiedObject.mRID>Load_1< / cim:IdentifiedObject.mRID>

[0113] <cim:IdentifiedObject.name>Load1< / cim:IdentifiedObject.name>

[0114] <cim:EnergyConsumer.ratedS>100< / cim:EnergyConsumer.ratedS>

[0115] <cim:Equipment.EquipmentContainer rdf:resource="#VoltageLevel_1" / >

[0116] <!-- Other attributes... -->

[0117] < / cim:energyconsumer>

[0118] <!-- Connection point -->

[0119] <cim:connectivitynode rdf:id="ConnectivityNode_1">

[0120] <cim:IdentifiedObject.mRID>ConnectivityNode_1< / cim:IdentifiedObject.mRID>

[0121] <cim:IdentifiedObject.name>CN1< / cim:IdentifiedObject.name>

[0122] < / cim:connectivitynode>

[0123] <!-- Terminal -->

[0124] <cim:terminal rdf:id="Terminal_Bus_1">

[0125] <cim:IdentifiedObject.mRID>Terminal_Bus_1< / cim:IdentifiedObject.mRID>

[0126] <cim:Terminal.ConductingEquipment rdf:resource="#BusbarSection_1" / >

[0127] <cim:Terminal.ConnectivityNode rdf:resource="#ConnectivityNode_1" / >

[0128] < / cim:terminal>

[0129] <cim:terminal rdf:id="Terminal_CB_1">

[0130] <cim:IdentifiedObject.mRID>Terminal_CB_1< / cim:IdentifiedObject.mRID>

[0131] <cim:Terminal.ConductingEquipment rdf:resource="#Breaker_1" / >

[0132] <cim:Terminal.ConnectivityNode rdf:resource="#ConnectivityNode_1" / >

[0133] < / cim:terminal>

[0134] <!-- Other terminals... -->

[0135] Example of SVG snippet:

[0136] <g id="BusbarSection_1">

[0137] <polyline points="100,200 200,200" / >

[0138] < / g>

[0139] <g id="Breaker_1">

[0140] <use xlink:href="#breaker-symbol" x="300" y="200" / >

[0141] < / g>

[0142] <g id="Transformer_1">

[0143] <use xlink:href="#transformer-symbol" x="400" y="200" / >

[0144] < / g>

[0145] <g id="Load_1">

[0146] <use xlink:href="#load-symbol" x="500" y="200" / >

[0147] < / g>

[0148] Step 2: Device Mapping and ETAP Model Generation.

[0149] According to the predefined mapping rule table, convert the components and attributes in the CIM model into the corresponding components and parameters of the ETAP software. The following provides an example of a mapping rule table, specifically illustrating key rules such as BusbarSection being mapped to BUS in ETAP, Breaker being mapped to HVCB or LVCB according to the voltage level, and PowerTransformer being mapped to XFORM2W.

[0150] CIM Class CIM Attributes ETAP Component Type ETAP attributes Conversion rules / default values BusbarSection rdf:ID, name BUS ID, LocX_D2D, LocY_D2D The bus position is directly taken from the SVG coordinates. length Len_D2D Calculated from the polyline length of the SVG Breaker rdf:ID, name Based on voltage conversion to HVCB or LVDB ID, PdeStatus The status is set according to normal_open. breaking_capacity ACBreaking Direct mapping of breaking capacity PowerTransformer rdf:ID, ratedS XFORM2W ID, AnsiMVA The capacity value is directly mapped; if there is no load, a simulated load of a default proportion of the rated capacity is automatically added. vectorGroup PhaseShiftHL Vector group converted to phase difference EnergyConsumer rdf:ID, rated_s LUMPEDLOAD ID, MVA Load capacity is directly mapped, and the power factor is set to the default value. ACLineSegment linetype CABLE RPosValue, XPosValue Look up impedance parameters in the cable database length LengthValue Obtain directly from CIM properties ConnectivityNode rdf:ID BUS ID Dynamically create virtual bus nodes

[0151] Step 3: Topological Connection Reconstruction.

[0152] Based on the Terminal and ConnectivityNode relationships in CIM, reconstruct the electrical connection topology required by ETAP.

[0153] Traverse all ConnectivityNodes (connection points), find all the terminals connected to this connection point, obtain the devices corresponding to these terminals, and classify the devices they are connected to into two categories: busbar devices (BusbarSection, StationZB) and non-busbar devices; if a connection point is associated with a busbar device, converge all the connection relationships of this connection point to this busbar device, and assign a unique Pin (pin number) to each connection. Using the busbar device as the connection point, create a connection from the busbar to the device in ETAP; if a connection point is not associated with any busbar device, create a new ETAP busbar (BUS) with its average coordinates, and connect all the devices under this connection point to the new busbar. Add the new connection relationship to the CONNECTIONS in the ETAP XML.

[0154] Step 4: Generate ETAP XML File

[0155] Write the generated components and connections into the ETAP XML file. The following provides an example of an ETAP XML file.

[0156] Example of ETAP XML File

[0157] <PDE Flat="1"

[0158] <PROJECTINFO Project Information / >

[0159] <components compositeguid="xx">

[0160] <BUS LocX_D2D="20"

[0161] LocY_D2D="30"

[0162] ID="BUS_1"

[0163] NominalkV="10" / > ...

[0165] <XFORM2W LocX_D2D="20"

[0166] LocY_D2D="200"

[0167] ID="XFOR_1"

[0168] AnsiMVA="630.0"

[0169] AnsiPosXR="20"

[0170] AnsiPosZ="10"

[0171] AnsiZeroXoverR="20"

[0172] AnsiZeroZ="10"

[0173] PhaseShiftHL="-30"

[0174] PhaseShiftPS="30"

[0175] PrimkV="10"

[0176] SeckV="0.4"

[0177] FromBus="BUS_2"

[0178] ToBus="BUS_3" / >

[0179] <HVCB LocX_D2D="20"

[0180] LocY_D2D="50"

[0181] ID="HVCB_1"

[0182] ACBreaking="20000"

[0183] Normal="1250"

[0184] Rated="12"

[0185] PdeStatus="Open" / >

[0186] <LUMPEDLOAD LocX_D2D="20"

[0187] LocY_D2D="300"

[0188] ConstantZPercent="96"

[0189] MVA="504.0"

[0190] PF="90"

[0191] KV="0.4"

[0192] PhaseTypeString="3-Phase" / >

[0193] <connections>

[0194] <connections>

[0195] <CONNECT FromElement="BUS"

[0196] FromID="BUS_1"

[0197] FromPin="0"

[0198] ToElement="HVCB"

[0199] ToID="HVCB_1"

[0200] ToPin="0" / > ...

[0202] < / connections>

[0203]

[0204] Example 4: This example provides a computer device / equipment / system, including a memory, a processor, and a computer program stored in the memory, which, when executed by the processor, implements the steps of the method.

[0205] Example 5: This example provides a computer-readable storage medium storing a computer program / instructions thereon, which, when executed by a processor, implements the steps of the method.< / connections> < / components>

Claims

1. A method for automatically converting power system model data to ETAP software, characterized in that, include: The file input module receives CIM / E standard format XML files and corresponding SVG graphic files; The parsing module parses the XML file to construct a power system component object model based on the CIM standard, and simultaneously parses the SVG file to obtain the spatial coordinate information of each component; The conversion engine module calls the predefined mapping rules in the mapping rule library to map and match the elements in the CIM standard component objects with the elements in the ETAP software database. The mapping rules define the correspondence between CIM types and ETAP component types, and between CIM attributes and ETAP parameters. The topology processing engine module reconstructs the electrical connection topology required by ETAP based on the relationship between Terminal and ConnectivityNode in CIM / E, automatically converts ConnectivityNode into BUS element in ETAP, and generates the corresponding connection relationship; The file output module generates and outputs a data file that can be recognized by the ETAP software based on the matching results. The data file format is either the ETAP XML project file format or the data format imported in batches via API.

2. The method according to claim 1, characterized in that, If the file input module receives multiple sets of CIM / E files, it performs element coordinate calibration and merging processing on the multiple network topologies composed of multiple sets of CIM / E files to generate a unified ETAP model.

3. The method according to claim 2, characterized in that, The element coordinate calibration and merging process for the multiple network topologies thus formed includes: Assign a separate coordinate space offset to each individual CIM / E file to avoid overlapping component graphics during merging; For elements with the same rdf_ID in all files, merge their attributes. In the merged network topology, the coordinates of the elements are taken as the minimum or average of the coordinates of all coordinate points of that element in all files.

4. The method according to claim 1, characterized in that, The predefined mapping rules are a configurable mapping rule table; The mapping rules include: The ACLineSegment in the CIM model is mapped to the CABLE and XLINE models in ETAP based on the PSRType attribute; Map Substation, BusbarSection, and ConnectivityNode in the CIM model to the BUS model in ETAP; The Breaker, LoadBreakSwitch, and Disconnector in the CIM model are all converted into the switch model in ETAP according to their respective voltage levels. The Breaker of 10kV and above is converted into HVCB, and the Breaker of 10kV and below is converted into LVCB. The PowerTransformer and its contained PowerTransformerEnd in the CIM model are converted into the XFORM2W model in ETAP. Convert the EnergyConsumer model in the CIM model into the LUMPEDLOAD model in ETAP.

5. The method according to claim 4, characterized in that, The mapping rules also include rules for handling model differences, which include: When the line ACLineSegment in the CIM model provides a text description of linetype and length, the preset line impedance parameter calculation subsystem queries and calculates the resistance, reactance, zero-sequence resistance and zero-sequence reactance parameters required for the line ACLineSegment in ETAP. When there is no direct corresponding parameter in ETAP for a parameter in the CIM model, the default value or the value is derived and assigned using a formula based on electrical calculation principles. When there are components in the CIM model that are not supported by ETAP, a strategy of ignoring them or replacing them with the closest equivalent component is adopted.

6. The method according to claim 1, characterized in that, The topology processing engine module reconstructs the topology structure, including: Iterate through all ConnectivityNode objects and categorize the devices connected to them into bus devices and non-bus devices; If a connection point is associated with a bus device, all connections of that connection point are aggregated to the corresponding bus device, and a unique pin number is assigned to each connection. If a connection point is not associated with any bus device, a new ETAP bus is created with the average coordinates of that connection point, and all devices under that connection point are connected to the new ETAP bus.

7. An automatic conversion system for power system model data to ETAP software, characterized in that, include: The file input module is used to receive CIM / E XML and SVG files; The parsing module is used to parse XML and build a CIM object model, and also parse SVG files to obtain component coordinates; A mapping rule base is used to store the mapping relationship between CIM and ETAP; The topology processing engine module is used to reconstruct the connection topology based on the relationship between Terminal and ConnectivityNode, and to handle the coordinate space allocation when merging multiple files. The transformation engine module is used to perform mapping and generate ETAP data; The file output module is used to output the converted ETAP project file and the component rdf_ID mapping table; The output of the file input module is connected to the parsing module, the output of the parsing module is connected to the conversion engine module, the output of the conversion engine module is connected to the topology processing engine module, and the output of the topology processing engine module is connected to the file output module.

8. The system according to claim 7, characterized in that, The mapping rule database is pre-configured with a line impedance parameter calculation subsystem, including: A line impedance database for storing parameters of positive-sequence resistance, positive-sequence reactance, zero-sequence resistance, and zero-sequence reactance per unit length for common cable or conductor models at different cross-sectional areas; A model parsing submodule is used to extract cable model and cross-sectional area information from the cable model string provided in the CIM file using regular expressions; A parameter query submodule is used to query and return the corresponding impedance parameters from the line impedance database based on the extracted model and cross-sectional area, and then populate the ETAP cable model.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-6.

10. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1-6.

Images