A programmer finishes a setup, the toolpath is proven, the print is attached, the setup sheet is written, and the NC program is generated. Then the files often move through a network drive, an email, or a USB stick, and nobody can say for certain which revision is running on the machine or who touched it last.
Datanomix and Hexagon, already partners in advancing Manufacturing Intelligence, have expanded their collaboration with a new connection between Hexagon’s Cloud and Datanomix G-Code Cloud + DNC. Programmers continue to work in Esprit Edge before uploading the NC program and its supporting documents to Hexagon Cloud. From there, revision control, Digital Production Bundle assembly, and controlled delivery to the machine are automated.
“Every shop has the same gap, and it’s right where programming ends, and production begins,” said Greg McHale, Founder and CEO of Datanomix. “Programming and the machine should not be two different systems of record, with people guessing whether the right program is running, the right setup sheets were used, or where the right version of these artifacts even lives. Datanomix and Hexagon built a connection that carries revision control and the full production package from print to post to part and brings what happened at the control back to the programmer who owns it.”
Also Read: Telxius Boosts Global Network Capacity and Efficiency with Nokia 800G Coherent Pluggable Deployment
How it works
1. Program the part in Esprit Edge, as usual
2. Upload the NC program, print, setup sheet, and tooling docs to Hexagon’s Cloud
3. Datanomix G-Code Cloud + DNC versions everything and files it by part number
4. Once approved, the package lands at the operator’s Machine HUD as one Digital Production Bundle the same workspace they already use for production monitoring
5. Edits at the control come back to engineering as change requests, so the programmer decides what makes it into the next approved revision
Automated delivery from cloud to shop floor. Engineering approves the revision, and it syncs to G-Code Cloud + DNC and lands on the floor. Nothing reaches a machine that wasn’t released. No walking out to find out what’s running, or who changed it last.
A visible feedback loop to engineering. Edits made at the control are recorded against the delivered program and returned to the programmer. What changed at the machine becomes part of the record instead of getting rediscovered on the next run or worse, never discovered at all.
Zoltan Tomoga, Product Manager at Hexagon’s Production Software Division, explained: “Recurring work may return months or years later, after machines, tooling and personnel have changed. Returning controller edits to engineering as change requests helps programmers understand what was learned during the previous production run, decide what remains relevant, and incorporate the right changes into the next approved version.”
Built for regulated work
For shops running medical, defense, and aerospace programs, NC code is a controlled asset. Traceability and protection aren’t optional: encryption, version control, role-based access, a complete audit trail. Once uploaded, programs authored in Esprit Edge are managed in a platform built for CMMC 2.0, where every change is logged with who, what, when, and why.