Current plan
M-01 running
- Energy over 30 min
- 31.1 kWh
- Peak power
- 64.7 kW
Energy Monitoring
Know where your electricity goes
Connect the power meters you already have over RS485 / Modbus to the AIoT Gateway, and see the consumption of each panel and line on one dashboard, with alerts when a value crosses its limit.
Common problems
- The electricity bill is high, but nobody knows which machine or line drives it
- Peak demand is exceeded without anyone noticing, until the monthly bill arrives
- Meters are still read by hand — data is late, incomplete and hard to compare
What we measure
Values read from your equipment
Read through the gateway, shown on the dashboard, with history charts.
- Energy (kWh)
- Power (kW)
- Voltage (V)
- Current (A)
- Power factor (PF)
- Demand
Calculated indicators
Coming soonThese indicators are in development and will be enabled step by step. You can preview them in the demo.
- Electricity cost at TOU rates
- Daily / monthly peak demand
- Estimated CO₂ emissions
- Energy share by area or production line
Data path
From shop-floor equipment to dashboards and alerts.
Scroll to explore the connection path →
Power meter
Meters in the MDB or sub-panels
RS485 / Modbus
Modbus RTU or Modbus TCP
AIoT Gateway
Reads values; buffers when the connection drops
4G
Dual SIM or site LAN, encrypted with TLS
AIoT TH Cloud
Time-series storage, isolated per organization
Dashboard / Alerts
On the web; alerts via LINE and email
What you get today
Available as soon as the gateway is installed.
Dashboards
Latest values and charts for every data point, on desktop and mobile.
History
Detailed data for 30 days on every package; longer history is kept as summarised data, by package.
Threshold alerts
Set a high / low limit per data point. When a value goes out of range, you are alerted via LINE and email.
Offline alerts
Get alerted when a gateway or device stops sending data — no need to wait for someone to notice.
AI Insights
Coming soonAI capabilities are on our roadmap. They are not available yet.
- Anomaly detection based on each data point's usual pattern
- An AI-written daily summary report
- An AI assistant that answers questions from your data, citing the actual readings
Example: flag a machine that uses more energy than its own usual pattern.
FACTORY APPLICATIONS
From a site problem to a practical system
Illustrative system designs with equipment, data, responsible teams and project conditions. These are not customer case studies.
DIGITAL TWIN · SIMULATED
Simulated digital twin: site, equipment and events in one view
This simulated digital twin is a model running in your browser. It does not mirror a PLC or customer site and does not control equipment.
Loading 3D map…
Live (simulated) · 08:00:00
Illustrative 3D layout, not surveyed coordinates. Scene labels show values from the simulated twin. Select equipment on the scene or in the twin tree.
Total power62.0 kW
M-02 temperature46.0 °C
M-02 vibration2.10 mm/s
WHAT-IF · SIMULATED
Current plan vs alternative · next 30 simulated minutes
Alternative
M-01 stopped
- Energy over 30 min
- 17.4 kWh
- Peak power
- 36.2 kW
Computed from the browser simulation to compare choices; not a prediction for a real site.
Inspection and command history
Select a scene device, then inspect or control it
Data path
PLC / Meter → Modbus TCP / RS485 → Gateway → MQTT TLS :8883 → Monitor
CCTV uses IP over PoE / NVR independently of LoRaWAN. This scene is illustrative and has no live video.
Operator view
Connect power readings and machine states to site locations for maintenance inspection.
ILLUSTRATIVE SYSTEMUnderstand where and when the factory uses energy
Example system: main switchboard, production line and compressed air
Move from a monthly total to area-level meter readings that engineering teams can use to investigate loads and plan improvements.
Suppose a factory wants to monitor three metering points. Start with readings and history for each point. Cost calculations or energy per unit require additional data and agreed formulas; they are not automatically included.
Problems and practical approaches
The monthly bill does not identify high-load areas
Teams investigate several cabinets and may act on the wrong source
Approach · Define main and submeter boundaries, collect readings by point and compare periods with similar production conditions
Manual readings are recorded at different times in separate files
Differences may reflect timing rather than actual load changes
Approach · Read supported meters through a gateway, standardize names, units and timestamps, and compare values with the meter display
An unusual load is discovered only after the shift
The team lacks event-time data to prioritize equipment checks
Approach · Agree site-specific thresholds, enable scoped notifications and assign a person to investigate the equipment
Equipment and components
- Three compatible meters: main, production line and compressor
- An industrial gateway with matching interfaces, power and connectivity
- Cloud points organized by site, area and asset
- Dashboards, history and notifications within package scope
Data to monitor
- Power in kW and cumulative energy in kWh
- Voltage, current and power factor where exposed by the meter
- Last update time and connectivity status
Data journey
- Electricity meters
- RS485 / Ethernet
- Industrial gateway
- AIoT TH Cloud
- Dashboard / alerts
Workflow and responsibilities
Define circuit boundaries
Electrical engineer
Select comparison points and identify main versus submeter boundaries to avoid double counting
Configure acquisition
Equipment owner
Verify registers, units, CT ratios and polling intervals for the actual meter
Validate source readings
Installer and site team
Compare the dashboard with the meter at matching times and record discrepancies
Monitor load patterns
Energy engineer
Read current values and history alongside operating schedules, not totals alone
Investigate notifications
Maintenance
Check equipment and production conditions before deciding on an operational change
Review changes
Production manager
Compare similar operating periods and record changes and remaining data gaps
How each factory team benefits
Energy engineering
Identify periods and areas that merit further load investigation
Maintenance
Use timestamped readings when checking notified equipment
Production
Review machine-start schedules and shift changes with supporting data
Management and cost planning
Support improvement proposals with measurements; cost formulas still require separate validation
Who this is suitable for
- Factories with multiple circuits or buildings that need separate energy readings
- Engineering teams with readable meters and an owner for source validation
- Projects starting with critical points before a wider rollout
Acceptance checks
- Dashboard values match meter units and scaling
- Stale or missing data and timestamp meaning can be identified
- Owners can find a known event and test notifications within scope
DETAILS & PLANNING
Make energy readings comparable
Choose circuits and verify engineering units
Separate main meters, submeters and monitored circuits to avoid double counting. kW describes power, while kWh describes accumulated energy. Check register scaling and the meter’s CT/PT configuration before displaying values or deriving comparisons.
- Compare units and decimals with the meter display
- Identify per-phase versus three-phase totals
- Record meter replacements and scale changes
Define comparable periods and data coverage
Compare matching time periods and check for missing readings. Cost estimates need a confirmed tariff structure. Energy per unit needs production counts for the same period. A load chart alone does not establish actual billing cost or production efficiency.
- Use consistent site time and check device clocks
- Identify gaps, resets and meter replacements
- Agree calculation rules and analytics scope before use
Systems related to this page
Review each system’s scope before opening it or using the example to plan your project.
Simulated data · No physical PLC commands
Factory Operations
Explore machine states, energy, simulated readings and alarms with a 3D scene and example event history.
Demonstration with simulated data
Demo Center
Explore energy, machine monitoring and OEE examples with a 3D factory to understand data and workflows before planning a project.
Questions about this topic
Can existing electricity meters be connected?
Check for RS485/Modbus RTU or Ethernet/Modbus TCP and a matching register map. A meter without a supported interface may need an additional measurement device.
Does the dashboard replace the utility bill?
Not automatically. Actual charges depend on tariffs, time periods, demand charges and other terms. Validate the calculation and supporting data before using an estimate.
See an example, or talk to our team
The demo uses simulated data from a sample plant. Our team can assess your actual equipment and site.