Your entire plant,
in one system.
Dies, machines, maintenance, tickets, production and cost — not spread across six spreadsheets and three notice boards, but in one place, in real time.
No obligation · We reply within 1 business day
Sound familiar? These are not small annoyances — they cost real money.
On a shop floor the loss is rarely dramatic. It is not one big breakdown that eats the margin, but twenty minutes of searching every day, one missed service, and a ticket nobody knew was still open.
Where is that die?
Half an hour lost in the racks, because the register lives in a spreadsheet nobody updated for two weeks.
It broke again
Without stroke counting, preventive maintenance is always late. The breakage, however, is right on time.
Who did it, and when?
The repair is on a sheet of paper that has gone missing. The same fault gets analysed for the third time.
Which product loses money?
You find out at year end that a part has been unprofitable for months. By then the order is already made.
In short: it keeps in one place what today sits in six
SynCore digitises the daily running of a plant: what is happening to the dies and the machines, what broke, what has to be made today, how much came off the line in the shift, and what it earned or cost. One database, one login, everyone sees their own view. Here is what that looks like on an ordinary day:
06:10 — the shift starts
The operator opens the shift journal on the tablet next to the machine and logs piece counts and scrap hourly — the same thing they wrote on paper, except this also turns into OEE.
09:40 — a die jams
Two taps, a photo of the fault, and the ticket is moving. The toolmaker gets the alert on their phone, and the display on the shop floor shows everyone which machine is down and for how long.
09:45 — the system remembers
The same fault came up last year. The knowledge base offers the fix that worked, how long it took and what did not work — nobody has to work it out twice.
11:00 — maintenance falls due
The die has reached 80,000 strokes, the machine 250 running hours. The job is raised before the breakage, with an owner and a due date — not scribbled in a diary.
13:20 — where is that die?
The storage map shows it: zone A, shelf P3. Scan the QR code on the die and you are on its follower sheet — instead of half an hour spent walking the racks.
14:00 — end of shift
The journal closes and you can see straight away how much went out, how much was scrap, how much downtime there was, and whether that product made money that day. Not at month end.
Next morning — what do we run?
Planning turns the open orders and the stock into a daily plan: what goes on which machine, what has no material, and which line will not make its due date.
End of week — the management view
Response time, repair time, first-time-right rate, OEE, the products losing the most money. Nothing to stitch together: the screen is the report, and it exports to Excel and PDF.
End of month — improvement
Recurring faults become CI actions with an owner, a deadline and a measured saving. The system shows afterwards whether the action actually delivered anything.
You tried other ways. This is different.
vs. Spreadsheets
Excel does not send alerts when a PM is overdue. It does not calculate OEE, and the file vanishes from the shared drive. SynCore keeps everything in one place and warns automatically.
vs. Paper-based
The repair slip got lost in the corridor. The maintenance log is illegible. SynCore digitises everything: search, filter, report — one click away.
vs. Big ERP
Enterprise ERP needs an IT department, takes months to implement, and the interface was not designed for the shop floor. SynCore installs on a mid-range server in a day.
Work out what the system would return in your plant
Set your own numbers. The estimate has two parts: reduced unplanned downtime, and the working hours currently lost to searching.
Assumptions: a 15% reduction in unplanned downtime (through preventive maintenance and faster ticket response), plus 4 working hours per machine per month saved on searching and admin, at an internal rate of 9,000 HUF/hour. This is an indicative estimate, not a guaranteed result — the real figure differs from plant to plant.
The first year of a 6-machine plant — line by line
The calculator above counts two items. In practice the saving comes from more places, they just do not show up in the machine log. Here is the first year of a typical three-shift plant running around 350 dies, broken down item by item.
| Where it comes from | How we worked it out | Which module | Annual effect |
|---|---|---|---|
| Less unplanned downtime Due maintenance does not slip, and a fault does not sit unreported for hours. |
6 machines × 6 h/month unplanned stop × 15% reduction × 45,000 HUF/h | Machine and die maintenance, tickets | 2,916,000 HUF |
| No hunting, no paperwork Storage map, QR code and a digital follower sheet instead of walking the racks. |
6 machines × 4 hours/month saved × 9,000 HUF internal hourly rate | Die register, storage map | 2,592,000 HUF |
| Less scrap Scrap is visible by cause right after the shift, not at the monthly close. |
700,000 good pcs/year × 0.3 percentage point less scrap × ~1,100 HUF/pc material and labour | Production, economics | 2,310,000 HUF |
| Breakages that did not happen Stroke-based due dates: maintenance comes before the breakage, not after it. |
2 avoided breakages a year × 350,000 HUF repair and replacement | Die maintenance | 700,000 HUF |
| No report stitching The screen is the report; the Excel export is one button. |
5 h/week of management and engineering reporting × 46 weeks × 9,000 HUF | Overview, statistics, export | 2,070,000 HUF |
| Total — first year | ≈ 10.6 M HUF | ||
This is a model calculation, not one customer's result. We do not publish reference figures about the plants we work with. Every line above follows logic the system actually measures — at the demo we recalculate it with your machine count, hourly rate, scrap rate and downtime, and we will say so if it does not add up.
What it takes from you
The shift journal has to be kept, and faults have to be reported at the machine. Once that happens, the rest assembles itself — which is why the operator screens are designed around a handful of taps.
When the first results show
Hunting time and ticket response time improve in the first weeks. The OEE and economics picture needs 4–8 weeks of data to become meaningful.
Measured, not felt
The system measures the period before and after rollout: response time, repair time, first-time-right rate, downtime. You do not have to take our word for it.
Seven modules, one database, no double entry
These are not separate programs: a ticket knows which die it belongs to, maintenance sees the stroke count, and the profitability analysis works from the actual production journal.
The whole life of a die on one page
Register, storage location, stroke count, condition, documents and the full repair history. The follower sheet is created digitally instead of getting lost in a corridor.
- Maintenance due dates driven by stroke count
- Photos, drawings and measurement reports attached to the die
- Storage map: which rack, which shelf
Traceable from report to closure
Anyone can raise a ticket, the system notifies, the owner sees their queue. The statistics then show where response time slips and what keeps coming back.
- Priority, owner, deadline, SLA monitoring
- Public board for a shop-floor display
- Response and repair time trends, first-time-right rate
Preventive maintenance that actually prevents
PM plans per machine, cycles, completed and overdue jobs. Coolant emulsion checks run here too, with measurements and limits.
- PM and CM jobs in one calendar
- Spare part usage linked to stock
- Emulsion: concentration, pH, measurement log
Shift log instead of paper — and OEE for free
The operator records the shift: piece count, scrap, downtime and reason. That turns into OEE, trends and a live shop-floor display, with no extra data entry.
- Digital production journal per shift
- OEE: availability, performance, quality
- Live view for a wall display, no login needed
What has to be made today — and what will not fit
From the open customer orders and the stock on site it derives, day by day, how much of which item is needed, whether there is material for it, which machine it lands on and whether it fits the available capacity. Instead of the old "open order" spreadsheet.
- Daily plan and weekly load per machine and operation
- Warns when a line cannot be made before its due date
- Shop-floor TV wall with the to-do list — no login needed
Shows which product loses money — and why
Contribution margin per product, scrap and downtime converted into money, on a waterfall chart. You find out after the shift, not after the year.
- Product-level margin and payback
- Scrap and downtime cost in currency
- Waterfall analysis: where the money disappears
CI process and tasks, not sticky notes on a board
A Kanban board for daily work, alongside structured process improvement: goals, owners, maturity level and a knowledge base.
- Tasks on a Kanban board, also from templates
- CI: SMART goals, recurrences, maturity scoring
- Knowledge base built from solved faults
What can SynCore do? What can't it?
The modules work together: the ticket knows which die it belongs to, maintenance sees the stroke count, and economics works from the actual production journal.
| Feature | Dies | Machines | Tickets | Production | Economics | CI / Tasks | Planning |
|---|---|---|---|---|---|---|---|
| Registry / register | ✅ | ✅ | ✅ | ✅ | — | ✅ | ✅ |
| Stroke counting | ✅ | — | — | — | — | — | — |
| Preventive maintenance | ✅ | ✅ | — | — | — | — | — |
| OEE calculation | — | — | — | ✅ | ✅ | — | — |
| Automatic alerts | ✅ | ✅ | ✅ | — | — | — | ✅ |
| Photo / document attachments | ✅ | ✅ | ✅ | — | — | ✅ | — |
| Cost / margin calculation | — | — | — | ✅ | ✅ | — | — |
| Public display / TV wall | — | ✅ | ✅ | ✅ | — | — | ✅ |
| Export (Excel / PDF) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Pricing
No hidden costs. Price depends on plant size and the number of modules rolled out. You do not have to implement everything at once — start with the most urgent problem.
Dies + Tickets
Solve the most urgent problem: registry and ticketing in one place.
+ Machines + Maintenance
Full maintenance system with PM scheduling and emulsion checks.
All modules
Production, economics, CI process — complete manufacturing control.
In our demo we prepare a personalised, itemised quote — with no obligation.
Not a concept mock-up. This is the working system.
The images below are from the actual SynCore interface, filled with demonstration data. Click to enlarge.
See it for yourself — right now
This is not a video or a slideshow: it is a real, running SynCore filled with demonstration data. Click through the modules, open a die, a fault ticket or the production report — you see exactly what you would see on the shop floor.
The login is view-only: it cannot create, change or delete anything, so there is nothing you can break. The data is fictional, not real plant data.
Three steps and it runs
Not a months-long project. The system runs in Docker; a mid-range server is plenty.
Assessment and demo
We look at how the plant works today and walk you through the system live. That is when it becomes clear which modules you actually need.
Installation and data migration
Installed on your own server or on a machine we operate. Existing die and machine lists are imported from Excel.
Training and go-live
Short, role-based training — operator, maintenance, engineer, manager. In-system help is available on every module.
Your data stays yours
It can run entirely on the plant's own server, even without an internet connection. No mandatory cloud, no data handed to third parties.
Add modules as you go
You do not have to roll out everything at once. Start with the die register; the rest can follow later.
Tailored to you
Roles, permissions, fields and settings that follow your own processes. Custom modules can be built on request.
What people ask before deciding
How much does it cost?
Pricing depends on plant size, the modules you roll out and how it is hosted, so we do not publish a fixed price list. After the demo you get a specific, itemised quote — with no obligation.
Where is our data stored?
Wherever you want it. The system can run on the plant's own server inside a closed network, in which case no data ever leaves the site. If it is more convenient, we can host it for you.
What happens to our existing spreadsheets?
We take them over. Die, machine and part lists can be imported, so nobody retypes hundreds of rows. Export stays available too: lists can be saved to Excel and PDF.
How long does it take to train people?
Half an hour to an hour per role for daily use. The operator screen is deliberately designed around very few clicks, and every module has built-in help.
Does it work on tablets and phones on the floor?
Yes, the interface is responsive and works on tablets and phones. A large live display can also be put on the shop floor, which needs no login at all.
What if we need something custom later?
We develop the system ourselves, so a custom field, report or even a whole module can be built. This is not a boxed product locked to an outside vendor.
Let's look at what it would bring to your plant
The demo can be online or on site — no obligation whatsoever. Choose your preferred way below:
- A live walkthrough, mapped onto your own processes
- An honest answer if SynCore is not the right fit for something
- An itemised quote after the demo
Or directly: info@syncoresystem.com