Competitor teardown, Celesnity product, 27 Jul 2026

SymphonyAI Industrial: one plant context, many products on top

SymphonyAI connects plant data into a governed model of assets, types and relations. Graph analytics, ML models, agent flows, generated apps and a Copilot all reuse that model. It is the broadest platform in this set and the hardest to learn.

Founded
2017
Romesh Wadhwani, $1B commitment
Team
~2,500
Company figure, Mar 2025
Revenue
~$500M
Run rate, secondary source, unverified
Portfolio
5 verticals
Industrial, retail, financial services, enterprise IT, media
Pricing
Not public
Enterprise sale on Microsoft Azure
What matters for Minder
  • The asset is the shared context: canonical types, mappings and a knowledge graph. Apps, models, flows and Copilot are outputs that inherit it.
  • People approve every step that touches operations. P&ID entities are verified one by one, types are published from draft, models need an explicit deploy, generated apps show code and diff before release.
  • The CIP runtime (flow, current step, measurement, alert queue with an owner) is the closest benchmark for our Produce loop. Recommendations stop short of approval, execution and outcome, which is where Minder can go further.

Product shape

Five product areas on one context layer. The official demo walks them in this order.

SourcesOPC UA/DA, Modbus, MQTT, OSIsoft, Aspen IP.21, InfluxDB, Kafka, Azure IoT Hub, ODBC, CMMS, P&ID drawings
→
FoundryConnectors, namespaces, canonical types, source-to-type mapping, P&ID extraction with human verification
→
Cortex, ML, Flows, ForgeKnowledge graph and impact analysis; model training and deploy gate; agent workflows; prompt-to-app
→
OperateGenerated role apps, alert queue with owner, Copilot drawer with "Show AI's work"

Screens are 33 frames from the 30 Jan 2026 official demo, with sample data. A generated app is an example output, not a fixed SymphonyAI module.

symphonyai.com/industrial/iris-foundry

Foundation: connect, verify, standardise

Raw sources become a published, reusable model before any app runs on them.

Connector catalog

Connector catalog

  • Card per source: OPC UA/DA, Modbus, ODBC, Aspen InfoPlus.21, InfluxDB, Kafka, Azure IoT Hub, Kinesis, MQTT, OSIsoft, SFTP.
  • Namespaces keep each source's own asset hierarchy, down to condenser, turbine and KPI.
P&ID verification workbench

P&ID to verified plant context

  • Upload a drawing, pick an extraction model, watch each page move through Analyzing.
  • Workbench: entity list with category and confidence filters, detections drawn on the drawing, a count such as 61 / 62 verified.
  • A person confirms every entity before it reaches the asset model.
Minder: the queue plus confidence plus human check is the pattern for any AI extraction that feeds operations, including our plant model from documents.
Type properties and publish gate

Canonical types

Types such as MaintenanceWorkOrder, QCReport and OperatorLog carry mandatory fields and live as Draft until someone presses Publish.

Source-to-canonical field mapping

Four sites, one type

A mapping canvas joins the schemas of four plants to one canonical type. Powerful, but the crossing lines give no focus on conflicts or unmapped fields.

symphonyai.com/industrial/knowledge-graph

Diagnose: from a moved KPI to a cause

The graph supplies relations; impact analysis turns a marked time window into ranked causal paths.

Impact analysis critical paths

Impact analysis

  • Mark up to seven days on a KPI such as Net Power Export, then compare three critical paths.
  • Each path shows its contribution, likely causes and recommendations.
  • The flow ends at a recommendation. No approval, owner or outcome check appears.
Minder: keep the same thread going: proposed action, approval, execution, verified outcome.
Knowledge graph explorer

Knowledge graph

Enterprise, region, plant and unit as nodes. The side panel holds documents, trend, alerts, similar and connected assets. Copilot sits in the corner.

ML run evaluation and deployment gate

Model deploy gate

Anomaly trend with alert markers next to Retrain, Retest and Use in Deployment. Evidence sits beside the decision to promote.

symphonyai.com/industrial/iris-forge

Build: agent flows and generated apps

Flows orchestrates reasoning, tools and people. Forge writes editable application code.

KPI RCA flow template

IRIS Flows

A KPI root-cause template runs from inputs through LLM, tool and code nodes to a PDF and an email. Resources (APIs, datasets, Trino, LLMs) are bound per node.

