INDUSTRY JOURNEY
Energy Monitoring
Your energy bill just spiked 40%. No one knows which line caused it.
Energy data lives everywhere - meters, a BMS, SCADA, utility feeds. This journey brings it into one workspace and turns it into saved queries everyone reads the same way.
The challenge
Energy management in an industrial facility runs into:
- Scattered data - meters, submeters, BMS and utility feeds in different systems
- No allocation - consumption cannot be traced to a line or a process
- Reporting burden - sustainability reports need manual data collection
- Hidden waste - inefficiencies buried in aggregate numbers
What OpenX gives you
| Capability | How it helps |
|---|---|
| One consumption view | Every meter and source on surfaces in one workspace |
| Cost allocation queries | Azi proposes warm queries that trace consumption to processes |
| A record of changes | Once Provenance is set up in your landing zone, Saves to connections, surfaces and warm queries are recorded; accepted proposals are not (what is recorded) |
| Any AI over MCP | Claude, ChatGPT or Cursor reads the same saved queries |
When someone asks "How did you calculate that?", you show them the saved query behind the number.
What you will build
| Component | Description |
|---|---|
| Connections | Power meters, gas meters, BMS feeds, utility data |
| Surfaces | Building-level, line-level and equipment-level monitoring |
| Warm queries | Consumption tracking, cost allocation, demand analysis |
| API endpoints | ERP integration, sustainability reporting, dashboards |
| MCP | Energy questions answered by any MCP client |
Two tracks
Track A: Hybrid - monitor without replacing
You have meters, a BMS and an energy management system. This track adds OpenX beside them:
- Bring existing meter data in through a live-device connection
- Create surfaces by building, floor or line
- Build allocation queries with Azi
- Call those queries from your reporting tools
Track B: Full - meter it all
Starting fresh, or want complete control:
- Design your metering architecture from scratch
- Create a complete surface hierarchy
- Build a query library
- Give operations, sustainability and finance the access they need
Before you start
| Requirement | Details |
|---|---|
| An OpenX workspace | See Get a Workspace |
| Azure (optional) | Live devices use Fathym's shared IoT hub until your workspace has its own landing zone and IoT fabric in your Azure subscription |
| Data sources | Meters, a BMS, or a Simulator node |
TIP
No meters connected yet? Shape a Simulator node like your meter readings and follow along. The surfaces and queries are the same.
Why it matters
Sustainability reporting
| Requirement | How saved queries help |
|---|---|
| Scope 1 emissions | One saved query over gas consumption |
| Scope 2 emissions | One saved query for electricity allocation |
| Reduction targets | A documented baseline, and progress against it |
Cost allocation
- By department: which team consumes what
- By process: which production lines cost most
- By time: peak demand against off-peak
AZI
When someone asks "Why did our bill go up?", I can propose queries that trace consumption to specific lines, shifts or equipment, for you to accept.
Choose your track
Next steps
- Other industries -> Industry journeys
- Common query shapes -> Query Patterns