Product sheet

RUNA

Component register and operations platform for physical assets

Ready for the platform

The situation this answers

The components live in the project tool, in the spreadsheet, in the O&M binder and in the system that replaced the last one. None of them know about the others. When someone asks where a switch is today, and where it was last year, someone has to go looking.

Fits best when

You build and operate the same facility, but in two different systems.
You need to answer where a component is now, where it was before, and when it moved.
You are subject to traceable user access requirements, under the Norwegian power contingency regulations, or NIS2 where it applies.
A component should be called the same thing by you, by your supplier and by the regulator.
You already have a system holding the network data, but nothing holding the components beneath it.

What you get

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

RUNA stands on its own and requires no other modules.

What we do not cover: RUNA does not operate the facility: no SCADA, no network calculation, no field repairs.

RUNA · Product sheet

How it works

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 functions in detail

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.
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.
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.

The status, explained

Ready for the platform: Verified against simulated market interfaces. After the move into the platform, you can test it yourselves.
Demo at our end: We can demonstrate it, not verified against the market.
In production: In production with a customer today.

Works together with

FRAMSYN: Maintenance orders based on actual condition, not age - combining data from SEFTA, SPIRA and RUNA.; Demo at our end
LEIDANG: Closed marketplace for preparedness resources; Demo at our end
SPIRA: One consolidated register for metering points, installations and assets - the source of truth the rest of the chain builds on.; Ready for the platform
SAMTYGD: A shared integration layer to the modules, the surrounding systems and market hubs such as Elhub.; In production
STUBB: Mock services that simulate external systems with realistic behaviour and real data formats.; Ready for the platform

Terms used here tvimenning.no/en/ordbok

RDS: Reference designation system per ISO/IEC 81346. Gives every component in a facility one unambiguous designation that holds for its whole life.
GlobalID: A unique id that follows a component for its entire lifetime, across every system it appears in. The technical term for it is UUID.
NIS2: EU directive on network and information security - imposes strict security requirements on critical infrastructure.
Fixed asset: Physical equipment owned and used over time - transformer, cable, breaker. It has both a technical and an accounting side, and the two rarely agree.
NOARK: The Norwegian standard for records management in the public sector - requirements for journaling, versioning and disposal.
REN: Norwegian Organisation for Rational Electric Network Operations - industry organisation for technical standards in electricity networks.