Summary

  • The expanded integration carries programs and supporting documents from Esprit Edge through cloud revision control to the operator's workspace.
  • Controller edits return as engineering change requests, not automatic approved revisions. Recording a change and deciding it is fit for reuse are different jobs.

The next order for a familiar part may arrive long after the people, tooling or machine setup have changed. A local adjustment that helped the previous run can then be either valuable knowledge or an unexplained exception. Saving the file is not enough. Someone must understand why it changed and decide whether that change belongs in the next released program.

That is the most consequential part of the Datanomix-Hexagon integration described in Datanomix's September 9 announcement. The forward route brings an NC program and its supporting documents into controlled delivery. The return route brings edits made at the machine back to engineering as change requests. A programmer, rather than the mere existence of a newer file, determines the next approved revision.

The return journey matters

The current integration page describes programmers working in Esprit Edge, uploading the program, print, setup sheet and tooling documents to Hexagon Cloud, and having G-Code Cloud + DNC version and organise the material by part number. After approval, a Digital Production Bundle appears at the operator's Machine HUD, the workspace used for production monitoring. Edits at the controller are recorded against the delivered program and returned for engineering consideration.

The distinction between a delivered version and a proposed change is commercially useful. It can preserve what the floor learned without silently making every local adjustment the standard. A repeat job may use different tooling or equipment. A change request supplies something to investigate; it does not establish that the same adjustment should be applied again.

This is a proposed operating benefit, not a measured customer result. The sources reviewed do not quantify fewer scrapped parts, shorter setups or faster engineering decisions. Nor do they establish the complete range of supported controllers, offline behaviour or a standard deployment price. Those details affect how much of a shop's real program movement the connection can cover.

A bundle is more than a file—and less than a validation

Keeping a print, setup information and program together may reduce the chance of teams assembling incompatible instructions from separate folders. It does not prove that the documents are correct or that the physical setup matches them. Revision control answers which record was released; it does not, by itself, answer whether the resulting part meets its requirements.

Datanomix's August 24 scanner description helps define another boundary. It describes finding missing header information, examining naming patterns, auditing fields and checking programs against a selected machine's expectations. Examples include author, revision, tooling and target times. These checks can expose gaps in the program library. A populated field, however, is not proof that its contents are accurate.

That scanner post places insertion of missing fields on its roadmap. This article does not treat that planned remediation as a confirmed current capability. Similarly, the integration's language about regulated work is a vendor representation, not independent evidence that buying the software certifies a manufacturer or validates a machining process.

The partnership itself is not new. A January 2023 announcement established the production-monitoring relationship and plans for further integration. The new commercial proposition is a more connected path between programming and production, not the invention of that channel.

The practical test is whether returned changes receive timely decisions and whether accepted knowledge reaches later released bundles. An immaculate version history with an ignored review queue would preserve evidence without making it useful. Conversely, a well-handled exception can stop the next team from having to rediscover the last team's solution.