DELMIAworks
Connect AI agents and workflows to DELMIAworks (IQMS): items, sales orders, work orders, inventory, shipments and production, behind your firewall.
Book a demo
DELMIAworks for AI agents and workflows.
engini lets your AI agents and workflows work in DELMIAworks, the manufacturing ERP from Dassault Systemes formerly known as IQMS EnterpriseIQ, used by plastics, metal and medical manufacturers: read items, inventory and sales orders, read work orders and real-time production, read shipments and invoices, enter sales orders and customers, and start a workflow when records change. DELMIAworks stays on your servers, and the On-Prem Agent connects it out to engini with no inbound ports. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
What your agent can do in DELMIAworks. Every tool is one you allow or leave out.
The DELMIAworks tools in engini, grouped by what they change. On a plant system a write moves material and money, so write tools go only to the agents that need them.
Read
Read items and stock by location.
Read orders, releases and what shipped.
Read jobs and what each work center produced.
Read billing.
Read any DELMIAworks table with a SQL query. Read only.
Write
Enter an order with its releases.
Keep customers current.
Triggers
Sales orders, work orders or shipments added or changed.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to DELMIAworks. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your DELMIAworks connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of DELMIAworks tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects DELMIAworks and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every DELMIAworks tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to DELMIAworks through engini
{
"mcpServers": {
"engini-delmiaworks": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your DELMIAworks connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the DELMIAworks tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on DELMIAworks. Agents and workflows, across systems.
Releases from EDI and portals
Releases from EDI or a customer portal become DELMIAworks sales orders, and changes reach the planner in Teams.
Plant data in the ERP
Shipments and invoices flow to NetSuite or Sage Intacct when finance runs elsewhere.
Downtime people hear about
When a work center goes down, maintenance gets a ServiceNow work order and a Slack message.
Answers from the floor
An agent answers production, stock and release questions. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between DELMIAworks and another system engini connects is available.
You decide what each agent may do in DELMIAworks. engini enforces it on every call.
Only the tools you allow
A toolset lists the DELMIAworks tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own DELMIAworks account and engini acts as that person, with their DELMIAworks permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
DELMIAworks behind your firewall.
If DELMIAworks runs in your own data center, install the engini On-Prem Agent on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to DELMIAworks while it runs a task. You open no inbound ports or firewall rules. Calls through it run on the same engine as MCP, the API and workflows, and each one is recorded in History.
On-Prem Agent guide →Connect DELMIAworks in three steps. Then decide what each agent may do.
Sign in to DELMIAworks
Install the engini On-Prem Agent on a server that can reach DELMIAworks, create a database user with read access and a DELMIAworks user for writes, then add a DELMIAworks connection.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in DELMIAworks from Claude, ChatGPT, Cursor or your own code.
DELMIAworks and engini. Straight answers.
Can an AI agent write to DELMIAworks, or only read?
Both. engini has tools to enter sales orders and keep customers current. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
What if the tool I need is not listed?
Run Query reads any DELMIAworks table, and new tools can be added for the areas you use. Talk to us about what you need.
Does the agent act as me in DELMIAworks?
It reads as the database user and writes as the DELMIAworks user behind the connection. Every run is recorded under the person who started it.
Can a change in DELMIAworks start work?
Yes. Scheduled triggers check DELMIAworks for new or changed sales orders, work orders and shipments. A workflow can include an AI agent step.