FOR PLANTS THAT ALREADY HAVE THE DATA
Keep the tools you run. Put their data to work.
Your historians, edge gateways and brokers already collect the data. OpenX takes it in through IoT Hub and API connections, into your own Azure, and turns it into saved queries, APIs, apps and answers your AI can read.
New to OpenX? Key terms →
FROM THE PLANT FLOOR · TO THE ANSWER
- Devices
- Into Azure IoT Hub, in your subscription
- Data
- Into Azure Data Explorer, queried on demand
- Questions
- OEE, downtime, thresholds, as saved queries
- Answers
- API routes for MES dashboards and apps
- AI
- Reads the same answers over MCP
Your plant data, in your Azure, ready for AI.
WHAT CHANGES ONCE THE DATA IS IN
From stranded data to answers your team uses.
A data backbone in your Azure
IoT Hub and Data Explorer, set up in your own subscription from one window.
The questions you keep asking
OEE by line, a downtime Pareto, threshold checks: saved once as warm queries, with parameters for line, site and shift.
Answers as APIs
Each saved query is an API route your MES dashboards, Power BI and apps can call, under your access rules.
Apps on top
Inspection results and work orders in a Cosmos DB store, next to the machine data they describe.
AI that proposes, people who decide
An AI connected over MCP drafts queries and changes. A person accepts them and deploys.
Change on your schedule
Stage cloud changes during the week and deploy at a shift change. Removals wait until you deploy.
IF THE HISTORIAN IS WHERE DATA GOES TO STAY
For teams who want more from the data they already have.
Plant and OT/IT leads
Data out of the historian and into your own cloud, not a vendor's.
Operations and engineering
The KPI you need as a saved query, without waiting on a data team.
Equipment makers and integrators
Connect devices for a pilot, serve the data as an API, and sell it per site.
NEXT TO THE TOOLS ON YOUR FLOOR
Your plumbing stays. OpenX is where its data goes next.
Edge gateways, brokers and DataOps tools move and model plant data well, and OpenX works alongside them. It is cloud-side, with no edge runtime of its own: it is where the data becomes queries, APIs and AI-built apps.
- Device data feeds warm queries, databases, API routes and the MCP server in one workspace.
- AI changes wait for a person, and changes to your cloud wait for Deploy.
- Your data stays in your own Azure.
ON THE LINE
From a sensor to a shift report.
Device to dashboard to AI
- 01Press-line sensors stream into IoT Hub.
- 02A warm query computes OEE, and the API Manager serves it to the MES.
- 03An AI reads the same answer over MCP.
A pipeline from one sentence
- 01"Add the press-line sensors, a 5-minute OEE query and an API route for the MES."
- 02The AI proposes the connection, the query and the route.
- 03A person reviews, accepts and deploys.
Sell the monitoring
- 01Device data is served through API routes.
- 02Licenses sells a monitoring plan per customer site.
- 03The plan's rights open those routes.
WHERE IT RUNS
Plants, sites and buildings.
MANUFACTURING
SCADA, MES and historian data in one workspace, for OEE and downtime.
ENERGY AND UTILITIES
Meter and site data under your own cloud policies, for cost allocation.
BUILDINGS
Building systems and utility feeds, served to billing and maintenance apps.
Your data is already there. Put it to work.
Start with a simulator, connect a line, and serve the first answer.
MORE OF OPENX
AI governance →
Over MCP, AI proposes and a person accepts. Only a person deploys.
OpenX MCP Server →
A few tools let any MCP-capable AI read your workspace and propose changes to it.
API Manager →
Your workspace is already an API. Decide who may call it and what each caller reaches.
Warm queries →
Save a question over live data and serve the answer to dashboards, apps and AI.
Provenance →
A record you can prove, kept in your own cloud, with corrections and signatures.
Your cloud →
Connect your Azure, build the landing zone, and the rest of OpenX runs inside it.
Databases →
A Cosmos DB store in your subscription, with a governed API for each container.
App Identity →
Your own sign-in directory, identities for your jobs, and access in one window.
Licenses →
Sell what you build on your own Stripe, and turn a subscription into a plan's rights.
IoT →
IoT Hub and Data Explorer in your Azure, feeding queries, APIs and AI.
Communications →
Send mail through your own relay, with the password in your vault and sends on record.
App building →
Data, sign-in, access, an API and billing: your app's backend, already there.