Fuses

Why are fuses not found in the model?

•All information related to fuses is managed within the corresponding switches and distribution boards. For this reason, no standalone fuses are captured. This approach significantly simplifies the model for the user. Various alternatives arise in the data capture process regarding how switches and fuses can be recorded. These alternatives are described in more detail in the data capture guidelines.

Decommissioned and Dismantled Lines

How should decommissioned objects be handled?

•Decommissioned lines should be separated from the operational lines with minimal shortening so that these assets are no longer interconnected. This corresponds to the actual situation in the field.

•Additionally, the decommissioned assets will have the attribute "DetailLifeCycleStatus" set to a type of decommissioning. This will also recalculate the network attribute NET_MainLifeCycleStatus and set it to the "Decommissioned" phase, so that network tracking no longer considers these assets.

If assets are dismantled, this can also be documented using the value "Dismantling" in the attribute "DetailLifeCycleStatus."

By retaining decommissioned or dismantled lines in the dataset, they remain available for reports and statistics for accounting purposes, or for inquiries about the network and assets over time (historical data). The object identification remains intact, ensuring that communication with third-party systems continues to function.

To control the visibility of decommissioned or dismantled assets on the map without increasing the complexity of the map display, a "Layer Filter" functionality is planned for the medium term.

A function for outsourcing and archiving decommissioned/dismantled objects into a simple "Archive Feature Class" is not currently planned as part of product development. The development of such functionality may be considered within the scope of customer projects.