091 220 06 29Call Write to us Menu

Il software che sa ascoltare

It knows how long every machine runs. Even the iron from '95.

For owners and shop-floor managers

There's a CHF 300,000 machine on your floor that works every day and tells no one anything. ERGANE makes it talk — together with all the others, on your own workshop server.

Technical drawing: a manual lathe, a 1990s mill, a five-axis machining centre and a CNC lathe, all connected by network cable to a switch and from there to the workshop server.
Old machines and new ones, different makes, on the network you already have. No sensors, nothing to mount on the machine.

The machines talk. The programs come back.

Shop-floor software for CNC machine shopsOld and new machines, different makes · on-premise

The connection for the machines you already have.

Not an MES, not an ERP. The answer everyone gives you is to buy a new machine: we give a voice to the one that's already there. The owner stops running the shop from memory.

The shop floor, live. Not from memory.

ERGANE speaks each control's native language — whatever the make, old or new — and reads what the machine already knows about itself. No hardware to fit.

ERGANE Live Status header: the machine has been running since 15:12, for 69 minutes; before that it was stopped. Read from the control at 16:20:33. No active alarm.
The line the shop foreman looks at first: the state, said once, how long it has lasted and when it was read. Alarms underneath.
5-axis centrecontrol from 2019 Running O2041 28 / 40 4200rpm
Milling machinecontrol from 1995 Running O0817 9 / 60 1800rpm
Lathecontrol from 2007 Stopped O3310 18 / 25 0rpm
Vertical centrecontrol from 2021 Not answering — — 0rpm
Read from the control, live Example. The machines and programs are fictional.
Technical drawing: the pendant of a 1990s CNC control — small screen, keypad, emergency stop — with a cable plugged in at the back that puts it on the network.
The '95 control doesn't get replaced. If it has a network port, it just gets connected; if it only has the serial port, we supply the converter.

How many hours it really ran

Time in cut, downtime, alarms, parts made. Per day, per week, per machine — the 1990s ones included.

Loads, feed, spindle

The numbers the control already holds, read live and kept over time. And while it cuts, how much load that program usually puts on the spindle, measured on the runs before: a measurement, not an alarm.

Mixed fleet, one screen

The iron from '95 and the brand-new centre on the same page, every machine in its place. Even a Heidenhain TNC 640 tells you whether it's cutting, without buying extra control options. That's the thing the machine builder's portal won't do.

What it doesn't know, it says

Every figure carries the time it was read. If a machine doesn't answer, or the control doesn't give a value, the screen says "not read": never a zero to fill the gap, never a guessed "running".

A control that isn't on the list?

That's not a no. We look at what's fitted, check whether it can be read — and if it can, we integrate it: you don't pay for the whole development, because that control then stays in the product.

The last 2 hours in Live Status: the state strip — running, a short pause, a stopped stretch — and below it the spindle load curve, with the band showing the usual load for program O2041: 57–63%.
The last two hours: states and spindle load on the same time axis, and the band showing how much load that program usually puts on the spindle. App screen, sample data.

Why nothing needs fitting on the machine. The control already has a way to talk — the network port, or the serial one. Nobody ever asked it: ERGANE asks. Where there's only serial, we bring the converter. Connecting is an hour's work, with no sensors and no boxes: we hook up to the control while the floor carries on as usual.

Send the program. And the program comes back.

The moment a CHF 4,000 part gets scrapped is almost always the same one: the wrong version ended up on the machine. ERGANE closes the loop.

Technical drawing: the program goes from the computer to the machine control and comes back; the two copies are compared line by line.
After sending, ERGANE reads the program back from the control and compares it, line by line, with what it sent. If one line doesn't match, you know before the cycle starts.
Technical drawing: on the left scattered copies of the same program, crossed out; on the right a single document with the version strip along its side.
One file per program. The history lives inside the file: no more copies with different names to compare by hand.

Every version, archived

Who changed what, and what changed between yesterday and today. Two versions compare line by line.

CNC memory and network folders, one list

The machine's programs and the ones on the server in the same tree, like in File Explorer: search inside the text too, copy, rename. They go to the CNC with no USB sticks, and you can browse the server even with the machine switched off.

