Skip to content

Production Entry

Production Entry is where the output of a run is recorded: how many pieces were good, how many were scrapped, and how many need reworking. Quality and Performance are both worked out from these counts.

The page is built for a shop-floor terminal — large plus and minus buttons rather than fiddly typing.


Logging counts

  1. Choose the Machine and Shift — the Shift list only shows the shift set up under Shift Mapping, picked for you automatically. The Machine list shows the machines assigned to the selected shift in your Shift settings, or every machine if none have been assigned — see Which machines appear in the Machine list.
  2. Optionally pick the Work Order being produced, and Logged By — the list shows who is rostered onto that shift.
  3. Choose the SKU / Routing — the product being made and the operation being performed.
  4. Set Good, Scrap and Rework using the steppers.
  5. Click Log Count.

Counts are cumulative across the shift row: log them as you go, hourly or at the end of a run. Each entry is a separate record, and the row's figures are the sum of them.

Because each entry is logged at the current moment, there's nothing to pick for the Shift Row here — Enture shows a read-only "Currently in" line naming which row the current time falls into (see A shift can have more than one row), so you can confirm you're logging against the row you expect.

Choosing a Work Order locks the product

Once you pick a Work Order, the SKU list narrows to what that order is actually building. This prevents output being logged against the wrong product — a mistake that is tedious to unpick later, because it distorts two products' figures at once.


What the three counts mean

Count Meaning Effect on OEE
Good Right first time, needs nothing further Counts as good in Quality
Scrap Cannot be recovered Counts in the total, not as good — lowers Quality
Rework Can be put right with further work Counts in the total, not as good — lowers Quality

Scrap and rework both lower Quality, and neither lowers Performance. The machine produced those pieces, so it gets credit for the time spent; the loss shows up as quality, which is where it belongs.


Logging counts you missed at the time

If output from a past shift was never logged, switch to Reconcile from the Log Count dialog instead of using the live form.

  1. Choose the Machine, Shift and Shift Date, and the SKU / Routing.
  2. Choose the Shift Row — which of that shift's rows the output belongs to (see A shift can have more than one row). If there's only one row for that date, it's picked for you.
  3. Enture shows that row's actual window for the date you picked, and records the entry against the start of it automatically — there's nothing to set here yourself.
  4. Set Good, Scrap and Rework as usual. If the machine counts its own pieces, these may already be filled in — see Counts filled in from the machine.
  5. Click Reconcile Entry.

Switch back to Back to Live to return to the normal entry form.


Counts filled in from the machine

If the machine counts its own pieces and a cycle time standard points at those counters, Reconcile fills the counts in for you as soon as you've picked the machine, shift date, shift row and product.

Every figure stays editable. What's filled in is what the machine measured; if you know better, change it.

Under each stepper, a line tells you where the number came from — or why there isn't one:

What it says What it means
"500 measured by the machine" The counter's own figure for that whole shift row
"Your share of 500 measured, split by plan" The shift row ran more than one product, so the measurement has been divided between them in proportion to the production plan. This is worked out from the plan, not measured — check it against what actually ran
"300 already logged for this SKU, so only the remainder is offered" Someone has already reconciled this shift row. Only what's left is offered, so nothing gets counted twice
"500 measured for this shift row, 300 already logged against other SKUs" The row has no plan, but another product has already been logged against it, so only the unclaimed remainder is offered
"Counter measured 500 for this whole shift row, shared across 2 SKUs — enter this SKU's share" More than one product ran, and the plan can't say how much of it was this one. Enter the split yourself
"No counter data recorded for this shift row" A counter is mapped, but nothing was recorded for that row — most often because the machine wasn't connected at the time, or was only wired up later. Enter the count by hand
"Could not read the machine's counter" Enture couldn't reach the machine data just then. Enter the count by hand; nothing is blocked
"The counter reading looks wrong (reset or rollover)" The counter went backwards over that shift row, which usually means it was reset or wrapped around at its maximum. The reading isn't trustworthy, so none is offered

A count with no counter mapped gets no line at all and behaves exactly as it always has.

A blank is never a zero

Where a counter is mapped but no reading is available, the box is left blank rather than set to 0. A zero would say the machine measured no scrap — which is a very different claim from "we don't know", and it would show up as a perfect Quality figure that nobody actually measured.

If the totals don't match

If what you're about to save would take the shift row past what the counter measured, Enture says so — for example "This shift row would total 550 against 500 measured." It's a note, not a block: the figures are yours to decide. A gap usually means the actual product mix differed from the plan, which is worth knowing rather than hiding.

The counts are only filled in on Reconcile, not on the live form. Live entries are recorded at the current moment, and a counter reading only exists for a shift row once that row is over.

Or let Enture record them without you

Once counter parameters are mapped, you can skip this screen entirely for those machines: Automation records yesterday's counts once a day, from the same readings and with the same plan-proportional split described above.

Generated entries appear in Recent entries like any other, with a note saying they were generated, and you can correct or delete them. Two things to know:

  • Anything you logged by hand is subtracted first, so a shift you part-logged yourself is never double-counted.
  • To adjust a generated count, add a separate entry for the difference rather than editing the generated one — automation re-reads the counter and will overwrite the figure on its own row.

Finding an entry

Search — the box beside the buttons at the top of the page searches by machine name and SKU. It narrows the entries already listed, so it works alongside the date filter.

Filtering by date — the funnel icon beside Log Count shows or hides the From / To date filters above the table. By default the list shows the last 7 days.


Recent entries

The table lists recent entries with their Machine, counts, product and the shift row each one was recorded against.

Machine is listed because the table isn't limited to one machine — until you pick one, it covers every machine in the organisation.

Correcting a count

Engineers see Correct and Delete actions on each row. Correct reopens the same good, scrap and rework steppers so the entry can be set to what it should have been; Delete removes it outright.

The product and the machine aren't editable — if output went against the wrong product, delete the entry and log it again on the right one, since that mistake distorts two products' figures at once.

Tip

Operators can't correct entries; only engineers can. So check the counts and — above all — the selected product before logging. Never try to cancel a mistake by logging negative or offsetting counts: that leaves two wrong entries instead of one.


If you record work on Job Cards

Where work is tracked on a Job Card, the shift entries on the card are the place to record output — not this page. Those counts feed OEE automatically, so entering them here as well would count the same production twice.

This page remains the right place for production that isn't tracked through a job card.