How Energy & Utilities teams in Australia automate repetitive work with AI while respecting the Privacy Act and sector rules — implemented by dgm on osFoundry.
dgm is an independent osFoundry integration partner — not affiliated with osFoundry’s maker (OS LLC), and dgm has no completed client integrations yet.
Automation is where AI pays for itself in energy & utilities — but the goal is a measurable reduction in manual work on a specific workflow, not ‘AI everywhere’. Here is a sensible way to approach it in Australia.
What to automate first in energy & utilities
Good first candidates are high-volume, repeatable and text- or data-heavy: grid and demand forecasting, predictive maintenance on network assets and load optimisation are typical. Avoid starting with one-off or highly bespoke work — the return is harder to prove.
A practical automation sequence
- Pick one repetitive energy & utilities workflow — for example grid and demand forecasting — and write down the current steps and time spent.
- Set a baseline so you can measure improvement, and confirm where the data lives and whether it must stay in Australia.
- Build a small automation with a human in the loop, check its output against the regulator expectations that apply, then expand.
| Stage | Focus |
|---|---|
| Scope | One workflow, current steps, time spent |
| Baseline | Measurable starting point + data-residency check |
| Pilot | Human-in-the-loop build, checked against compliance |
| Expand | Roll out once value is proven |
Compliance while you automate
The Australian Energy Regulator (AER) economically regulates electricity and gas networks and markets across the National Electricity Market (all states and territories except WA); state economic regulators such as IPART (NSW) and the Essential Services Commission (Victoria) set water pricing, and the Bureau of Meteorology holds a statutory water-information role. Price-determination data and reliability/safety obligations shape how AI is deployed, and critical-infrastructure security expectations apply. Because there is no standalone AI law in force in 2026, the constraints to design around are privacy (the Privacy Act 1988 and the Australian Privacy Principles), the Australian Consumer Law, and the sector rules above.
Keeping automation in Australia
Critical-infrastructure and customer data favour in-region or self-hosted AI. osFoundry’s managed cloud pins data to the US, EU or Japan — it does not currently offer an Australian managed region. For data that must stay in Australia, the honest path is self-hosting osFoundry (BYO Cloud) inside an Australian cloud region such as AWS (Sydney or Melbourne), Microsoft Azure (Australia East, Australia Southeast or Australia Central in Canberra) or Google Cloud (Sydney or Melbourne), or running models locally on-device. osFoundry can run your chosen model under one layer and be self-hosted in an Australian region or run locally for sensitive workflows.
Where dgm fits
dgm is an independent integration partner that helps Australian businesses adopt osFoundry — scoping a first use case, handling the build, and connecting AI to the systems you already run. dgm can build the first energy & utilities automation with you and keep a human in the loop. dgm is independent of osFoundry’s maker (OS LLC) and has no completed client integrations yet, so everything described here is a service offered, not a past result. If you want to scope a practical first project, dgm can help you map it out.