- Step 01
Connect the data
EnergyAI Ops connects to the site's existing infrastructure. No equipment needs to be replaced.
- electricity meters
- sensors and controllers
- SCADA, BMS, DCIM, EMS
- Modbus RTU/TCP, RS-485
- APIs, CSV and Excel
- maintenance logs
- Step 02
Digital equipment passport
Manuals, procedures, specifications and maintenance history become a structured digital passport.
- type, model, serial number
- specifications and operating limits
- normal modes
- connected meters and channels
- event, maintenance and repair history
- documentation and engineers' notes
AI helps extract information from documents, but safety-critical fields are approved by a specialist.
- Step 03
Observation and baseline
In the first days, the system learns how the equipment behaves and checks data quality. Initial observation usually takes 2 to 5 days. At this stage EnergyAI Ops gives no final diagnosis - it builds an initial baseline, a model of normal equipment behaviour.
- the site's operating mode
- data quality and completeness
- seasonality
- number of operating cycles
- emergency and rare modes
Model maturity depends on these factors.
- Step 04
Detect deviations
The platform compares current readings with the normal mode and flags unusual changes.
- rising energy use
- phase imbalance
- falling power factor
- unstable operation
- running outside the schedule
- changes after a repair
- Step 05
Analyse the context
EnergyAI Ops does not treat every signal as a failure. It checks the context - which cuts useless alerts and makes recommendations better grounded.
- production schedule
- temperature and weather
- load changes
- recent maintenance and switching
- neighbouring equipment
- history of similar events
- Step 06
Engineer confirmation
The engineer remains the decision owner. Feedback is stored and refines models, rules and baselines.
- normal mode
- needs observation
- needs inspection
- technical action required
- false alarm
- confirmed fault
- Step 07
Verify the result
After maintenance, EnergyAI Ops compares readings before and after the work. Maintenance becomes a closed, verifiable loop.
- did the deviation disappear
- did the reading return to normal
- did energy use change
- does the problem persist
- is another check needed