Where ACORiX is headed
Reporting is the beginning, not the ceiling.
ACORiX started as the reporting and intelligence layer for DELMIAworks. The same foundation is built to carry finance from the report to the close, and to reach across manufacturing ERPs over time. What follows is direction, shared honestly, not a set of dated promises.
Two axes
More modules. More ERPs. One foundation.
ACORiX grows in two directions at once. Down one axis, more modules on the same foundation. Down the other, more ERPs, each native-first. Both build on the setup you do once.
Now
Reporting for DELMIAworks
Visual report authoring, free organization-wide viewing, native drill-down, access that matches how DELMIAworks is structured, and clean Excel with live sync. Migration from Spreadsheet Server and Crystal Reports. Live today.
Next — more modules
From the report to the close
Financial analysis and business intelligence (multi-dimensional GL). Job costing. Close automation. FP&A on the same foundation. Agentic analysis and workflow triggers on top of your live data, so the numbers do not just display, they work.
Later — more ERPs
Across manufacturing ERPs
Additional manufacturing ERPs, one at a time, native-first, each with deep integration rather than a thin generic connector. DELMIAworks is the beachhead. Others, including Epicor, are under active exploration.
How we build
Nothing moves to Now until it is earned.
Earned is not a figure of speech here. It is a specific test, and it is the same test for every module and every ERP on this page.
Earned means proven on real closes, not demos.
A module is only called available after finance teams have run it on their own live ERP data through three consecutive month-end closes, and the numbers have tied out against the close they already trust. Until that has happened it stays under Next, however finished it looks in a demo.
Depth in one ERP before breadth across many.
We finish an ERP to the depth of its own data model before we open the next one. For DELMIAworks that means the two-level EPlant structure, per-plant fiscal calendars, and the IQMS schema underneath them. A connector that reads your tables without understanding any of that is not an integration, and we would rather support one ERP properly than five superficially.
Each module has to fund the next.
We build what customers on the current module ask for next, in the order they ask for it, instead of committing to a feature list written a year ahead. That is why this page publishes direction and sequence, and deliberately publishes no release dates.