Product sheet

FRAMSYN

RCM maintenance orders

Demo at our end

The situation this answers

A component is replaced because it reached a date, not because it is worn. Some are scrapped while still sound, others fail between two inspections, because the fixed cycle never saw the load they carried.

Fits best when

You replace parts by age, because age is the only figure you can rely on.
Meter data and service history both exist, but nobody puts them together.
You have an RCM analysis in a spreadsheet nobody has updated since it was made.
You want to move to condition-based maintenance, but do not know where to start.
Your metering values live in another system that is staying, not being replaced.

What you get

Maintenance when needed, not by calendar
Fewer unexpected failures between inspections
Components that are still sound stay in place, not replaced
Built on data you already have
Can run on an MDM other than ours - configuration, not a rewrite

FRAMSYN stands on its own and requires no other modules.

What we do not cover: FRAMSYN does not do the work: no crew scheduling, no inventory, no execution in the field.

FRAMSYN · Product sheet

How it works

FRAMSYN rests on two equally important sources. RUNA owns the components, the history and the maintenance. SEFTA owns the metering values and test results that make it possible to say anything about condition at all - without them you are left with age, which is precisely what FRAMSYN sets out to replace. The RUNA integration runs both ways: RUNA supplies the component history, FRAMSYN sends predictive maintenance tasks back with a component reference, the predicted problem and a suggested time window, and RUNA enriches the task with context FRAMSYN does not hold. The result flows back, so the model sharpens over time.

The functions in detail

Condition-based maintenance: Maintenance orders are generated when a component actually needs it, not on a fixed schedule.
Combined data foundation: Metering data from SEFTA and asset data from SPIRA/RUNA are combined into a single decision basis.
Not tied to RUNA and SEFTA: FRAMSYN does not assume you buy the rest. Both RUNA and SEFTA can be replaced by systems with equivalent functionality - in the Nordics, Avance MDM and Quant are the closest. It is not prepared out of the box: it takes configuration and a bespoke integration, done by us or by you. RDS is not a requirement, but without it the assessment is less specific.

The status, explained

Demo at our end: We can show it here. Not yet verified against market interfaces, so your input carries weight now.
Ready for the platform: Verified against simulated market interfaces, not in operation.

Works together with

SEFTA: Validation, estimation, and editing with versioned time series, traceability, and export-ready data.; Ready for the platform
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
RUNA: One register for the physical components - the whole lifetime, with traceable history and standardised designation.; Ready for the platform
LEIDANG: Closed marketplace for preparedness resources; Demo at our end

Terms used here tvimenning.no/en/ordbok

Component: A 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.
Metering data: Data from electricity meters - the foundation for billing, balance settlement and market processes in the power market.
RCM: Methodology for determining maintenance needs from a component's actual condition and failure mode, not a fixed calendar. The basis for FRAMSYN's maintenance orders.
Condition-based maintenance: A maintenance tactic: continuously monitor a component's condition and intervene when the data shows a deviation - not on a fixed calendar. What FRAMSYN does in practice.
RDS: Reference designation system per ISO/IEC 81346. Gives every component in a facility one unambiguous designation that holds for its whole life.