FAQ
The questions buyers ask before a Demo or Pilot
What DYDON Energy AI OS is, how a Pilot starts, which Energy Assets connect, and how your equipment and data stay safe. If your question is not here, ask us directly.
Product and features
What is DYDON Energy AI OS?
An AI-driven energy operating system that connects the six Energy Asset classes, EV charging, BESS, solar, buildings, fleets and the grid, and orchestrates them as one system. Across those assets it connects, monitors, predicts, optimises, controls and monetises, rather than managing each one on its own.
How do the five product lines relate to the platform?
AiEMS, AiDC OS, Residential DER, EVOS and DYDON VPP share the same engine and are packaged for a specific setting: commercial and industrial storage, AI data centres, home energy delivered through channel partners, EV charging and fleet depots, and cross-asset aggregation into energy markets. Assets on any of the other four product lines can join DYDON VPP.
Do I need to replace my battery, inverter or chargers?
No. DYDON Energy AI OS is hardware neutral: batteries and inverters connect over Modbus and SunSpec, chargers over OCPP, and the equipment you already own stays in place.
Do we need solar or new storage to start?
No. AiEMS works on storage alone; solar improves the economics and joins the same optimisation when it is added. AiDC OS starts with the UPS and batteries already on site and shows what additional storage would be worth before you buy it, and EVOS runs on the chargers alone until storage arrives.
Does AiDC OS put data centre uptime at risk?
No. The reserve requirement is a hard constraint in the plan and is enforced at the edge, so optimisation happens inside the reserve you set rather than at its expense.
Which markets does DYDON operate in?
Australia and Taiwan. DYDON VPP connects to Australian frequency and demand response programmes and to Taiwanese demand response, and the protocol layer itself is not tied to either market.
Getting started: demo and pilot
What are the stages of a deployment?
Five fixed stages: Assessment, Pilot, Deployment, Expansion and Aggregation. Assessment sizes the opportunity from your data, Pilot proves it on one site or feeder, Deployment rolls it out, Expansion adds sites and asset types, and Aggregation connects the fleet to markets through DYDON VPP.
How long does an assessment take?
Usually a few weeks from receiving tariff and interval data to a written assessment and a pilot proposal. For AiDC OS the assessment also covers integration with the UPS and batteries already on site.
What does a pilot need from us?
Tariff and interval data for the site. Most pilots start on a single site, room or feeder before expanding.
What does a channel partner have to build for Residential DER?
Nothing on the software side. You handle hardware, installation and first-line support; DYDON provides the platform, integration and market interface. The app and portal are white-label, you can integrate through the API into your own product, and the customer relationship stays with you.
Energy assets and system integration
Which protocols and vendors are supported?
Equipment that speaks OCPP, OCPI, OpenADR, CSIP-Aus, Modbus, MQTT or SunSpec, plus vendors we have integrated through their APIs. Ask us about a specific model and we will tell you.
Does DYDON need its own hardware on site?
The edge agent runs on a small industrial gateway or on hardware the site already has, depending on the equipment. It does not require DYDON-branded chargers, batteries or inverters.
Which chargers does EVOS support?
Chargers that speak OCPP; vendor-specific behaviour is handled in the integration layer. Public charging away from your sites is tracked through roaming where the operator supports OCPI.
Which batteries and storage systems are supported?
Batteries and inverters over Modbus and SunSpec. For AiDC OS, UPS units with a Modbus or vendor API interface are supported as well, and integration is part of the assessment.
Does it work with our existing energy management, building management or fleet system?
Yes. AiEMS sits alongside a building management or SCADA system and takes over dispatch of the storage and flexible loads only. EVOS takes departure times and energy needs from your fleet management system through the API.
Can we integrate DYDON into our own software, or bring partner assets into DYDON VPP?
Yes. The same APIs that power the white-label products and fleet integrations are available to customers and partners. Assets on DYDON Energy AI OS join DYDON VPP directly, and partner assets join through the API.
Security and data
What happens if the site loses connectivity or DYDON's cloud is unavailable?
The edge agent keeps running the last plan locally, inside the safety envelope, until the cloud reconnects. If the plan expires first, assets fall back to a safe configured state. Nothing on site depends on the cloud to stay safe.
Who can send control commands to our equipment?
Commands that change how equipment behaves are scoped, logged and constrained by the site's safety envelope at the edge. Each edge agent and connected device carries its own identity and credentials, and every call between components is authenticated and authorised.
Where is our data stored?
In AWS regions appropriate to the market. Data residency requirements are agreed per customer.
Who monitors the platform?
Site reliability engineering monitors the platform and sites continuously, with alerting on both software and equipment health.
What happens to my site during a DYDON VPP event, and how is the revenue shared?
Dispatch is automatic and stays inside the site's safety envelope; the asset owner does nothing and sees the event on the dashboard. Programme revenue is settled on the platform and shared with asset owners under the commercial agreement.
Still have a question?
Tell us what assets you run and what you want to know. We will answer directly, or walk you through it on a demo.