Full Track: Author Your Production Intelligence

You chose complete control. Build your production system from first principles.


What You'll Build

By the end of this track:

ComponentScope
ConnectionsAll production data sources
SurfacesPlant → Line → Cell → Station hierarchy
Warm queriesComplete OEE, quality, downtime library
TeamRoles for ops, quality, maintenance, engineering
AI integrationFull MCP connection

Phase 1: Design Production Architecture

Step 1.1: Map Your Hierarchy

Plant
├── Line 1
│   ├── Cell A (Machining)
│   │   ├── Station 1
│   │   └── Station 2
│   └── Cell B (Assembly)
│       ├── Station 1
│       └── Station 2
├── Line 2
│   └── Same structure
└── Support
    ├── Quality Lab
    └── Maintenance

Step 1.2: Identify Data Sources

LevelData SourceMetrics
StationPLC/SensorCycle time, state, counts
CellCell controllerThroughput, WIP
LineMESOEE, yield, batch tracking
PlantAggregationTotal output, efficiency

Step 1.3: Create Connections

Ask Azi:

Azi proposes all connections. Review and approve each.


Phase 2: Create Surface Hierarchy

Step 2.1: Plant Surface

Ask Azi:

"Create a plant-level surface that aggregates all line production data."

Azi proposes:

  • Surface name: Plant-Production
  • Nodes: Line1Total, Line2Total, QualityOverall
  • Description: Plant-wide production aggregation

Step 2.2: Line Surfaces

SurfaceNodesPurpose
Line-1CellA, CellB, LineOEELine 1 detail
Line-2CellA, CellB, LineOEELine 2 detail

Step 2.3: Cell and Station Surfaces

For deep operational visibility:

SurfaceNodesPurpose
Line-1-Cell-AStation1, Station2Machining detail
Line-1-Cell-BStation1, Station2Assembly detail

Your surface hierarchy determines query granularity. A station-level surface enables machine-specific analysis.


Phase 3: Build Comprehensive Query Library

Standard Production Queries

QueryPurposeLevel
plant-oeeOverall plant OEEPlant
line-oeeLine-specific OEELine
station-cycleStation cycle analysisStation
downtime-paretoTop downtime causesPlant/Line
quality-fpyFirst pass yieldLine
throughput-hourlyHourly productionLine

Step 3.1: Plant OEE Dashboard Query

Ask Azi:

"Create a query that calculates real-time OEE for the entire plant, broken down by line."

Azi proposes:

ProductionData
| where Timestamp > ago(1d)
| summarize
    AvailableTime = sum(iff(Status != "Planned Downtime", Duration, 0)),
    RunTime = sum(iff(Status == "Running", Duration, 0)),
    ActualUnits = sum(Units),
    GoodUnits = sum(iff(Quality == "Pass", Units, 0))
    by Line
| extend IdealCycleTime = 30 // seconds - adjust per line
| extend Availability = RunTime / AvailableTime
| extend Performance = (ActualUnits * IdealCycleTime) / (RunTime)
| extend Quality = GoodUnits / ActualUnits
| extend OEE = Availability * Performance * Quality * 100
| project Line, Availability = round(Availability * 100, 1),
          Performance = round(Performance * 100, 1),
          Quality = round(Quality * 100, 1),
          OEE = round(OEE, 1)

Step 3.2: Station-Level Analysis

Ask Azi:

"Build a query that identifies bottleneck stations based on cycle time variance."

StationData
| where Timestamp > ago(8h)
| summarize AvgCycle = avg(CycleTime),
            StdDev = stdev(CycleTime),
            Count = count()
    by Station
| extend CV = StdDev / AvgCycle // Coefficient of variation
| order by CV desc
| project Station, AvgCycle, StdDev, CV, Count

Step 3.3: Quality Traceability

Ask Azi:

"Create a query that traces all process steps for a specific lot number."

ProductionData
| where LotNumber == "{lotId}"
| join kind=leftouter QualityData on LotNumber
| project Timestamp, Step, Station, Operator,
          Measurement, Status, InspectionResult
| order by Timestamp asc

Phase 4: Establish Team Permissions

Step 4.1: Define Roles

RoleAccessScope
EngineeringFull accessAll surfaces, all queries
OperationsLine surfaces, run queriesProduction data
QualityQuality surfaces, editQC-specific queries
MaintenanceDowntime surfacesEquipment-focused
ManagementPlant surface, viewDashboards only

Step 4.2: Invite Team Members

Ask Azi:

"Invite quality-manager@company.com as Editor for Quality surfaces."

Step 4.3: Configure Surface Permissions

SurfaceAdminEditorViewer
Plant-ProductionEngineeringOperationsManagement
Line-1EngineeringOperations-
Quality-ControlEngineeringQualityOperations
Thinking Tip:

Quality can edit quality queries but only view production data. This prevents cross-contamination of metrics.


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": {
    "production-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "@openindustrial/mcp-server",
        "--workspace", "YOUR_WORKSPACE_ID",
        "--token", "YOUR_TOKEN"
      ]
    }
  }
}

Step 5.3: AI-Powered Analysis

Ask Claude:

"Why did Line 1 miss its production target yesterday? Show me the contributing factors."

Claude queries OEE components, downtime events, and quality data—then correlates them to identify root cause.

You built the entire production intelligence system. Every connection, surface, and query. Now any MCP-native AI can analyze it—through your governed layer.


What You Built

ComponentCount
Connections3+
Surfaces6+ (plant → station)
Warm queries6+
Team rolesConfigured
MCP integrations1+

Category Metrics

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

What Governed Production Intelligence Looks Like

Before Control PlaneAfter Control Plane
Different OEE per systemOne definition, one number
Tribal knowledge on metricsDocumented, governed queries
AI recommendations without contextAI insights with full data lineage
Manual root causeData-driven, traceable analysis

Next Steps

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