Full Track: Meter It All

You chose complete control. Build your energy intelligence from scratch.


What You'll Build

By the end of this track:

ComponentScope
ConnectionsBuilding, floor, line, and equipment meters
SurfacesComplete hierarchy from campus to equipment
Warm queriesComprehensive energy analytics library
TeamRole-based access for ops, sustainability, finance
AI integrationFull MCP connection

Phase 1: Design Metering Architecture

Step 1.1: Map Your Hierarchy

Before creating connections, map what you'll monitor:

Campus / Facility
├── Building 1
│   ├── Floor 1
│   │   ├── Production Line A
│   │   └── Production Line B
│   └── Floor 2
│       ├── Office Space
│       └── Data Center
├── Building 2
└── Utilities
    ├── Chiller Plant
    └── Compressed Air

Step 1.2: Identify Metering Points

LevelMetersData
CampusMain utility meterTotal consumption, demand
BuildingBuilding submetersElectrical, gas, water
FloorDistribution panelsCircuit-level consumption
EquipmentIndividual metersMachine-specific usage

Step 1.3: Create Connections

Ask Azi:

Azi proposes all connections. Review and approve each.

Thinking Tip:

Start with the simulator if hardware isn't ready. The data structure and queries work identically.


Phase 2: Create Surface Hierarchy

Step 2.1: Campus-Level Surface

Ask Azi:

"Create a surface for campus-wide energy monitoring that aggregates all building data."

Azi proposes:

  • Surface name: Campus-Energy
  • Nodes: Building1Total, Building2Total, UtilitiesTotal
  • Description: Facility-wide energy aggregation

Step 2.2: Building Surfaces

Create a surface for each building:

SurfaceNodesPurpose
Building-1-EnergyFloor1, Floor2, HVAC, LightingBuilding breakdown
Building-2-EnergyProduction, Office, SupportBuilding breakdown
Utilities-EnergyChiller, CompressedAir, SteamCentral utilities

Step 2.3: Production Surfaces

Granular tracking for manufacturing:

SurfaceNodesPurpose
Line-A-EnergyMotors, Conveyors, HVACLine-level allocation
Line-B-EnergyMotors, Conveyors, HVACLine-level allocation

Your surface hierarchy determines your query granularity. Design it to match your reporting needs.


Phase 3: Build Comprehensive Query Library

Standard Queries

Build these essential queries with Azi:

QueryPurposeFrequency
daily-consumptionDaily kWh by buildingDaily
monthly-costMonthly cost by areaMonthly
peak-demandPeak demand analysisOn-demand
baseline-comparisonCurrent vs baselineMonthly
sustainability-scope2Scope 2 emissions calcQuarterly

Step 3.1: Daily Consumption Query

Ask Azi:

"Create a warm query that shows daily electricity consumption broken down by building."

Azi proposes:

EnergyData
| where MeterType == "Electric"
| where Timestamp > ago(30d)
| summarize DailyKWh = sum(kWh) by bin(Timestamp, 1d), Building
| pivot Building, sum(DailyKWh)
| order by Timestamp asc

Step 3.2: Cost Allocation Query

Ask Azi:

"Build a query that allocates energy costs to each production line based on their consumption percentage."

let TotalConsumption = EnergyData
| where Timestamp > ago(1M)
| summarize Total = sum(kWh);
EnergyData
| where Timestamp > ago(1M)
| summarize LineConsumption = sum(kWh) by ProductionLine
| extend Percentage = LineConsumption / toscalar(TotalConsumption) * 100
| extend AllocatedCost = Percentage / 100 * 50000 // Monthly energy budget
| order by AllocatedCost desc

Step 3.3: Sustainability Reporting Query

Ask Azi:

"Create a query for Scope 2 emissions calculation using grid emission factors."

EnergyData
| where MeterType == "Electric"
| where Timestamp > ago(1y)
| summarize TotalKWh = sum(kWh) by bin(Timestamp, 1M)
| extend EmissionFactor = 0.42 // kg CO2 per kWh - update for your grid
| extend Scope2Emissions = TotalKWh * EmissionFactor / 1000 // tonnes
| order by Timestamp asc

Phase 4: Establish Team Permissions

Step 4.1: Define Roles

RoleAccessUsers
AdminEverythingIT, Engineering
SustainabilityAll queries, edit for emissionsSustainability team
FinanceCost queries, view-onlyFinance team
OperationsBuilding surfaces, readFacility managers

Step 4.2: Invite Team Members

Ask Azi:

"Invite sustainability-lead@company.com as Editor for the sustainability queries."

Step 4.3: Set Surface Permissions

Restrict sensitive cost data:

  1. Open Cost-Allocation surface
  2. Click Permissions
  3. Limit to Finance and Admin roles
Thinking Tip:

Sustainability can see consumption but not cost allocation. Finance sees costs but not operational details.


Phase 5: Connect External AI Tools

Step 5.1: Generate MCP Configuration

  1. Open the APIs menu in the top bar
  2. Select API Keys to generate a JWT token
  3. Copy your workspace ID from the workspace settings
  4. Use the configuration below with your credentials

Step 5.2: Configure Claude Desktop

{
  "mcpServers": {
    "energy-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "@openindustrial/mcp-server",
        "--workspace", "YOUR_WORKSPACE_ID",
        "--token", "YOUR_TOKEN"
      ]
    }
  }
}

Step 5.3: AI-Powered Analysis

Ask Claude:

"What areas have the highest energy intensity and what's driving it?"

Claude queries your governed data, correlates consumption with production metrics, and provides insights—all auditable.

You built the entire energy intelligence system. Every meter, every surface, every query. And now any MCP-native AI can analyze it—through your governed layer.


What You Built

ComponentCount
Connections5+
Surfaces6+
Warm queries5+
Team rolesConfigured
MCP integrations1+

Category Metrics

MetricYour Result
Time to First Governed Query~1 hour
Query library5+ queries
Surface hierarchy3 levels
Audit coverage100%
AI connectedMCP-native

What Governed Energy Intelligence Looks Like

Before Control PlaneAfter Control Plane
Spreadsheet emissions reportsGoverned, auditable queries
"Trust me" allocationsTraceable cost calculations
AI recommendations without dataAI insights with full lineage
Scattered meter dataUnified, governed view

Next Steps

If you want to...Go to...
Try the Hybrid trackHybrid Track →
See query patternsPatterns →
Learn more about MCPMCP Guide →
Explore manufacturingManufacturing Journey →
On this page