Datanomix, ProShop ERP Partner to Deliver Automated Job Costing, More

Datanomix, a provider of its Automated Production Intelligence platform, and ProShop ERP, a supplier of digital manufacturing-management systems, have announced a partnership to help manufacturers deliver more insights from their operational data. The first of many new features, they say, delivers automated job-costing analytics that compare ProShop target takt times for part production to actual part performance at the machine, via Datanomix. The ability to compare targets to actuals and benchmarks offers clarity on gross-margin performance on a per-part basis relative to operations, while highlighting where the greatest opportunities for margin improvement exist.

A ProShop ERP integration is now available inside the Datanomix platform. By enabling this integration, Datanomix automatically matches part numbers in the machine code to those from ProShop ERP and extracts target takt times. These targets are integrated into the Datanomix Quote Calibration Report to quickly identify opportunities for margin improvement by comparing the ProShop target takt times to Datanomix actuals and benchmarks. Pre-packaged filters in the report show exactly which jobs to work on.

“ProShop ERP is built to store and manage the data that’s vital to running a factory, helping manufacturers make better decisions for their front office and shop floor,” says Paul Van Metre, co-founder and CEO of ProShop ERP. “By partnering with Datanomix, we’re closing a loop that lets our customers tie true costs back into our existing job costing and profitability workflows by refining the exact machine utilization times to augment current labor, out-of-pocket costs and overhead costs.”

“Knowing how much it really costs to produce parts is the holy grail for precision manufacturers when it comes to job costing and quoting,” adds Greg McHale, CTO and co-founder of Datanomix. “With Datanomix, manufacturers get operations data directly from CNC machines, offering an incorruptible window into actual job performance derived while running parts because there is no operator input required.”