Introducing EdgeIQ Fabric - Powering Agentic Orchestration for Connected Operations and Physical AI

EdgeIQ Fabric lets operations teams ask about, act on, and orchestrate workflows across connected product and industrial operations in plain language, grounded in a unified context across the entire value chain.

Every operations team knows the outcome it wants. Fewer devices offline. Faster recovery when a line goes down. A firmware rollout that finishes cleanly across the fleet. Until now, getting there meant translating that outcome into workflows, APIs, and device semantics, then waiting on the few specialists who could do it.

Today we are introducing EdgeIQ Fabric. Fabric makes Symphony agentic, in both the interface and the workflow engine underneath it. Before Fabric, Symphony orchestrated the workflows that experts designed. With Fabric, anyone can state the outcome they want in plain language, and Symphony designs, governs, and runs the workflow that delivers it.

Ask. Act. Orchestrate.

Fabric gives every operations user three capabilities through one plain-language interface.

Ask. Question the entire estate and get answers with full device, connectivity, and process context.

Act. Take a governed action across the fleet and the systems around it. Fabric previews what will run, a person approves it, and it executes.

Orchestrate. Describe an outcome and Symphony builds and runs the workflow that delivers it, across the value chain, from a device signal to a service ticket to a customer record to finance.

In Industrial Operations, a plant operations leader at a tier one automotive supplier types one instruction: when any press line reports a vibration anomaly, open a service ticket with full device context, notify the line supervisor, and schedule an inspection. The workflow is live before the end of her shift.

In Connected Product, a customer operations lead stages a firmware campaign for every unit still running an older version, moves those devices to a high-bandwidth rate plan for the download window, and rolls back any device that fails to check in afterward.

Each starts as a sentence describing an outcome. Each ends as a governed workflow running across devices, networks, data, and applications.

Where the physical meets the digital

Connected Operations is the name for businesses that run in both the physical and the world. It spans two domains. Connected Product, where companies build, deploy, and monetize fleets of smart, connected products. Industrial Operations, where manufacturers and other industries digitally transform their factories, hospitals, job sites, power plants and supply chains.

The intersection of the physical and digital domains is where the opportunity is. Products that keep creating value after they ship. Plants that run on live operational data. And Physical AI, AI that perceives and acts on the physical world, is emerging as a priority across both domains.

It is also where the hardest problems live. The physical and digital domains are two different worlds. They differ in topology, technology, communication protocols, data models, security, and the skills needed to run them. And every layer of the value chain has its own vendors, most of whom manage, automate, and integrate within their own layer. Physical AI makes this harder, not easier. AI that acts on machines, networks, and fleets needs full context and human governance to act safely.

Orchestration, not merely automation or integration

The Connected Operations value chain runs across devices, networks, data, and business applications. Over the years, businesses automated tasks within each of those domains and integrated systems between some of them. Processes still do not run end to end. The missing piece has always been orchestration that works within each domain and across all of them at the same time.

That is a different job from integration. It is not just connecting device management systems to each other. Not just connecting connectivity platforms to each other. Not just connecting either of those to enterprise applications and cloud. It is running workflows within each of those layers, across them, and between all of them. Orchestration is not a pane, a plane, or a layer. It is a fabric woven through the whole of operations.

EdgeIQ built Symphony as the first orchestration platform purpose-built for exactly this problem. Fabric takes it from orchestration that experts build to orchestration that anyone directs.

Unified context

Agentic orchestration cannot work without unified context. Unified context is one normalized view of devices, connectivity, data, and the business systems around them. It lets business applications see and understand the physical world, and lets machines and networks act on business policy and intent.

That is what makes AI effective, because it can reach every domain a workflow touches. Accurate, because its answers draw on one consistent record, not fragments stitched together. And secure, because the same access controls, device security, and secrets management govern every action in every domain, and a person must approve any action that changes the state of a device or system. Without unified context, what you have is not orchestration. It is automation or integration, trapped in silos.

Unified context is hard to build. It took fourteen years of work in one domain: OT and IoT devices, multi-protocol data both structured and unstructured, and multi-network, multi-carrier connectivity with endpoints reaching the platform over many different modes. That is what purpose-built means. In Symphony, unified context comes together through:

• Common data and event models, shared by every device, network, data source, and application the platform touches.

• A common security model, which applies role-based access control, account-level controls, device security, and secrets management to every action and workflow Fabric runs.

• Device abstraction, which normalizes how devices and endpoints are identified and reached, across protocols and networks, without imposing a fixed structure or requiring a proprietary agent on the device.

• A relationship and topology model, which maps how devices, SIMs, sites, fleets, customers, and users connect, so a question about one resolves in the context of all the others.

• A semantic model, which maps the language of the business, such as a press line or a customer account, to the devices, data, and systems behind it.

• The Integration Hub, which reaches outward to the systems a business already runs on, from CRM and ERP to manufacturing execution and field service, through the EdgeIQ API, Model Context Protocol, and secure Bring Your Own Application (BYOA) integration. Every system it connects becomes a system Fabric can ask, act on, and orchestrate against.

• An Operations Historian, which reaches back in time, holding a normalized, long-term record of the estate that workflows and applications draw on. 

Trust by design

Because Fabric acts on physical systems, trust is built into the platform, not bolted on. Fabric is read-only by default. Every action that changes the state of a device, a workflow, or a downstream system is previewed in full and requires explicit human approval. Fabric is generative at design time and deterministic at run time: the AI authors the workflow, a person approves it, and Symphony runs it the same way every time.

From workflows to outcomes

Outcomes are what agentic orchestration makes possible. Not a faster dashboard. Not a smarter chatbot on top of the same silos. Operations teams state the outcome, and Fabric delivers it across the entire value chain, from the physical world to the business systems that depend on it.

"Unless getting a candy bar out of a vending machine is your goal, achieving outcomes is never as easy as pushing a single button. For organizations living at the intersection of the physical and digital worlds, outcomes only come through orchestration. And consolidating platforms in any single domain -  device, connectivity, data, application or security - doesn't deliver outcomes. EdgeIQ replaced the swivel chair with unified context and multi-domain workflows. With Fabric, we're taking it to the next level with agentic orchestration - giving the of power outcomes to operational experts, not just platform experts."

Michael Campbell, CEO