Our products

Master data register

SPIRA

Ready for the platform

Master Data Hub - single source of truth for energy assets

Master data accuracy - Elhub messaging requirements

Errors in the metering pointThe fundamental unit in Elhub - the unique point in the electricity network where energy is measured and settled, identified by an 18-digit GSRN number. and installation register are one of the most common - and least visible - causes of billing errors. When addresses, metering point IDs or 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. data disagree across systems, the fault only surfaces far downstream, often as a customer complaint about an incorrect invoice. SPIRAOne consolidated register for metering points, installations and assets - the source of truth the rest of the chain builds on. tackles it at the root: one consolidated register for metering points, installations and assetsPhysical equipment owned and used over time - transformer, cable, breaker. It has both a technical and an accounting side, and the two rarely agree. that HESHead-End System - central system for collecting and managing data from smart meters in AMI networks., MDMMeter Data Management - system for collection, storage, quality assurance and distribution of metering data from the electricity grid. and settlementTurning metering data into money. Consumption and production per metering point become what each party owes or is owed. can rely on.

Component register

RUNA

Ready for the platform

Component register and operations platform for physical assets

Traceability and oversight - RDS (ISO/IEC 81346) and NIS2 audit logging

Most grid companies keep their component data spread across spreadsheets, GISGeographic Information System - system for collecting, storing and analyzing location-based data - used in network mapping and planning. and people's heads. RUNAOne register for the physical components - the whole lifetime, with traceable history and standardised designation. gathers it in one place, across the whole lifetime from goods receipt to retirement. Each component gets a functional designation per the RDSReference designation system per ISO/IEC 81346. Gives every component in a facility one unambiguous designation that holds for its whole life. standard (ISO/IEC 81346The standard giving every part of a plant an unambiguous designation by function, location and product. The basis RDS builds on.) and an identifier that follows it across systems - so the register can answer where a component is now, where it was before, and when it moved. That history is what makes auditing and condition assessment possible after the fact.

Maintenance planning

FRAMSYN

Demo at our end

RCM maintenance orders

Condition-based maintenance - RCM methodology

Age-based maintenance wastes in two directions at once: components are scrapped while still working well, and others fail unexpectedly because the fixed cycle never caught the real deterioration. FRAMSYNMaintenance orders based on actual condition, not age - combining data from SEFTA, SPIRA and RUNA. replaces the calendar with data on how the component is actually doing - metering data from SEFTATvimenning’s VEE engine: validates, estimates and edits metering series with versioned time series and a full audit trail, before data goes to Elhub. shows what it has been subjected to, while SPIRATvimenning's metering point and asset register - your single source of truth for master data, with a built-in validation engine and Elhub integration. and RUNATvimenning's component register for electrical installations - providing structure and traceability for the components installations are built from. hold year of manufacture, installation date and service history. It is the combination that lets the system speak to condition rather than age. FRAMSYNTvimenning’s tool for condition-based maintenance: raises work orders from how the component is actually doing, not from how old it is. does not, however, assume you use our registers: it can be connected to the systems you already have, through an adapter. The difference is how much works from day one - with SEFTA, SPIRA and RUNA the support is complete out of the box, while a third-party system requires its own configuration and integration, and gives a more limited first level.

Integration layer

SAMTYGD

In production

Shared integration layer

System integration - Elhub gateway and market hubs

A shared integration layer between the modules, the surrounding systems and market hubs such as Elhub. One place for messages, metering data and formats.

EDI server

HANDSAL

Demo at our end

EDI server for B2B

Message exchange - EDIEL/ECP/Peppol/EDIFACT

Power suppliers, grid companies and balance responsible parties exchange structured messages directly between themselves every day - invoices, delivery plans, product data - without going through a central market hub. That bilateralMessages travel directly between two parties, without passing through a shared hub. The opposite of the centralised model Elhub is built on. Also called point-to-point. traffic is usually handled either by an expensive, closed message broker, or by home-built solutions with no monitoring, quarantine or alerting when something fails to arrive. HANDSALEDI server that receives, translates, routes and confirms messages between companies and marketplaces. is a self-hosted EDIFACTElectronic Data Interchange For Administration, Commerce and Transport - UN standard for electronic data exchange. gateway that gives this a dependable foundation - without the traffic having to pass through a third party.