Skip to main content

Panel lifecycle stages · why Operating is final

What Planning, Assembling, Deploying and Operating each mean, which stage corrections are possible during the build · and why Operating is final: an Operating panel holds runtime records and cannot be moved back.

Overview

A Hybird panel moves through four lifecycle stages, and the app shows where each panel stands. The stage is not just a label · it decides which steps the app offers and whether the panel is expected to report data. This article explains each stage, what can be corrected when a panel has been progressed further than the physical build actually is · and why Operating is different.

The four stages

  1. Planning · layout and labels prepared in Hybird OS. Devices are scanned to their planned slots in this stage.

  2. Assembling · breakers mounted, scanned and addressed with the app's per-breaker Assembly guide.

  3. Deploying · installed on site and connected.

  4. Operating · every device reporting · the panel is handed to the customer, and consumption, live measurements and remote switching are on.

The Assembling stage in practice · each breaker is scanned and addressed with the app's per-breaker Assembly guide. The full build flow, stage by stage, is covered in Building and commissioning a panel with the Hybird app.

Operating is final

Once a panel enters Operating, it cannot be moved back to an earlier stage · by anyone. From the moment a panel is Operating, its devices accumulate runtime records · data measurements written against the assets · and those records permanently anchor the panel in its final state. This is why the move to Operating is the one lifecycle step to treat as a deliberate hand-over, not a step to click through: only move a panel to Operating when every device is addressed, the self-check is clean, and the build is genuinely complete.

When a panel is progressed too early during the build

Before Operating, stages can be corrected. A panel pushed ahead of the physical build · for example into Assembling or Deploying before devices are scanned or addressed · shows these signs:

  • The build steps the installer expects · scanning, the Assembly guide · are not offered for the panel.

  • The self-check flags devices, or newly mounted breakers never received addresses.

Lifecycle stages cannot be wound backwards from the app · contact Hybird support and the panel is stepped back through the stages to the one matching reality, usually to Planning. Nothing physical is lost: once the state is corrected, the app offers the build flow again from the scanning step, and the installer works forward through the stages as normal.

If a panel reached Operating incorrectly

Because Operating is final, an incomplete or incorrectly built panel that has already entered Operating cannot be stepped back. Contact Hybird support to discuss the options for that installation · do not attempt to work around it in the app.

If devices do not report after a build completes, see New device not reporting after installation · troubleshooting guide.

Contact

Ask Maggie · the support chat, bottom-right in the installer portal and the help centre · or contact technical support at [email protected] · +45 3020 4900.

Related articles

Summary

Panels move Planning → Assembling → Deploying → Operating, and the stage decides what the app offers. Stages progressed too early during the build can be stepped back by Hybird support · usually to Planning, so the app guides the build again from scanning. Operating is the exception: once a panel is Operating it holds runtime records against its assets and its state is final · it cannot be moved back, so only complete the move to Operating when the build is genuinely done, and contact Hybird support if a panel reached Operating incorrectly.

Did this answer your question?