Operational data foundation
Connects operational, enterprise, event, document, and application context into an agent-ready operating foundation.
XMPro provides the industrial operating layer for AI agents, applications, recommendations, workflows, and governed autonomous operations. This reference architecture shows how that operating layer connects operational data, enterprise context, applications, agents, governance, and decision accountability into one deployable architecture.
The XMPro Agentic Operations Platform sits between operational systems and operational action. It connects data sources, contextualises the operation, governs decisions, and serves both human applications and MAGS-powered agents from the same operating foundation.
XMPro connects operational systems, Data Stream Designer, Operational Context Engine, AI Workflow Harness, MAGS, AppDesigner, XMPro FRS, Action Agents, human review, and Decision Trace into one governed decision architecture.
Historians, DCS, SCADA, CMMS, ERP, engineering systems, alarms, work orders, models, and external data remain source systems. XMPro sits above and across these systems to create governed decision flow.
Observes, normalises, enriches, and prepares operational signals so they are fit for applications, context, models, workflows, advisors, and decision loops.
Turns operational data into trusted semantic context and an open, governed ontology. OIM sits inside OCE as the identity and ontology model. Connects identity, semantics, relationships, constraints, source priority, and lineage.
Governs model reasoning inside visible Data Stream workflows: context assembly, classification, summarisation, enrichment, structured outputs, approved tool access, validation, routing, observability, and governance.
Powers AI Assistants, AI Advisors, and Cognitive Decision Teams through governed Cognitive Decision Loops. Uses trusted context to support observation, reflection, planning, coordination, approval, action intent, and Decision Trace.
AppDesigner delivers dashboards, workflows, operational applications, and role-based experiences. XMPro FRS front-runs scenarios, what-if branches, constraints, and proposed action intent before production action. Action Agents execute only through configured pathways. Human review and approval remain part of the architecture where risk demands it.
Preserves the evidence of what was observed, what context was used, which objectives and constraints applied, what recommendation or action was produced, who approved, simulated, escalated, or executed it, and what outcome followed.
Reasoning models improve inference. XMPro provides the operational context, governed workflows, front-running simulation, decision architecture, bounded action, and evidence layer required for industrial operations.
Foundation
Connects operational, enterprise, event, document, and application context into an agent-ready operating foundation.
Operational Knowledge Graph models assets, sensors, processes, relationships, policies, enterprise context, identity, trust, and provenance.
Application
Supports operational applications, recommendations, workflows, approvals, and decision review experiences.
Gives MAGS-powered agents governed access to operational context, recommendations, and decision pathways.
Governance
Evaluates actions through risk, safety locks, source confidence, policies, approvals, evidence packs, and audit records.
Decision Trace records what was recommended or done, why, what evidence was used, who or what approved it, and what outcome followed.
Reach
Designed for brownfield industrial systems, edge/local patterns, enterprise integration, and cross-site scaling.
Uses open semantic, validation, query, provenance, and industrial standards where appropriate to avoid trapping operational knowledge in a closed model.
XMPro is not only an application layer on top of someone else’s operating model. It provides the operating model, context layer, application layer, agent layer, governance layer, and decision accountability layer required for agentic operations.
CORE OPERATING MODEL
The platform is organised around a simple operating loop. The same five steps run whether a human, an agent, or a policy-controlled action does the work.
The architecture is grounded in action, not just data readiness. It exists to help industrial organisations operate better — not to build a more elegant data model.
Eight stops between observation and recorded outcome.
Agent or application receives operational context.
Asset, process, identity, and enterprise context resolved.
A recommendation or action is proposed.
Risk, policy, source confidence, safety locks, approvals checked.
Outcomes and feedback improve future recommendations and operating context.
Decision Trace captures what happened, why, who approved, and what evidence supports it.
The approved action is executed or handed off.
Decision routes to a human, workflow, agent team, or policy execution path.
CONTROL MODES
Agents recommend. A human decides, plans, and acts.
Agents prepare and coordinate. A human approves execution.
Agents execute within governed policy limits and escalate exceptions.
XMPro is designed for brownfield industrial environments where critical context is spread across many systems.
XMPro doesn’t require every system to become the system of record. It creates an operating foundation that can connect, contextualise, govern, and act across the systems customers already run.
Governance is part of the architecture — not a bolt-on control layer.
The platform earns the right to support autonomy by making decisions governable, explainable, and reviewable.
Four supported patterns. Pick against connectivity, sovereignty, latency, and governance — deeper detail on the dedicated page.
Enterprise-scale analytics, governance, application access, and centralised coordination.
Site-local context, constrained connectivity, low-latency needs, operational continuity.
Central governance with site-level execution.
Regulated, air-gapped, or sovereignty-sensitive environments.
Open standards for semantic modelling, validation, query, provenance, industrial taxonomies, and AI access — so operational knowledge doesn’t become a proprietary dead end.
Web Ontology Language — semantic modelling.
Validation rules for the operating model.
Cross-domain query across the knowledge graph.
Provenance and decision lineage.
Model Context Protocol — agent-accessible context.
Industrial reliability and maintenance taxonomy.
Enterprise–control system integration model.
Industrial automation interoperability.
Starting points for technical evaluation. Need a downloadable architecture brief, a decision-replay walkthrough, or a worked cross-domain query? Talk to a solution architect.
Technical reference for installation, deployment, configuration, and component behaviour.
OpenXMPro’s public repository for generative AI agents and Multi-Agents — the agent layer in code.
OpenReference implementations and architecture patterns your team can read, adapt, and reuse.
OpenKubernetes deployment artefacts — concrete starting point for k8s evaluators and platform teams.
OpenReal industry asset modelling — Wind Power Plant & Wind Turbine DTDL models you can inspect.
Open