Skip to main content
Energy

A project is run from the first work order to the last meter reading

We implement management systems for energy contractors, operators and asset owners: work orders with proof of execution, preventive maintenance schedules, an asset and warranty register, progress claims, and readings recorded so they can be compared — sized to your segment: an installation contractor needs project and claim control, an operator needs documented maintenance and faults with causes, a renewable asset owner needs a warranty and performance record, and an efficiency provider needs a baseline and documented measurement. What they share: what is not recorded cannot be proven — not in a claim, not at audit, not when comparing one year’s performance with another.

Request an operations assessmentSee the segments
  • Four segments, four scopes
  • Proof of execution before talk of speed
  • A reading recorded so it can be compared
  • Not an EPC contractor or an approving body
  • No saving, generation or uptime promises

Direct answers

The questions asked first

How do you treat a contractor, an operator, an asset owner and an efficiency provider differently?

By fit rather than price: a contractor suffers because a project is known from spending rather than from progress, so it needs documented items and claims with on-site proof of execution, and running an asset-management system before that is waste. An operator suffers because maintenance is reactive, so it needs a preventive schedule, a fault log with causes, and spare parts tied to the asset. A renewable asset owner suffers because warranty and performance are scattered between vendor files and invoices, so it needs an asset record linking the panel or inverter to its warranty and to production readings. An efficiency provider suffers because savings are claimed without a baseline, so it needs measurement before and after on a published method with written reference conditions. In the assessment we tell you which of these you are.

Do you guarantee a saving percentage or a generation figure?

No. We guarantee no saving percentage, no generation figure, no uptime and no efficiency improvement, because those are set by the tariff structure, the weather, the equipment used, consumption behaviour and maintenance — none of which an administrative system controls. What we do commit to is that what happens is measured: a documented baseline before implementation, readings recorded with their reference conditions, a published calculation method written into the contract, and a result presented as it is even when it falls short of expectation. A guaranteed figure in this sector is a promise nobody making it actually controls.

Do you carry out installation works and engineering design?

No. We are a systems company: we do not undertake EPC works or electrical installations, we supply and install and calibrate no panels, inverters, meters or sensors, we issue and stamp no certified engineering design, and we do not handle regulatory or utility approval procedures. What we do is build the system that runs the work: work orders with proof of execution, the maintenance schedule, the asset and warranty register, progress claims, and the reading and measurement record. Design, installation and approvals remain the responsibility of the licensed party.

What usually stops energy systems projects?

Three things we see repeatedly, none of them technical: no asset register — what exists, where it is and under which warranty is unknown, so everything rests on memory; items and claims not tied to execution — collection is delayed and a dispute arises on every claim; and the absence of a baseline — consumption is said to have fallen with no documented prior measurement, so every saving claim becomes challengeable. That is why we start with the asset register, the items and the baseline, before any promise of a report or an indicator.

Context

Why this sector is different in the Kingdom

Four operational realities impose requirements on the system that do not appear in other markets — with no market figures and no targets.

Energy sits within Vision 2030 priorities

Energy is one of the strategic sectors in the Kingdom’s Vision 2030, with a general direction towards consumption efficiency and diversified production — context that explains the demand for documentation and measurement, while we publish no programme numbers or targets, because they are not ours and we cannot verify them.

Context, not a figure

A tariff that demands calculation, not impression

The effect of any change in consumption cannot be read from a single bill; a decision needs a baseline, regular readings and comparison under the same conditions — which the system builds rather than leaving to impression.

A baseline before a claim

Long-life assets need a record, not memory

A panel, inverter or transformer runs for years with a warranty, maintenance cycles and readings; without a record tying them together, the warranty right is lost and performance is hard to evidence.

A documented asset

Distributed field teams

Installation and maintenance teams work across many sites on a changing connection, so the system needs offline entry, documentation with photos and location, and synchronisation that loses nothing.

Offline, then synced

We state the context because it explains the requirements — not to sell with it: we publish no market size, no growth rate, no programme target and no expected saving percentage, because such a figure is either something we cannot verify or something that does not apply to your operation.

Segments

Four segments — and four different scopes

The same sector does not mean the same project. Read your segment first, then what fits you — and, plainly, what does not.

Installation and execution contractor

Several projects · field teams · recurring items and progress claims

What it suffers from
A project is known from spending rather than progress: items live in a spreadsheet, execution in photos on phones, and the claim is built on an estimate so collection is delayed and a dispute arises on every submission.
What fits it
Project items tied to actual execution, photo and location proof per item, a claim built on documented execution, and project cost readable while it runs rather than after closing.

