Understand structural changes such as combining or replacing installations before applying them.
Combining, replacing, hiding, deleting, and unclaiming assets solve different problems. Do not use them interchangeably.
| Action | What it changes | Typical use |
|---|---|---|
| Hide / deactivate | Keeps the asset and its history but removes it from normal active views. | Temporarily or permanently stop operational follow-up without deleting data. |
| Hide from monitored table | Keeps the asset active but removes it from the main monitored overview. | Exclude an auxiliary or non-operational asset from portfolio supervision. |
| Unclaim controller | Detaches company management relations from a controller hierarchy. | Transfer or remove a controller from the current company. |
| Delete custom asset | Removes monitor relations for a manually created custom-… asset. | Remove a virtual object that should no longer exist. |
| Combine / replace | Changes how existing records or histories are represented. | Correct a structural migration with support guidance. |
Use support for structural migrations
Combining or replacing installations can affect hierarchy, historical interpretation, alarms, reports, and access. Record the intended source, destination, and effective date before applying the change.