NC Programs in ERGANE: in the same tree, the CNC memory of a Doosan DNM 5700 and its network folder, with the subfolders Archivio, Flange, Piastre and Supporti; on the right the six programs in the Supporti folder, with comment, size and date modified.
CNC memory and network folders in the same tree, like in File Explorer. App screen, sample data.
Version compare in ERGANE: identical lines in grey, with one removed, one changed and one added line highlighted.
Line by line: removed, changed, added. Identical lines stay grey, so what changed shows up at first glance.

The compare is byte for byte. Not "looks the same": it is the same, or ERGANE says so.

The NC editor. You correct, you don't rewrite.

On the shop floor, a program doesn't get rewritten: it gets corrected. Across 439 real edits, the typical one touches 15 lines out of 2,000 — the tool, the offset, the depth, the feed, the speed. ERGANE's editor puts exactly those up front, with a preview and a count before it touches the text.

ERGANE's NC editor on program O1502 SUPPORTO LATO B of a Doosan DNM 5700, opened from the network folder: at the top the Correggi, Guarda, Riscrivi and Macchina tabs with commands for tool, offset, depth, feed and speed; in the middle the program; on the right three saved versions, each with date, origin and note; at the bottom the file's dialect, encoding and line endings.
The tabbed bar — Correggi, Guarda, Riscrivi, Macchina: correct, view, rewrite, machine — and under Correggi the big commands for tool, offset, depth, feed and speed. On the right the versions, each with its note; at the bottom, how the file is built: dialect, encoding, line endings. App screen, sample data.

Finger-friendly, gloves included

Big controls, made for the tablet at the machine. The program opens read-only until you tap Modifica (Edit): a gloved tap writes nothing. And every command can be undone.

Next to the code, the machine

Next to every D and H offset in the program, the value the control holds right now. And from there the program goes to the CNC with the full round trip: send, read back, compare.

Your file stays your file

Open and save without changing anything: the file comes back identical to the byte, line endings and characters included. Tested on 12,419 programs from a real machine shop: 99.92% identical to the byte.

If it doesn't know what a number means, it leaves it alone. An S under G96 is in metres per minute, and the preview says so; G50 S on a lathe is the spindle speed limit, and it stays as it is. Where ERGANE doesn't recognise the control's dialect, the commands that rewrite numbers switch off — and it tells you why.

The path, before the spindle turns.

ERGANE draws the program's toolpath on the part, in 2D. And while the machine is cutting, the real tool position rides on top of it, read from the control, trailing where it has been. Top, front, side — and in 3D.

Technical drawing: a part clamped in a vice, an end mill in the spindle and the concentric passes inside the pocket.
The path the tool will take, drawn on the part. You look at it first, before the program goes to the machine; the call stays with the operator.

On the real stock

The 3D starts from the stock the CAM declared, not from an invented block, and removes material pass after pass.

Klartext too

Not just ISO code: Heidenhain Klartext programs get drawn as well, tilted planes included. When ERGANE can't draw a program correctly, it doesn't draw it: it tells you.

It's a view, not a safety system. It doesn't check collisions and it doesn't decide for you: it shows the path — the responsibility stays with whoever starts the cycle.

Measured tools reach the CNC.

Tools and work offsets for every machine on one page. If you measure on a Zoller presetter, you see for every offset the control's value, the presetter's measurement and the difference — and the measurement goes to the CNC without retyping the numbers by hand.

ERGANE's Tools and work offsets page: for every presetter tool, the H and D offsets with the control's value, the presetter's measurement and the difference; the state in words — aligned, different, empty, to decide — and a write button where needed.
Above, the selected program and the offsets it uses; below, one offset per row, with the difference picked out. App screen, sample data.

One row per offset

Control, presetter, difference. The row says in words whether it's aligned, empty, different or to decide — and why. Below, the work offsets as the control holds them right now, not as someone remembers them.

First the question, then the read-back

Before writing, ERGANE shows the machine and the numbers before → after, and waits for your yes. Afterwards it reads the control back and tells you whether it matches. If the value on the machine changed in the meantime, it doesn't write and shows you the new one.

It writes offsets, it does not move axes

ERGANE transfers the measured values: in batches, only into empty offsets and never into those of the selected program. Wear is corrected at the machine, and the operator starts the cycle, as always.

Lathes and Heidenhain: compare only

On lathes and on Heidenhain controls the table is compared with the presetter, and the measurement is entered at the machine. You still see the difference.

How long it ran, in one number.

Availability — cutting time over powered-on time — per week, month and year, machine by machine. Under every figure, what it rests on: how many powered-on hours, since when ERGANE has been reading, how long the machine didn't answer. Next to it, the target you set yourself.

