Comes from the scale
The operator sets the roll down and waits for the stability signal: the system takes the weight itself, with the tare of core and packaging. If the scale fails the value can be typed, and it stays flagged as such.
- gross
- tare
- net
EDG Sistemi · Industrial Solutions · Production control
weighing, labelling and production control for plastic film
The weight comes from the scale, the job from your ERP, the label prints itself. Nobody writes a number by hand, and by the end of the shift the day is already on record: how much was produced, how much was wasted and why.
Weighing · labelling · reporting · Blazor · .NET 9 · SQL Server
What it is
SI.SCO PRODUZIONE lives at the machines and in the office. At the machine it weighs, labels and records waste; in the office it shows what is happening now and what happened yesterday. In between there is no paperwork.
The operator sets the roll down and waits for the stability signal: the system takes the weight itself, with the tare of core and packaging. If the scale fails the value can be typed, and it stays flagged as such.
Unique code, barcode, job data, the customer EAN when required and a QR code that opens the roll's history. Six layouts, full or anonymous, in Italian or English.
Type, source and reason are chosen in three taps, then it is weighed. No waste exists without a written reason, which is why at month end you know where it comes from.
One screen with all the lines: what they are doing, how fast, how much they are wasting, how far along the job is. You look from three metres away and you understand.
A column next to the scale: large screen, barcode reader, label printer and badge reader. Everything it takes to close a roll, and nothing else.
The weight is the scale's, the time is the clock's, the operator is the badge's. No manual step means no number anyone can argue with.
From the job to the pallet
Four gestures, always the same. Each one leaves a piece of data behind, and those pieces in a row become the history of the product: where it was born, who made it, what it weighs and where it went.
01
the sheet is scanned
The operator scans the barcode on the work sheet. The job comes from the ERP: customer, article, width, thickness, core, metres, number of rolls and notes.
02
the roll goes on the scale
The weight appears large on the display. Once it is stable the system takes it by itself, with the tare of core and packaging: gross, tare, net.
03
the label comes out
Unique code, barcode, job data and, when the order calls for it, the EAN. The QR code is on there too, and it opens the roll's history on a phone.
04
off to the warehouse
At the last roll foreseen the line stops by itself and waits for an authorised release. When the job is done it closes, and the line waits for the next work sheet.
Type, source and reason in three taps, then the weight. Eleven types and the reasons your plant decides. Every piece of waste gets its own label.
Every weighing knows which of the three bands it belongs to, and weekdays stay separate from holidays. That is what lets you compare crews without argument.
The minutes between one roll and the next, the hours of downtime, the reason behind a release, who corrected a weight: data that collects itself while the work goes on. Nobody fills anything in.
The thirty screens
None of these screens is a drawing: they are the pages of the system, with sample data. Here is the index, for anyone who wants to see the rest.
At the machine
The station with the large weight, the job detail, waste in three taps, the menu with ten tiles, reporting a stop and the changeover sheet.
The weight large in the middle, gross, tare and net one under the other, and the four keys it takes to close a roll.

The job fields as they come from the management system, the progress in rolls and kilograms, the waste on that order.

Type, source and reason in large boxes; then the material goes on the scale and is weighed.

Ten tiles, one per action: close order, reprint, manual weight, release, report a stop, line instructions.

The cause and the duration in two taps: that time goes into the figures without anyone writing it down.

The format-change sheet with its drawings, on the screen the operator already has in front of them.

In the office
Control room, operations, waste, jobs, dashboard, shifts and crews, downtime, year-on-year comparison, log, summaries, exports, system status.
The nine lines on one screen: status, job, kilograms per hour, rolls closed, waste and progress.

The figures for the day, the shift and the week, compared with the period before.

One line per roll and a search on nine criteria: dates, station, operator, order, item, type.

The waste grid, the causes in order of weight and how they concentrate on each line.

The orders as they come from the management system and the detail of the one in progress, with what is left.

The three shifts side by side, the teams and the waste of each band, with holidays kept apart.

Hours lost by cause, by line and by shift, and the average length of a stop.

Month by month, year on year, item by item: where production grows and where it falls.

Everything that changes a figure: corrected weights, releases, cancelled labels, with who and why.

You choose what comes out, look at the preview and then print it or save it to Excel.

The devices on every station — scales, printers and readers — with the outcome of the last check.

Who authorises it, why and how many extra rolls: the request and its history stay on record.

Configuration
Stations, labels and the six layouts, waste types and reasons, operators and badges, profiles and access, alerts and thresholds, automatic summaries.
The nine stations and the settings of one of them: scale, printer, label templates, waste types enabled.

The label templates and a preview of how they come out of the printer, before going on the line.

The six templates side by side, large enough to read: pack, EAN, plain, waste, bales, packaging.

The eleven types and the company's own reasons, with a preview of what the operator will see.

Records, badge reading and what each of them may do, station by station.

The five profiles, the passwords, the badges and the last logins, with a lock after five tries.

When the system has to speak up and to whom: line stopped, waste over the threshold, limit reached.

The scheduled sendings, the recipients, and a manual send over any range of dates.

Outside
The history of a roll, the shift leader's tablet, the phone with the stop alert and the read-only customer portal.
From the job to the delivery, line by line, with every correction and its reason.

The nine lines in hand, the release requests to authorise with a badge, the stops to look at.

How the shift is going, the alert when a line stops, and the roll read with the QR code.

The job, read only, for whoever ordered it: rolls ready, weight, metres and expected delivery.

None of these screens is a drawing: they are the pages of the system, with sample data.
Twenty-four hours
The shop floor does not stop at six in the evening, and neither does the system. Night shift weighings come in with their band, alerts find the shift leader on the phone, and the next morning the numbers are already there, without anyone switching on a computer.
From the QR code to the whole story
The code on the label is not only for printing. Scanned with a phone it opens the life of that roll: which job it comes from, which line made it, who made it, at what weight, whether anyone corrected it and where it ended up.



Nobody enters anything to make it possible. You weigh, you label, and the story is already written.
How it is built, how you start
Nothing is installed on workstations: the system sits on the company server and opens in a browser, on the line as in the office, on the tablet and on the phone. Scales and printers connect to the stations; updates happen in one place.
Blazor on .NET 9 and SQL Server, the same technology as the other SI.SCO systems: no components to install machine by machine, no versions to keep in step.
You start with one line and carry on with the others: production never stops.
Start-up takes a few weeks. The scales, printers and readers are the ones on your floor; the link to the ERP is read-only, and nothing changes in the way jobs are created.
Five profiles, encrypted passwords, lockout after five attempts, badges you can switch off in a second. Every corrected weighing, every release and every cancelled label stays in the log, with its reason.
RequirementsNothing exotic: a Windows machine, SQL Server and the shop floor network. Stations are added when they are needed, without rebuilding anything.
Would you like to see them?
The people on the line make four gestures, and that is all. Around them the shop floor writes itself: the control room, downtime that gets counted, the tablet, the customer portal and an archive you can open from anywhere.
16 pages · PDF · in five languages

A live demonstration takes half an hour and is run on the lines you already have: no scales replaced, no production stopped.
Contact
What is weighed, what is labelled, what does not add up at the end of the day: that is the starting point, with a site visit, and it ends with a written proposal. No commitment before the proposal.