What does not fit you: Running asset management and preventive maintenance before items and claims are under control, a complex inventory system for a contractor buying materials per project, and dashboards before documented proof of execution exists.

Operator and maintenance (O&M)

Several assets or sites · maintenance teams · spare parts and faults

What it suffers from
Maintenance is reactive: a fault is reported by phone, a repair happens with no record showing recurrence, and spare parts are bought when they run out so no asset’s consumption is known.
What fits it
A preventive schedule per asset with published cycles, work orders with proof of execution, a fault log with cause and duration, spare parts tied to the asset, and fault-recurrence reporting per site.

What does not fit you: Starting with executive dashboards before a documented fault log exists, connecting sensors before assets are registered by number, and managing stock without a link to maintenance so parts go missing with no cause.

Renewable asset owner

Plants or distributed sites · vendor warranties · production readings

What it suffers from
Warranty and performance are scattered: which panel or inverter came from which vendor under which warranty is unknown, readings sit in a separate file without reference conditions, and evidencing performance or claiming warranty is hard.
What fits it
An asset record linking each component to its vendor, warranty and installation date; a reading record with its reference conditions; period-over-period performance comparison on a published basis; and alerts before a warranty expires or maintenance falls due.

What does not fit you: Relying on theoretical calculation instead of recorded readings, managing warranties in a file separate from assets, and building performance reports without reference conditions so the figure becomes challengeable.

Energy efficiency and audit services

Site audits · recommendations · post-implementation measurement

What it suffers from
Savings are claimed without a baseline: recommendations are written, work is done, then no documented measurement proves the effect, so the work stays theoretically convincing and unprovable to the client.
What fits it
A documented baseline before any implementation, a regular reading record with written reference conditions, a published calculation method agreed in advance, and an impact report presenting the result as it is — including what did not improve.

What does not fit you: Relying on bill-to-bill comparison without adjusting for conditions, promising a saving percentage before measurement, and omitting what did not improve because it weakens the story — which is the first thing to destroy trust at the first review.

The bands here are indicative guidance rather than an official classification, and the criterion is the nature of the obligation: delivering a project, operating an asset, the performance of an asset you own, or a published measurement result. Two segments can coexist in one company, and each has a different starting point.

Symptoms

What usually shows up in energy companies

Eight recurring symptoms, each with a different root cause — which is why the treatment differs even when the complaint sounds the same.

No documented asset register

What exists, where and under which number and warranty is unknown, so every decision rests on memory and every claim starts with a search.

Cause: no asset record

Items and claims in a spreadsheet

Items are not tied to documented execution, so the claim rests on an estimate and collection is delayed or partially rejected without a clear reason.

Cause: no link to execution

Maintenance at the fault rather than before

No preventive schedule and no fault log, so the same fault recurs with no view of its frequency, its operational effect or its spare-parts consumption.

Cause: maintenance without a log

A reading with no reference conditions

A figure is recorded without the conditions around it (weather, operation, output), so periods with different conditions are compared and an untrue effect is inferred.

Cause: measurement missing its context

Spare parts not tied to the asset

Parts are issued with no link to an asset or a fault, so shortages appear when needed and purchases repeat, and which asset consumes most is unknown.

Cause: undocumented issue

A warranty whose deadline is unknown

The warranty sits in a contract or an email with no alert before it ends, and is discovered after expiry at the first costly failure.

Cause: no warranty alert

A saving claim with no baseline

Bill is compared with bill without adjusting for conditions, so the effect looks larger or smaller than reality and the figure becomes challengeable at the first review.

Cause: no baseline

A field team documenting after returning

Documentation is written in the office at day or week end, so detail is lost and work is recorded without photos, location or real timestamps.

Cause: deferred documentation

Components

What we implement in your operation

Eight components built in order according to your segment; we do not implement all of them for an operation that does not need them all.

Asset register, numbers and warranties

A record per component with its number, location, vendor, warranty and installation date, and alerts before a warranty ends or maintenance falls due — the base everything else is built on.

The base

Project items and proof of execution

Numbered items per project, proof of execution with photo, location and timestamp, and an item closed after its criterion is met — not after it is claimed.

Execution documented

Progress claims and submissions

A claim built on documented execution with published rules, its attachments, its reconciliation with accounting, and a record of what was submitted, approved or rejected and why.

Collection without dispute

Preventive schedule and work orders

Published maintenance cycles per asset type, work orders with proof of execution, a fault log with cause and duration, and plan against actual.

Before the fault

A field app that works offline

An app for the technical team that works without a connection and syncs later: work orders, checklists, photos, location and the meter reading taken on the visit.

Documented in the moment

Reading and measurement record with a baseline

Readings with their reference conditions, a documented baseline before any implementation, and a published calculation method agreed before measurement rather than after.