ERGANE's Report / Availability for week 38: shop availability 72.1% against an 85% target, what it rests on (7 of 7 days, 280 powered-on machine hours), and one row per machine with availability, powered-on hours, stops and top cause.
The shop's week: the figure, the target and what it rests on, then one row per machine with its stops. App screen, sample data.

It finds the stops on its own

Five minutes and up: stopped, paused or in alarm. You give the cause in two taps if you want — it's not mandatory.

A log that stands up to the auditor

What ERGANE can't see gets written in by hand. A stop can't be deleted: it's reversed with a reason, and stays there, struck through. A new target applies from a set date, never retroactively.

As a PDF, in Italian or German

The report ready to leave the workshop, no touch-ups. And the CSV, for whoever wants to redo the maths.

Availability, not "full OEE". ERGANE measures what the control can actually tell it: times, states, part counts. Performance and quality stay out — we do not invent them. And a machine that doesn't say whether it's cutting gets no figure: better a declared gap than an invented number.

Who's running what. And when it's done.

When the customer calls and asks when it will be ready, the answer is on the screen — not in someone's memory.

Technical drawing: a TV hangs high above the machines on the shop floor showing the planning board; two machinists glance up at it from a distance.
On a TV hung in the workshop: you look at it from eight metres away, in passing, walking from one machine to the next.
ERGANE's Planning, week 39: one row per machine with jobs as bars (Staffa SX, Albero 90, Flangia Ø200 running 3 days late…) and, under each row, the strip of what the machine actually did, with its availability.
The shop-floor board: the plan on top, and under each machine what actually happened, read from the machines, with the availability from the Report. A job that runs past its delivery date flags itself.

Three things we don't do

  • We don't command the machine. We read it and we confirm it: no software of ours moves an axis.
  • It's not a timeclock. We measure the machines, not the people.
  • The data never leaves the workshop. On your server, not ours. No subscription to keep it alive.

The maths, do it yourself.

Taking a program to the machine: 15 minutes, four times a day. Conservative numbers from a real machine shop: the USB-stick round trips, the measurements taken at the machine, the edits made at the control.

Taking a program to the machine15 min
Times a day× 4
Working days per year× 220
Hours a year, at CHF 70 an hour220 h
You pay today15,400CHF
With ERGANE5,100CHF
You keep10,300CHF

Do the real example with your own numbers, in 30 days, on your own machine. A conservative estimate, not a promise of savings: your floor will have its own numbers, and the site survey exists to put them on the table.

How it starts.

One hour, at your place

We come to the workshop for the preliminary analysis and map the fleet: what control each machine has, what network is there, what connects and what doesn't. From that we prepare an assessment of your own situation, old machines and new. Without this step we don't start, and we make you no promises.

Thirty days on trial

A single machine — usually the oldest one. No cost, no commitment: your own data does the talking. At the end there's a straight answer: it can be done, or it can't. And the shop-floor numbers gathered in those thirty days stay yours, whichever way it goes.

The whole floor

If the pilot talks, we connect the rest, put the program archive on your server and hang up the board. Licence per site: the software stays yours.

Who is behind ERGANE.

More than 25 years on shop floors and in customers' offices taught us one thing: no shortcuts and no middlemen. We stand behind work done properly and systems that grow over time. Whoever looks after ERGANE looks after you.

Developed on the shop floor. Conceived, developed and supported by NS Net Source Sagl, and tested in production: ERGANE works in a machine shop every day, across different makes and vintages, against real deadlines. And if something's wrong, the app prepares the package to send us so we can understand the problem: no PIN or password ends up inside.

Already on the shop floor? Walk in with ERGANE.

Anyone selling machine tools, CAM, presetters or service is in the workshop before we are — and the owners trust them. If that's you: bring ERGANE to your customers, we'll handle the technical side.

  • We run the demo together, the first time. After that you run it yourself, if you want: connect the oldest machine and you'll see.
  • Your share is agreed up front, in writing, and follows what you bring: the customer, the demo, first-line support.
  • The customer stays yours. We do the connection and the software — we don't go around you.
Let's talk as partners

Let us try connecting the oldest machine you have. If it doesn't talk, it cost you nothing.

Tell us how many machines you have, which makes, and — if you know — which control they run. We'll tell you what connects, no waffle.

ERGANE is in production today at a machine shop in Ticino, on a mixed fleet of different makes and generations. The case, in full →