Forvaltning, drift og vedlikehold: asset management, operation and maintenance. The Norwegian collective term for everything that has to follow an installation through its life: what is there, how it is run and what has been done to it.
Definition
FDV comes from the construction industry and moved into the energy sector along with the installations. Some write FDVU, where the U is utvikling, development.
The three words are three different time horizons, and they are worth separating. Forvaltning is ownership: what we own, what it is worth, when it must be replaced. Drift is the everyday: that it is running and doing its job. Vedlikehold is the interventions: inspections, replacements, repairs.
FDV documentation is what has to be handed over when an installation is commissioned, and it is often the only thing that follows the componentA replaceable part inside a fixed asset. It has its own age, its own history and its own service life - independent of the asset it sits in. onward. Data sheets, installation instructions, serial numbers, warranty terms, maintenance intervals.
The Norwegian phrase «FDV-perm», the FDV binder, says something about where this came from. The documentation was delivered as a physical ring binder, and in many places it is still a binder, a folder of PDFs or a spreadsheet. Not because anyone decided so, but because nobody decided otherwise.
The problem is rarely that the documentation is missing. It is that it is not connected to anything.
The components exist in the project tool, in the spreadsheet, in the FDV binder and in the system that replaced the previous one. None of them know about the others. When someone asks where a particular breaker is, how old it is and when it was last looked at, the answer is spread across four places that do not talk to each other.
That connection is what RUNA is built for: one register of the physical assets, where the FDV information hangs on the component rather than in a binder beside it. LEIDAR uses the same register to answer whether the part exists somewhere else.
In practice
The problem is rarely that the documentation is missing. It is that it is not connected to anything.
The components exist in the project tool, in the spreadsheet, in the FDV binder and in the system that replaced the previous one. None of them know about the others. When someone asks where a particular breaker is, how old it is and when it was last looked at, the answer is spread across four places that do not talk to each other.
That connection is what RUNATvimenning's component register for electrical installations - providing structure and traceability for the components installations are built from. is built for: one register of the physical assets, where the FDV information hangs on the componentA replaceable part inside a fixed asset. It has its own age, its own history and its own service life - independent of the asset it sits in. rather than in a binder beside it. LEIDAR uses the same register to answer whether the part exists somewhere else.
