FOR THE QUESTION EVERYONE KEEPS ASKING
Ask once. Serve everywhere.
A warm query is a saved question over live data, like "OEE (overall equipment effectiveness) by line for the last shift". Save it once and the answer is ready for a dashboard, an app or an AI.
New to OpenX? Key terms →
ONE SAVED QUERY
- Steps
- Azure Data Explorer and Cosmos DB, one feeding the next
- Parameters
- Line, site, time window
- API route
- Its own path, under your access rules
- Export
- CSV from the editor
- MCP
- Your AI drafts it, checks it and reads it
Save a query. Get an API.
FROM QUESTION TO ENDPOINT
Live answers for people, apps and AI.
Built as steps
The Steps editor runs KQL against Azure Data Explorer or reads a Cosmos DB container you pick from a list.
One store feeding the next
A later step can filter by keys an earlier step read, like Data Explorer sensor data filtered by lot keys from Cosmos.
Parameters
One query becomes many: by line, by site, by time window.
A saved query is an API
Once saved, it gets its own path in the API Manager's Warm Queries tab, under the same access rules as everything else.
Take the data with you
Download any result as a CSV straight from the query editor.
AI builds and reads them
An AI drafts, checks and samples queries through the OpenX MCP Server, then reads the saved query's route like any other caller.
IF EVERY NEW KPI IS A TICKET
For teams tired of rebuilding the same query.
Operations and engineering leads
Get the number you need without waiting on a data team for every new KPI.
Data teams
Write the query once instead of again as a tile, an API, a report and a notebook.
App builders
A governed, parameterised endpoint over plant or lab data, with no service to write.
NEXT TO YOUR DATA TOOLS
A layer over Azure Data Explorer, not a replacement for it.
Saved queries as endpoints, querying several stores and MCP access all exist in good tools today. OpenX puts them in one object, in your own Azure.
- One saved query is an API route, a CSV export and something an AI reads, all at once.
- Cosmos DB and Data Explorer in one editor, with one step's keys filtering the next.
- It inherits access rights and the AI-proposal review from the rest of OpenX.
WHERE THE ANSWER GOES NEXT
One query, many places to land.
Lots and sensors in one answer
- 01Batch lots live in a Cosmos DB container.
- 02Sensor readings live in Data Explorer.
- 03A Data Explorer step filters by the lot keys a Cosmos step read, and one route serves the answer.
Query to app
- 01An OEE warm query runs over live line data.
- 02Its route appears in the API Manager.
- 03A supervisor app reads it with its own access.
AI as analyst
- 01An assistant drafts a query over MCP and checks it.
- 02A person saves it.
- 03It is a route every caller allowed to read it can call.
THE QUESTIONS TEAMS START WITH
Patterns you can start from.
The docs carry a query pattern library: time-series aggregation, thresholds, OEE, downtime Pareto, batch traceability and energy cost.
MANUFACTURING
OEE, downtime Pareto and device comparison across lines.
LIFE SCIENCES
Batch traceability, and excursion thresholds for cleanrooms.
ENERGY AND BUILDINGS
Energy cost and cost allocation across meters and sites.
Save the question. Serve the answer.
Live data, queried on demand, ready for every dashboard, app and AI you allow.
GO DEEPER
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.
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.