Measurement, not impression

Spare parts and operational stock

Parts tied to the asset and the fault, a reorder point for critical items, and known consumption per site instead of buying when something runs out.

Documented issue

Performance and adherence reporting

Reports decisions can be read from: preventive adherence, fault recurrence and its causes, proof-of-execution completeness, warranty status, and period performance against the previous one on a published basis.

A decision, not an archive

Method

The method: from the asset register to operation

Eight stages, each with a published output, starting with the asset register and the baseline rather than with configuration — because computing performance without a record or a baseline produces a false number.

  1. 01

    Assessment and segment

    A visit covering sites, assets and projects, establishing the real segment, what runs on spreadsheets today, and where the largest operational or contractual risk sits.

    Output: an assessment naming your segment
  2. 02

    Asset register and baseline

    Registering assets with their numbers, locations and warranties, and documenting the baseline for readings and existing projects — before any configuration.

    Output: an asset register and a baseline
  3. 03

    Configuration and testing

    Configuring work orders, claims and maintenance, and running a full cycle on real data: fault, work order, execution, proof, closure, claim.

    Output: one complete tested cycle
  4. 04

    Field app and training

    Training technical teams to document in the moment while offline, on checklists and meter reading, with illustrated guides left with you.

    Output: a guide per role
  5. 05

    Phased go-live

    Going live on one site, project or asset type first, then expanding — not switching all sites in a single day.

    Output: one site running, then expansion
  6. 06

    Maintenance and warranties

    Running preventive cycles, tying faults and parts to the asset, and activating warranty and inspection alerts before they fall due.

    Output: preventive maintenance running
  7. 07

    Integration and reconciliation

    Connecting meters and devices where an interface exists after inspecting it, connecting e-invoicing and accounting, reconciling claims and balances, and closing a first period.

    Output: a documented close with its differences
  8. 08

    Periodic improvement

    A periodic review: which asset’s faults recur, where claims are delayed, which reading is missing its conditions, and which report nobody uses and should be dropped.

    Output: a periodic improvement report

The durations shown are planning ranges to help you build your schedule, not contractual commitments: the actual duration depends on how ready your asset register is, how clean your items are and how quickly claims are approved, and can be affected by operational peak seasons.

Measurement

What we measure in an energy project

Indicators read from the operation itself, not promises about market or generation figures.

Asset-register completeness

The share of assets registered with a number, location, vendor and warranty, because an unregistered asset can be neither maintained nor claimed under warranty.

Preventive maintenance adherence

The share of preventive cycles executed on time against those due, because the shift from reaction to prevention is measured by this figure rather than by intent.

Proof-of-execution completeness

The share of items and orders closed with documented evidence (photo, location, timestamp), because an item without evidence does not count in a claim.

Claim accuracy

The share of claims accepted on first submission and what was rejected and why, because repeated rejection means items not tied to documented execution.

Reading-record completeness

The share of readings recorded with their reference conditions, because a reading without context produces an unfair comparison and a challengeable figure.

We announce no saving percentage, no generation figure, no uptime and no efficiency improvement, and no figures about market size or programme targets. What we measure is asset-register completeness, adherence to the preventive maintenance schedule, proof-of-execution completeness, claim accuracy, and completeness of the reading record with its reference conditions — figures read from your system about your operation.

Integration

Where the system lives in your operation

We connect what you have instead of forcing its replacement, and we inspect every interface before promising it.

Odoo (projects, stock and accounting)

The project, the claim and spare parts on the same stock and accounting entries, so the work is not run in two systems.

The primary integration

Meters — where an interface exists

We read from meters and devices only if they export data through an available interface, and after inspecting it; we neither supply nor calibrate meters or sensors.

An explicit boundary

E-invoicing

Connecting works and services invoices to the statutory integration with a log of every submission and response, and reports for anything failed or rejected.

With a documented log

Sites and maps

Connecting sites to capture coordinates and evidence where work was executed, after site names and numbers are unified — not before.

After sites are unified

Client and vendor systems

Receiving work orders from the client’s system and returning execution status to it, after inspecting its interface; if it has none we say so.

After the interface check

Boundaries

Where our scope stops — written before you ask

In energy, a management system gets conflated with engineering design, installation, approvals and hardware, so the separation is written out plainly.

EPC works and electrical installations

We are not an EPC or electrical contractor: we supply no panels, inverters or transformers, do not install or connect them, and do not test them.

Certified engineering design and approvals

We issue and stamp no certified engineering design and do not handle regulatory, utility or grid-connection approvals or studies.

Meters, sensors and measurement devices

We supply no meters, sensors or measurement devices and do not calibrate them; where an existing device exposes an interface we read from it after inspection.

