Implementation of 'voltage level'

[ColinHDev]

Summary of the discussion

As discussed in #1960, an implementation of different kinds of voltage levels is required.

Type of change (CHANGELOG.md)

Add

• voltage level as subclass of quantity value that ('prescribed by' some 'operational voltage level') and ('has unit' some 'electric potential difference unit')
  • definition: A voltage level is a quantity value reflecting the desired voltage value that an electricity grid or electricity grid component is operating on.
• low voltage level as individual of voltage level
  • definition: A low voltage level is a voltage level in the german voltage classification system describing an electric potential difference of 400 volts.
  • object property assertion: 'part of' 'german voltage classification system'
  • data property assertion: 'has number' 400
• medium voltage level as individual of voltage level and 'has number' some xsd:decimal[>= 10000 , <= 30000]
  • definition: A medium voltage level is a voltage level in the german voltage classification system describing an electric potential difference between 10,000 and 30,000 volts.
  • object property assertion: 'part of' 'german voltage classification system'
• high voltage level as individual of voltage level
  • definition: A high voltage level is a voltage level in the german voltage classification system describing an electric potential difference of 110,000 volts.
  • object property assertion: 'part of' 'german voltage classification system'
  • data property assertion: 'has number' 110000
• extra high voltage level as individual of voltage level and 'has number' some xsd:decimal[>= 220000 , <= 380000]
  • definition: A extra high voltage level is a voltage level in the german voltage classification system describing an electric potential difference between 220,000 and 380,000 volts.
  • object property assertion: 'part of' 'german voltage classification system'

---

• voltage classification system as subclass of information content entity that 'has part' min 1 'voltage level'
  • definition: A voltage classification system is an information content entity that categorizes the voltage, components of an electricity grid usually operate on, into different levels.
• german voltage classification system as individual of voltage classification system
  • definition: The german voltage classification system is a voltage classification system currently being used in the electricity grid of Germany.

---

• operational voltage level as subclass of information content entity
  • definition: An operational voltage level is an information content entity that prescribes the intended operating voltage of some electrical artifact.
• low operational voltage level as subclass of operational voltage level that 'prescribes' value 'low voltage level'
  • definition: A low operational voltage level is an operational voltage level usually for the local distribution of electricity. Electricity at this voltage level can be converted to a medium operational voltage level. The usual producers feeding electricity at this voltage level into the grid are smaller wind farms and solar installations. Households are the usual consumers receiving electricity at this operational voltage level.
• medium operational voltage level as subclass of operational voltage level that 'prescribes' value 'medium voltage level'
  • definition: A medium operational voltage level is an operational voltage level usually for the regional distribution of electricity. Electricity at this voltage level can be converted to a high or low operational voltage level. The usual producers feeding electricity at this voltage level into the grid are wind and solar farms. Industries can be consumers receiving electricity at this operational voltage level.
• high operational voltage level as subclass of operational voltage level that 'prescribes' value 'high voltage level'
  • definition: A high operational voltage level is an operational voltage level usually for the interregional distribution of electricity. Electricity at this voltage level can be converted to an extra high or medium operational voltage level. The usual producers feeding electricity at this voltage level into the grid are natural gas power plants and hydropower. Large-scale industries can be consumers receiving electricity at this operational voltage level.
• extra high operational voltage level as subclass of operational voltage level that 'prescribes' value 'extra high voltage level'
  • definition: An extra high operational voltage level is an operational voltage level usually for the transmission of electricity. This is the usual voltage level electricity is imported and exported. Electricity at this voltage level can be converted to a high operational voltage level. The usual producers feeding electricity at this voltage level into the grid are coal and nuclear power plants, as well as offshore wind farms and hydropower.

Workflow checklist

Automation

Closes #

PR-Assignee

• 🐙 Follow the Pull Request Workflow
• 📝 Update the CHANGELOG.md
• 📙 Add #'s to term tracker annotation

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[ColinHDev]

I implemented the structure proposed in #1960 (comment) except:

• There is no prescribed by property, so I've used is about
• There is no has continuant part property, so I've used has part
• 'grid component' 'bearer of' some 'operational voltage level' - Since it is also in the scope of this issue to remove grid component and replace it with a grid component role, I haven't included this axiom yet. Also, there is no bearer of property (or something similar) that matches based on the definition

[stap-m]

@ColinHDev in the last oeo-dev meeting, we decided on the import of prescribes etc. from CCO. I wasn't aware that it also affects this PR and only commented here, sorry: #1979 (comment)

[areleu]

Also, there is no bearer of property (or something similar) that matches based on the definition

In this case 'has bearer' is equivalent to 'depends on'. Since we are talking about a quality, as far as I remember, we could use 'quality of'

Nvm is the inverse 'has characteristic' and the respective quality relation

[stap-m]

• grid component' 'bearer of' some 'operational voltage level' - Since it is also in the scope of this issue to remove grid component and replace it with a grid component role, I haven't included this axiom yet. Also, there is no bearer of property (or something similar) that matches based on the definition

Also, there is no bearer of property (or something similar) that matches based on the definition

In this case 'has bearer' is equivalent to 'depends on'. Since we are talking about a quality, as far as I remember, we could use 'quality of'

Nvm is the inverse 'has characteristic' and the respective quality relation

Anyway, it should be 'operational voltage level' 'characteristic of' some 'grid component' (and not the other way round).
Please also see my comment in PR #2054 on making grid component an equivalent class and additionally introduce grid component role.

[ColinHDev]

