Use case · Analytics
Smart analytics
wattiot learns what is normal for each machine, spots what leaves that range, and an agent has the report ready before the shift starts.
01The situation
Nobody looks at the data at three in the morning.
Compressors do not stop when production does. A leak, a valve left open or a badly scheduled dryer keeps drawing power all night, and on the dashboard it looks like any other night.
Seeing it takes knowing what is normal for each machine at each hour, and someone checking every day. In a small plant, that someone does not exist.
What is normal for each machine, learned from its own data.
TodayFixed thresholds nobody updates.
What leaves the range, with the report already written.
TodaySomeone has to catch it in time.
Your questions, in plain language.
TodayExport to Excel and cross-check by hand.
02The schema
From the compressor room to your inbox.
The same signals that already reach wattiot Core feed anomaly detection, the agents and the assistant. There is no second system to integrate.
What you already have
- Compressor 1
- Compressor 2
- Dryer
- Air flow
What wattiot adds
- Modbus TCP readsactive
- Local bufferready
- Encrypted uplinkTLS 1.3
- P10–P90 bandlearned
- kW_Air47 kWout
- Productionstopped
- Temporal03:00
- Generar Informegenerated
- Notificar Emailsent
- CompressorsPower of the compressors and the dryer, and air flow, over Modbus TCP.
- wattiot EdgeReads, stores locally if the network drops and sends encrypted to the cloud.
- wattiot CoreLearns each signal's normal band and flags whatever leaves it.
- AI agentEvery day at 03:00 it reviews the night, writes the report and emails it.
03From data to result
From a normal band to a report in your inbox.
Nobody sets a threshold: the band comes from each signal's own history. When the night leaves it, the agent finds it, puts a number on it and raises it. Whatever is left to know, you ask the assistant.
- 1Normal band
Compressed airkW_Air
P10–P90 band
Each signal's usual range, P10–P90, learned from its own history.
- 2Anomaly
213 kWh, no production
Production · runningstopped
Production stops at 22:00, but the air stays at 47 kW and leaves the band.
- 3AgentActive
Agent · Night watch
Scheduled · every day03:00
Review the night shift and act on compressed-air waste.
213 kWh with no production since 22:30.
- Shift report
- Email to maintenance
At 03:00 it reviews the shift, works out the kWh with no production and acts.
- 4Report and assistant
Email · 03:01To: maintenance
Compressed air: 213 kWh with no production
Shift report · PDFHow much did compressed air use last week, and where is it heading?
wattiot18.4 MWh. 31% of it ran with no production, mostly on night shifts.
The report lands in maintenance's inbox. For the rest, the assistant.
04Spec sheet
What the installation takes.
For the technical lead: where each reading comes from, how it is read and what it becomes.
- Sources
- Two compressors, a dryer and an air flow meter
- Protocol
- Modbus TCP. Read-only
- Detection
- Normal P10–P90 band, learned per signal
- Operational contexts
- Production running or stopped, and shift
- Agent
- Temporal trigger at 03:00, Generar Informe and Notificar Email
- Assistant
- Plain-language questions about signals, contexts and KPIs
- Alerts
- Email, push and a shift report as PDF
- On site
- One wattiot Edge on the room's network
Does this look like your plant?
We will show you on a scenario like yours: what to connect first, what you will see and which plan fits.