Product

RUNA

Ready for the platformComponent register and operations platform for physical assets

Structure and control over the components that installations are built from

Request a demo →View services

Used by:

NE DSOs KP Power producer FV District heating H₂ Hydrogen

What is RUNA?

RUNA covers the full lifecycle of physical assets in one system: design, construction, commissioning and ongoing maintenance. Construction projects follow a phased lifecycle with FAT and SAT checklists built on the REN standards, and with external reporting to NVE and Statnett. The register stores every installation interval with a timestamp, so it can answer where a component is now, where it was before, and when each assignment began and ended. A digital twin of the grid is no truer than the component data beneath it. The simulation knows the transformer it was told is there, not the one actually standing there, with its vintage and its history. If the underlying record lives in spreadsheets, the model inherits the spreadsheet. RUNA does not solve the simulation, but the layer below it: which component, where, and since when. That is the difference between modelling the grid and modelling an assumed grid.

The name

runaOld NorseBefore systems and spreadsheets, there was runa - knowledge of every tool's type, condition and history, held in the memory of whoever used it. A broken haft did not mean the end of the axe, only a new one fitted to the same head. RUNA carries the same idea into the component register: meters, transformers and repeaters known and described, not assumed.

Before systems, before forms and before databases, there was runa. Not as figures in a list, but as a mark of knowing: what had value was known. What was in use was remembered. What broke was made whole again. In a Norse community, oversight was not something you administered - it was lived.

Fishing - when the sea demanded order. Nets, traps, lines, hooks and floats each had their place, their use, their condition. When a net tore, you knew which rope it was tied with, who had woven it, and how long it had been in use. You worked with what was known: rope was mended, hooks replaced, floats swapped for better stock. That is how a living record came about - not of the catch, but of the gear. That was a runa.

Farming - when tools had to last. The tools of the field were few but decisive: ploughshares, scythe blades, shafts, fittings. Nothing was discarded without reason. When a scythe blade cracked, you knew how old the steel was, whether it was forged locally or traded for, and whether it could take one more sharpening. Shortcomings weren't ignored - they were noted in memory, and when the time came you went to the smith with the right knowledge in hand. Not 'make a new one', but 'make this one, better'.

Forestry - when repair mattered as much as work. In the forest the axe was everything, but so were the shaft, the wedge and the binding that held it together. A broken shaft didn't mean the end of the axe - it meant a new shaft, a new binding, the same head. The smith, the woodworker and the farmer shared a common understanding: tools live in parts, and keeping track of the parts wasn't bureaucracy. It was survival.

But memory dies with the person who holds it. So what was meant to last was cut in stone. The Rök stone carries the longest runic inscription we know, raised by Varin in memory of his son. The Rosetta Stone carried the same decree in three scripts, because that was how proclamations were made. Neither was intended as a key to anything. They became one long after those who carved them were gone. Without them we would not have understood the rest.

RUNA's component register carries this idea forward. What's owned here isn't the installation, the connections or the grid structure - it's the component: the meter, with its type, vintage and attributes; the transformer, with its use and its history; the modem, the concentrator and the repeater, as parts of a larger whole. RUNA is where these are known, described and chosen. When the inspection authority asks for spot checks, the answer isn't a guess - it's knowledge. When something must be replaced, it doesn't happen at random; it happens with knowledge of what's there now, and what should be there tomorrow.

What it looks like

RUNA in use

The history tab for one AMS meter in RUNA: the change log with created from import, meter replaced, status change and firmware updated over OTA, each with who and when. Beside it: external systems, where SPIRA is listed as the linked metering point with the note that SPIRA owns the relation to the metering point. The left menu shows components, component masters, field library, stock and operations. — Screenshot from a demo environment. The figures are realistic demo data, not from a customer installation.

Key features

From design to maintenance in one system

Construction projects follow a phased lifecycle from design through construction and commissioning to maintenance, with FAT and SAT checklists built on the REN standards and external reporting to NVE and Statnett. The handover from project to operations is not an export, but the same data set changing phase.

Component catalogue

The catalogue describes the component types a grid is built from: the meter with its type, vintage and properties, the transformer with its application and history, and the modem, concentrator and repeater. Specifications live on the type, not on each unit, so a new installation inherits the description.

Normalised structure

A standardised data model ensuring consistency across installations and projects, so a transformer means the same thing in two projects built five years apart, and reports can be assembled without manual translation.

SPIRA integration

Tight integration with SPIRA to link components to metering points and installations. RUNA answers what a component is; SPIRA answers where it sits and who is connected to it. Every installation interval is stored with a timestamp, so the question "which meter was here last year?" has an answer rather than an estimate.

Reusability

Define a component once and reuse it across installations, instead of retyping the same specification for every project. The GlobalID follows the individual unit through its whole lifetime and across the systems it appears in, so its history stays intact even when the component is moved.

Document management on NOARK principles

A single document library across locations, assets and projects, with templates, keywords and versioning. Disposal leaves a tombstone, so an audit can see that a document existed and when it was disposed of. The solution follows the NOARK principles; it has not been tested against a Noark 5 core.

Audit log and event log

A read-only audit log with archiving, and an event log showing who has been logged in and when. Section 7-4 of the Norwegian power-preparedness regulation requires control of user access; the log is designed to answer that question without manual reconstruction.

Timeline of events

Design, commissioning and maintenance work appear as coloured markers on a timeline. Dates can be narrowed and the timeline zoomed, and clicking a marker gives the details. It is the one view that shows a component’s full history without anyone having to search.

Check-out, so two people do not edit the same document

A document can be reserved on check-out. Only the person who reserved it, and an administrator, can release it. Everyone else sees who holds it and when it was locked, so they know who to talk to instead of guessing.

Maintenance even without a maintenance system

RUNA integrates with the maintenance system you have. If you do not have one, maintenance exists in a simpler form inside RUNA itself, so the register is not left waiting for something else to be procured first.

RDS designation and GlobalID

Each component gets a functional designation per RDS (ISO/IEC 81346) and a GlobalID, a UUID that follows the component for its whole lifetime and across the systems it appears in. The designation is what lets two systems talk about the same component without first agreeing on a name.

Grid infrastructure and assets

Not only the components sitting on an end-customer metering point: substations, transformer stations and power stations are registered as assets with the larger REN sheet structures they are actually built to. That is the part of the grid that otherwise ends up in spreadsheets because it does not fit a metering-point register.

Results you can expect

✓Project and operations on the same data set - no handover
✓Documented user access without manual reconstruction
✓Reduced time spent on component registration
✓Consistent data quality across projects
✓Easy reuse of standard components
✓Tight integration with SPIRA

See use cases →

Get started quickly

RUNA is built for rapid implementation. Typical setup takes weeks, not months.

Dedicated implementation support
Integration with existing systems
Training for your team
Ongoing support after go-live

Who uses RUNA?

Installers

Standardise component registration and eliminate manual errors by reusing approved components.

Grid companies

Get visibility into which components are used in the grid and ensure technical consistency.

Project managers

Plan installations faster with access to a standardised component catalogue.

Ready to see RUNA in action?

Book a demo and we will show you how RUNA can solve your specific challenges.

Request a demo →View all products