Forge generated app workbench

IRIS Forge

"Build an app to monitor asset health" yields a project with Code, Diff, Preview, terminal and a Deploy button. Output is software you can inspect.

Minder: keep agent graphs apart from the production graph. For apps, generate bounded operator and manager views from the plant schema first; a full Forge can wait.
symphonyai.com/resources/blog/industrial/sip-cip-iris-foundry

Operate: generated role apps

The demo shows apps for a beverage CIP line, HVAC service and power generation.

SIP/CIP runtime step monitor

CIP runtime

  • Current step, 10 of 27 steps done, 3 warnings, live metrics.
  • Step chain with a Completed, In Progress, Warning, Error, Pending legend. Pick a step for expected vs actual duration and live flow, temperature and conductivity against targets.
Minder: the clearest flow-first runtime in the set. Copy flow overview, current step, measurement, issue queue.
Alert work queue

Alert queue

Open, In process, History. Each alert shows location, affected systems, impact, recommended actions and event history, with Assign and Start.

Merit-order recommendations

Merit-order recommendations

Current vs optimal load and cost impact per unit, with an action such as "Increase load". No approve, owner or result.

Copilot active-alert summary

Copilot in context

  • A drawer over the current screen answers "summary of active alerts" with a table by severity and a written summary.
  • Show AI's work, feedback, regenerate, export to PDF.
Minder: answers should land as decision packets on real objects, with typed actions, rather than a separate chat space.

Analysis

Fact = from SymphonyAI's site, demo or press. View = our assessment.

Platform Fact

  • IRIS Foundry is an industrial DataOps platform on Azure that feeds Microsoft Fabric.
  • Areas: Foundry, P&ID ingestion, Cortex knowledge graph, ML Studio, IRIS Flows, IRIS Forge, Workspace, Connected Worker, Copilot.
  • Clear lifecycle states: Draft and Published types, model runs promoted to deployment, apps deployed through a pipeline.

AI Fact

  • Model registry holds anomaly, causal, mapping and Azure OpenAI models.
  • Vision extraction on P&IDs, LLM agent nodes in Flows, code generation in Forge, Copilot over current context.
  • Novelis began with rule alerts and added ML alerts over 32 plants to build trust (vendor-reported).

Moat View

  • Real: breadth of connectors and governed context; one stack from data to generated apps; big-company credibility and capital.
  • Thin: home page follows product taxonomy instead of the job; dense dashboards with repeated filters; UI differs across modules and generations.

Gaps View

  • Recommendations never show approval, execution or verified outcome.
  • Error, permission, stale-data and rollback states are mostly missing from public screens.
  • "Unverified" is styled green, which reads as safe.

Market Fact

  • Industrial cases named: GSK (connected worker), Vandemoortele (paperless shifts), Novelis (predictive maintenance), Nippon Gases (asset intelligence). Results are vendor-reported.
  • Demo domains: power generation, beverage CIP, HVAC service, refining.

For Minder View

  • Build now: versioned workflow and field definitions; step runtime; flow and table views of one event log; issue queue with owner and age; decision packet with approval and outcome.
  • Later: connector studio, generic agent resource manager, prompt-to-code apps, ML registry UI, enterprise dashboards.

SymphonyAI vs Minder

Where the two products start, and where they meet.

SymphonyAIMinder
Starting pointExisting OT and IT systems, drawings, CMMSFirst-party event capture from workers and signals; legacy systems as adapters
Primary userData and OT engineers, reliability engineers, executivesFrontline workers and managers on one event log
Context modelNamespaces, canonical types, knowledge graphPlant model and operational graph
AI stackGraph analytics, ML Studio, agent flows, code generation, CopilotAgent loop over the operational graph via read-only Trino, cited answers
AutonomyRecommend; human approval stated in Flows, not shown in appsRead-only and advisory in production; humans approve consequential actions
Time to first valuePlatform build-out before appsFirst app live in month 1; Kasa live in six weeks
GeographyGlobal, multi-verticalVietnam proving ground, Europe next

Sources

Full research: UI deep dive, 33 frames, 11 flows and SymphonyAI × Ethon screen atlas, 304 fragments. Revenue and headcount come from secondary sources and vary by date. Case outcomes are vendor-reported.