⌁ operational intelligence for grid infrastructure

We translate between what your assets actually do and what your models assume they do.

Grid assets are physical objects.

Their behaviour is encoded in operational data that most financial and regulatory processes never touch.

We close that gap.

Get it wrong and it surfaces as a rejected capex program, a mispriced asset, or a fault no one saw coming.

⊟ The problem:

Electricity distributors own physical infrastructure with 40–60 year asset lives.

The decisions being made now about what to replace, what to maintain, what to invest in — these are long-horizon decisions made from data that is frequently wrong, incomplete, or locked inside the heads of engineers approaching retirement.

When that knowledge leaves, regulatory submissions get built on assumptions the operational people know are wrong.

Capital programs hit undocumented field conditions at every turn.

AER challenges land on expenditure that can’t be evidentially defended because the data quality underneath the justification is poor.

That’s when it gets expensive.

⊟ Services:

Three problems. One domain. No generalism.

01 — Operational Data Verification

Your financial model and your regulatory submission make assumptions about how your assets perform.

We go into the operational data — SCADA historian, protection event logs, work management records — and establish what’s actually happening versus what you’re assuming.

Where gaps exist, we quantify them, explain the physical cause, and build the monitoring infrastructure that makes this continuously visible — not discovered at the point of a fault investigation or an AER challenge.

Example: a revenue proposal assumes a fleet at 98.5% availability. The historian says 96.1%, and the derating signature explains why.

Across a five-year determination, that 2.4 points is the difference between a capex program the AER funds and one it sends back — and it is far cheaper to know before you submit than after the independent reviewer finds it.

↳ Deliverable: verified performance baseline against model assumptions, quantified gap analysis, monitoring infrastructure specification.

02 — Regulatory Submission Support

AER scrutiny of capex justification is specific: prudency requires evidence, efficiency requires options analysis, and both require data whose provenance you can demonstrate under cross-examination.

We build the data layer that makes your submission credible and auditable.

Connecting asset condition data, failure history, and load projections into a technical narrative that holds up when the independent reviewer starts asking questions.

↳ Deliverable: traceable evidentiary data layer, failure probability modelling, regulatory-ready capex justification documentation.

03 — Asset Data Infrastructure

New assets are commissioned with enormous volumes of test records, protection settings, and as-built data that immediately becomes static and unsearchable.

Existing assets carry operational history that lives in experienced engineers’ heads and nowhere else.

We design and build the systems that capture this — structured, queryable, linked to the historian — at commissioning rather than retrofitted a decade later when something fails and nobody can find the original settings.

↳ Deliverable: operational data layer connecting physical documentation to real-time performance, built for the asset lifecycle not the project closeout.

⊟ Who calls us:

Always at a capital event, never in steady state — an acquisition, a commissioning handover, a determination window. Operations budgets defer this work; capital events pay for it.

⊹ Asset Manager — Distributor

Ageing transformer fleet. Can’t quantify the risk in a form the AER will accept as evidence for a capex program. Needs the gap between operational data and regulatory evidence closed before the next submission window.

⊹ Project Manager — Commissioning

Commissioning data is a mess of spreadsheets and PDFs. Needs it structured, linked to the historian, and queryable before the AER review — not twelve months after handover when something fails and nobody can find the original protection settings.

⊹ Infrastructure Fund — Due Diligence

Making a long-duration bet on a distribution asset. Needs someone to independently assess whether the capex forecast in the information memorandum reflects what the operational data actually says about asset condition and performance trajectory.

⊹ Regulatory Affairs — Revenue Proposal

Eighteen months from the submission deadline. The evidentiary foundation for the capex program is still being manually reconciled across four systems by a team hoping the AER doesn’t look too closely. Needs that replaced with a systematic capability.

⊟ Domain:

What a binding constraint looks like in the dispatch data.

What a transformer derating signature looks like in the historian before the field crew confirms it.

How the AER applies prudency and efficiency tests to capex justification.

What the regulatory asset base means for capital allocation decisions.

That domain knowledge is not incidental to the service. It is the service.

A data engineering firm without it cannot do this work credibly.

We don’t pretend otherwise and we don’t compete on price with firms that do.

We price against the size of the decision, not the size of the timesheet.

⌁ Regulatory: AER determination process, DNSP revenue framework, STPIS reliability incentives, capex prudency and efficiency tests, regulatory asset base mechanics.

⌁ Operational Technology: SCADA historian, PI/OSIsoft, protection relay systems, IED configuration, RTU telemetry, fault event logging, DERMS integration.

⌁ Asset Management: zone substation topology, feeder-level condition assessment, failure probability modelling, maintenance optimisation, asset lifecycle economics.

⌁ Data Infrastructure: column-level lineage, operational data verification, cross-system reconciliation, as-built data capture, historian-linked asset documentation.

⊟ What we’re not:

× A generalist data consultancy that happens to have done some energy work

× Staff augmentation with a company name and a better day rate

× IT consulting that treats the grid like any other enterprise infrastructure problem

× A platform or SaaS product looking for a distribution network to prove itself on

× Available for projects outside the NEM grid infrastructure domain, regardless of the day rate

⊟ Contact:

If the problem is real, let’s talk about it.

We don’t do capability presentations.

If you have a specific operational data problem, a regulatory submission challenge, or an asset data gap that needs closing — describe it and we’ll tell you whether we can help.

Melbourne, AU — Distribution Networks — NEM

⇱ marzella@motis.group