DISCRETE MANUFACTURING · AUSTRALIAN INDUSTRY
“We need to automate the line.” “We need better scheduling software.” “We need to track jobs in real time.” ThynkProcess hears some version of this from almost every discrete manufacturer it works with. And in almost every case, the same question gets asked before the conversation goes any further: what does your current job data actually tell you about where time is being lost?
The answer is almost always the same. It doesn't. Not really.
| The example below is drawn from a real ThynkProcess client engagement. Identifying details, including the name and location used, have been changed to protect the client's confidentiality. |
THE SCENE
Eighteen Years of Good Instincts, and a Slipping Number
Consider a $35 million metal fabrication business in Western Sydney — custom steel components, around 60 employees, a solid book of work. The owner, referred to here as Mark, had been running the business for eighteen years, with good instincts and strong customer relationships behind a growing order book.
But his on-time delivery rate had slipped from 88% to 71% over two years — not catastrophically, but enough to start costing repeat orders and straining relationships built over years. Mark's plan was clear: upgrade the scheduling system, and possibly add a shop floor terminal so operators could log job progress in real time. He had already spoken with two software vendors.
Before any commitment was made, ThynkProcess spent half a day on the floor.
WHAT WAS FOUND
The Problem Wasn’t Scheduling
The real problem wasn't scheduling. It was that nobody — including Mark — had a reliable picture of how long jobs actually took versus how long they were estimated to take. The estimating system and the production system had never been reconciled. Quoting was based on historic averages that were five years old and no longer reflected the current machine mix, skill levels, or material lead times on the floor.
New software layered on top of that foundation would have delivered a faster, more expensive version of the same inaccurate picture.
WHY THIS KEEPS HAPPENING
A Data Problem Specific to Discrete Manufacturing
Discrete manufacturing carries a data problem that process manufacturing doesn't share, and it's worth naming clearly. Every job is different — a custom fabricator, a precision machinist, a contract electronics assembler each has its own routing, setup time, and material requirements. That variability is the business model. But it also means job costing, routing, and time standards drift away from reality faster than most businesses realise, unless they are continuously updated against actual performance.
Three specific causes drive that drift:
| Source of Drift | What Happens on the Floor | Why It Stays Invisible |
| Stale time standards | Estimating teams work from standards set years ago and never revisited | Revisiting them requires an owner, and typically nobody has been assigned one |
| Jobs closed at standard time | Operators close jobs at the system’s expected time rather than actual time | The system is satisfied, so the discrepancy never surfaces as an exception |
| Unlogged rework and substitutions | Scrap, rework and material substitutions are absorbed informally rather than recorded | Logging takes time, and nobody wants to be seen as the one slowing the job down |
The result: the ERP or scheduling system shows a clean picture, while the floor tells a different story. Investing in automation or advanced scheduling on top of that foundation means optimising a fiction — and this isn't a small-business problem. ThynkProcess has seen the same pattern in $80 million make-to-order manufacturers running a ten-year-old ERP with 200 staff. Business size doesn't fix the data quality issue; it simply adds more layers of workaround on top of it.
THE APPROACH THAT WORKED
Six Weeks, No New Software
Mark went back to basics. Over six weeks, ThynkProcess reviewed actual job time data, reconciled it against estimates, and rebuilt time standards for the thirty most common job types in the business. Scheduling didn't change. Software didn't change.
| Metric | Before | After |
| On-time delivery rate | 71%, down from 88% two years earlier | 86%, recovered within four months |
| Estimating basis | Historic averages, five years old, never reconciled against actuals | Rebuilt time standards for the thirty most common job types |
| Technology changed | Two scheduling software vendors already engaged | None — scheduling system and software were unchanged |
| What changed instead | — | Six weeks reconciling actual job time against estimates |
Mark's business has since implemented a shop floor data capture system that now feeds accurate, reliable information into scheduling — technology that works because the foundation underneath it is finally sound.
THE PATTERN THAT MATTERS
Better Data, Not Just Better Software
Australia's discrete manufacturing sector is full of capable operators running businesses on foundations of accumulated assumptions. The opportunity isn't necessarily better software — it's better data feeding the software already in place.
The manufacturers who gain ground over the next decade won't necessarily be the ones who automate fastest. They will be the ones who understood what their operations were actually doing before they tried to change them. Manufacturers who break this pattern share one trait: before investing in any new system or automation, they close the gap between estimated and actual job data — not as a one-off exercise, but as an ongoing discipline that treats time standards as a live document, not a historical artefact.
When a discrete manufacturer invests in scheduling or shop floor software and it doesn't deliver — what's usually the real cause? The software, the implementation, or something that was broken before the project even started?
Discrete Manufacturing · Australian Mid-Market Manufacturing · ThynkProcess