Guaranteed saving, generation or uptime

We guarantee no saving percentage, no generation figure, no uptime and no efficiency improvement; those are set by the tariff, the weather, the equipment, consumption behaviour and maintenance.

When what is needed falls outside our scope we say so in the assessment and refer a licensed specialist instead of accepting it and learning at your project’s expense. That is written in the contract, not left to courtesy.

FAQ

Questions specific to energy companies

Direct answers on segments, scope, responsibilities and what we do not guarantee.

How do you treat a contractor, an operator, an asset owner and an efficiency provider differently?

By fit rather than price: a contractor suffers because a project is known from spending rather than from progress, so it needs documented items and claims with on-site proof of execution, and running an asset-management system before that is waste. An operator suffers because maintenance is reactive, so it needs a preventive schedule, a fault log with causes, and spare parts tied to the asset. A renewable asset owner suffers because warranty and performance are scattered between vendor files and invoices, so it needs an asset record linking the panel or inverter to its warranty and to production readings. An efficiency provider suffers because savings are claimed without a baseline, so it needs measurement before and after on a published method with written reference conditions. In the assessment we tell you which of these you are.

Do you guarantee a saving percentage or a generation figure?

No. We guarantee no saving percentage, no generation figure, no uptime and no efficiency improvement, because those are set by the tariff structure, the weather, the equipment used, consumption behaviour and maintenance — none of which an administrative system controls. What we do commit to is that what happens is measured: a documented baseline before implementation, readings recorded with their reference conditions, a published calculation method written into the contract, and a result presented as it is even when it falls short of expectation. A guaranteed figure in this sector is a promise nobody making it actually controls.

Do you carry out installation works and engineering design?

No. We are a systems company: we do not undertake EPC works or electrical installations, we supply and install and calibrate no panels, inverters, meters or sensors, we issue and stamp no certified engineering design, and we do not handle regulatory or utility approval procedures. What we do is build the system that runs the work: work orders with proof of execution, the maintenance schedule, the asset and warranty register, progress claims, and the reading and measurement record. Design, installation and approvals remain the responsibility of the licensed party.

What usually stops energy systems projects?

Three things we see repeatedly, none of them technical: no asset register — what exists, where it is and under which warranty is unknown, so everything rests on memory; items and claims not tied to execution — collection is delayed and a dispute arises on every claim; and the absence of a baseline — consumption is said to have fallen with no documented prior measurement, so every saving claim becomes challengeable. That is why we start with the asset register, the items and the baseline, before any promise of a report or an indicator.

Does a small energy company need a full system?

No. It needs three things done well: an asset register with numbers and warranties, documented proof of execution for every job, and a reading or claim record decisions can be built on. A complex maintenance schedule per asset type, connecting meters and advanced dashboards add setup and entry a small team cannot carry and get abandoned after months. An abandoned project is worse than a small successful one — and we say so at assessment stage even when it means a smaller scope for us.

How is an efficiency result measured without promises?

With four conditions written before implementation: a documented baseline of consumption before any change, reference conditions recorded with every reading (weather, operation, output), a published calculation method agreed in advance rather than chosen after seeing the result, and a report that also presents what did not improve. We guarantee no saving percentage because the outcome is affected by the tariff, the weather, the equipment and consumption behaviour. This is not excess caution: any saving figure without a documented baseline destroys trust at the first independent review.

What is out of scope?

EPC works, electrical installations, supply, installation and calibration; certified engineering design and stamping; regulatory, utility and grid-connection approvals and studies; meters, sensors and measurement devices; running field operations and maintenance on your behalf (we run the system, not the crew); guaranteed saving, generation or uptime; system and cloud licences (contracted in your name); and publishing market-size figures or national programme targets. We say all of this at assessment stage, before the contract.

Which segment are you?

Tell us your line of work, number of sites and assets, and whether you run maintenance or efficiency measurement, and we will come back with an assessment naming your segment, the fitting scope — and what does not fit you.

  • An assessment that names your segment
  • A written scope before any commitment
  • A plain statement of what is outside our scope
Request a proposal

Related topics

We are a systems implementation and integration company, not an EPC contractor, an electrical contractor or an approving body: we do not carry out installation or certified engineering design and do not stamp it, we supply and install and calibrate no panels, inverters, meters or sensors, and we do not handle regulatory or utility approvals. We guarantee no saving percentage, no generation figure, no uptime and no efficiency improvement, and we publish no figures about market size or national programme targets, because those outcomes are set by the tariff, the weather, the equipment, consumption behaviour and maintenance. Durations shown are planning ranges rather than commitments, and the scope of work is written into the contract.