Anyway, it should be 'operational voltage level' 'characteristic of' some 'grid component' (and not the other way round). Please also see my comment in PR #2054 on making grid component an equivalent class and additionally introduce grid component role.

But isn't every grid component designed to operate at a certain operational voltage level? On the other hand, when I talk about a (maybe even hypothetical) voltage level like extra, extra high voltage level, it doesn't need an existing grid component that operates on it for it to be an operational voltage level?
I hope my comment made any sense - I was just wondering, why the first proposed way of 'grid component' 'bearer of' some 'operational voltage level' isn't correct

[stap-m]

The classes still are missing definitions.

But isn't every grid component designed to operate at a certain operational voltage level? On the other hand, when I talk about a (maybe even hypothetical) voltage level like extra, extra high voltage level, it doesn't need an existing grid component that operates on it for it to be an operational voltage level? I hope my comment made any sense - I was just wondering, why the first proposed way of 'grid component' 'bearer of' some 'operational voltage level' isn't correct

BTW: charactersistic of is only allowed for SDC, see its definition. operational voltage level is a GDC, though.

[stap-m]

But isn't every grid component designed to operate at a certain operational voltage level? On the other hand, when I talk about a (maybe even hypothetical) voltage level like extra, extra high voltage level, it doesn't need an existing grid component that operates on it for it to be an operational voltage level? I hope my comment made any sense - I was just wondering, why the first proposed way of 'grid component' 'bearer of' some 'operational voltage level' isn't correct

The thing is that the sdc, e.g. a quality, existentially depends on the bearer, therefore it should possess the axiom. The bearer, on the other hand, could theoretically exist without a certain quality. However, technically has characteristic and characteristic of are inverse of each other.

[ColinHDev]

BTW: charactersistic of is only allowed for SDC, see its definition. operational voltage level is a GDC, though.

Oh, that's true. So the discussion should be about 'grid component' 'has information content entity' some 'operational voltage level' or 'operational voltage level' 'is about' some 'grid component'

I can implement it at the operational voltage level. I just still think it should be based on the grid component with 'grid component' 'has information content entity' some 'operational voltage level' since for something to be considered an operational voltage level, it doesn't require a physical implementation of said voltage level in a grid component.

[ColinHDev]

Also, the relation should be with electricity grid component and not grid component. A gas grid component has nothing to do with voltage levels.

[ColinHDev]

The classes still are missing definitions.

I just wanted to make sure the current structure was okay before trying to come up with definitions and possibly discarding them in the end. Should be all there now!

[stap-m]

• voltage classification system is currently just a subclass of information content entity but I can't really find a better fitting subclass.

ok, I agree.

[stap-m]

• operational voltage level is currently a subclass of objective specification (definition: A directive information entity that describes an intended process endpoint. When part of a plan specification the concretization is realized in a planned process in which the bearer tries to effect the world so that the process endpoint is achieved.)

  • But what is the intended process endpoint of an operational voltage level?

The current def proposal is An operational voltage level is an information content entity that prescribes the intended operating voltage of some electrical artifact. If we interpret the micro-process as bringing the voltage back to the intended voltage level from any departure of that level, I could go with objective specification. We should add an rdfs:comment Annotation about that.

[ColinHDev]

The current def proposal is An operational voltage level is an information content entity that prescribes the intended operating voltage of some electrical artifact. If we interpret the micro-process as bringing the voltage back to the intended voltage level from any departure of that level, I could go with objective specification. We should add an rdfs:comment Annotation about that.

I went with the following:

An objective specification always describes an intended process endpoint. In the case of an operational voltage level, this endpoint concerns the micro-process of returning the voltage within an electrical artifact to its designated level after any deviation. Thus, the process endpoint is characterized by the restoration of the target voltage level in the given electrical artifact.

[stap-m]

From the todays oeo-dev meeting no. 103:

• voltage classification system:
  • adjust definition "A voltage classification system is an information content entity that categorizes the voltages that components of an electricity grid power system usually operate on, into different levels."
  • add rdfs:comment: "Voltage classifications are crucial because they determine system requirements, equipment standards, and safety protocols. These classifications serve as a framework that industries—ranging from utility networks to manufacturers—use to design systems and equipment in accordance with predetermined voltage levels. By standardizing voltage levels, it ensures that the systems operate safely, efficiently, and consistently across different applications and regions. (source: https://missioncriticalengineers.com/voltage-classifications/ accessed 2025-07-04)"
• voltage level: rename to electricity grid voltage level
  • "A electricity grid voltage level is a quantity value reflecting the normative voltage value that an electricity grid is operating on."
• add axiom: electricity grid part of some power system
• operational voltage level:
  • reuse existing class from CHIO https://dlr-ve-esy.github.io/charging-ontology/CHIO_00000091.html
  • we need the CCO class performance specification @ColinHDev
  • I recommend opening a new issue for operational voltage level

[ColinHDev]

So, I've removed operational voltage level. Axioms that have to be implemented in #2108:

• 'electricity grid component' 'is subject of' some 'operational voltage level'
• 'electricity grid voltage level' 'prescribed by' some 'operational voltage level'
• 'low operational voltage level' prescribes value 'low electricity grid voltage level'
• 'medium operational voltage level' prescribes value 'medium electricity grid voltage level'
• 'high operational voltage level' prescribes value 'high electricity grid voltage level'
• 'extra high operational voltage level' prescribes value 'extra high electricity grid voltage level'

[stap-m]

The rest looks fine!