Pharma Factory Journey

Batch 112A just failed compliance. No one can explain why.


The Challenge

Pharmaceutical manufacturing demands:

  • Complete traceability - Every batch, every reading, every decision
  • Audit-ready data - Inspectors need proof, not promises
  • Rapid response - Compliance failures cost millions
  • Cross-system visibility - Data scattered across historians, SCADA, MES

Traditional approaches fail because:

  • Data lives in silos
  • Query logic isn't tracked
  • AI answers can't be audited
  • Nobody owns the full picture

The Solution: Governed AI

OpenIndustrial provides the Control Plane that connects your data and governs your queries:

CapabilityHow It Helps
Azi-built queriesNatural language to KQL, with your approval
Full audit trailEvery query, who ran it, when, what parameters
MCP-native AIConnect Claude or Copilot to governed data
Role-based accessQA sees QA data, Ops sees Ops data

This isn't AI with guardrails. This is a fundamentally different architecture—where AI proposes and you decide.


What You'll Build

By the end of this journey, you'll have:

ComponentDescription
ConnectionsTemperature, pressure, batch data from your systems
SurfacesCleanroom monitoring, QA gating, batch tracking
Warm queriesCompliance checks, threshold monitoring, trend analysis
API endpointsREST APIs for LIMS, MES, or custom dashboards
MCP integrationAny AI tool querying governed data

Two Tracks

Track A: Hybrid Integration

"Govern Without Replacing"

You have existing systems—DeltaV, HighByte, SCADA, historians. This track adds governance on top:

  • Connect to existing data sources via IoT Hub
  • Create surfaces that organize your data
  • Build compliance queries with Azi
  • Get API endpoints without changing infrastructure

Start Hybrid Track →

Track B: Full System

"Author It All"

Starting fresh or want complete control. Build everything with OpenIndustrial:

  • Design your connection architecture from scratch
  • Create a complete surface hierarchy
  • Build a comprehensive warm query library
  • Establish team permissions and workflows

Start Full Track →


Prerequisites

RequirementDetails
OpenIndustrial accountFree tier works for this journey
Azure subscriptionFor IoT Hub connections (Hybrid track)
Data sourcesAt least one: simulator, historian, or sensors
Time~2 hours for Hybrid, ~4 hours for Full
Thinking Tip:

Don't have data sources? Configure a simulator to follow along. The patterns are the same.


Category Metrics

At the end of this journey, you'll measure:

MetricTarget
Time to First Governed Query< 30 minutes
Compliance queries built5+
Audit coverage100% of queries logged
AI integrationAt least 1 MCP-native AI connected

Why This Matters for Compliance

Before Control PlaneAfter Control Plane
"The AI said it was compliant""Here's the query, who approved it, and the audit trail"
Black-box recommendationsTransparent, reviewable logic
Vendor-locked insightsPortable, governed data
Scattered evidenceSingle source of truth

Choose Your Track


What's Next

TrackLink
Start with HybridHybrid Track →
Start with FullFull Track →
See common patternsPatterns →
On this page