Shopfloor Log¶
The Shopfloor Log is where the shop floor records what happened on each machine: the production counts (good, scrap and rework) and the downtime (when the machine stopped, and why). Availability comes from the downtime; Quality and Performance come from the counts.
The page has five tabs:
| Tab | What it's for |
|---|---|
| Log Entry | The form for recording counts and downtime |
| Ongoing Downtimes | Every stoppage still running, on any machine |
| Downtime History | Stoppages that have ended |
| Production Entries | Counts that have been logged |
| Logbooks | Checklists and logbooks of the process that are waiting for you to fill in |
All five sit on one page, one under the other. Scroll down and the tab you've reached is highlighted; click a tab to jump straight to it. The tabs stay at the top of the screen while you scroll. A red number on Ongoing Downtimes shows how many stoppages are running right now.
Choosing a process¶
The process list at the top right of the page decides which machines the whole page works with. It starts on your first process (in the order set for processes in Digital Twin). Once you scroll down and the tabs stay at the top, the process list moves up beside them, so you can change process from anywhere on the page.
- The machines it covers are every machine on any of that process's lines.
- Of those, the page shows the ones assigned to your OEE shift — the same rule as before (see Which machines appear in the Machine list).
- If the process has no lines, or its lines have no machines on them, the page uses your shift's machines instead.
That one set of machines is what the Machine list in Log Entry offers, and what Ongoing Downtimes, Downtime History and Production Entries show — entries for machines outside the selected process are left out. Switching process clears the machine chosen in Log Entry.
The Log Entry form¶
The form has three parts. The top part — Machine and shift — is shared. Below it are two sections, Production and Downtime, each with its own button. Whatever you pick in the top part is used by whichever section you save, so you can log a count and a stoppage for the same machine without picking it twice.
Machine and shift¶
- Machine — the machines assigned to your OEE shift in Shift settings, or every machine if none have been assigned. See Which machines appear in the Machine list.
- Work Order (optional) — the order being run.
- Logged By (optional) — the person recording it. The list shows who is rostered onto the shift on the selected date, so it's a short list rather than everyone in the organisation.
- Shift Date and Shift Row — which row of the shift the entry belongs to (see A shift can have more than one row). The shift itself is the one set up under Shift Mapping.
Shift Date and Shift Row start on the row that is running right now, and a line under the fields confirms it — "Currently in: Day". For everyday logging you don't need to touch them.
Pick an earlier date or row to record something you missed — a past shift that was never logged, say. The line under the fields then shows that row's window and says the entry will be saved as a backdated entry, and both sections below change to suit (described in each section). Back to Live puts the fields back on the current row.
A row that hasn't started yet can't be logged against; Enture says so and the buttons stay disabled.
When the current time isn't in any row
If the current time falls outside every row of the shift, nothing is preselected and Enture says so. You can still log counts and start a stoppage at the current moment — worth checking Shift settings if that's unexpected.
Production¶
- Choose the SKU / Routing — the product being made and the operation being performed.
- Set Good, Scrap and Rework using the steppers.
- Click Log Count (or Reconcile Entry for a past row).
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. After saving, the counts reset to zero and everything else stays as it was, ready for the next entry.
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.
For a past row, the entry is recorded against the start of that row automatically, and if the machine counts its own pieces the steppers may already be filled in — see Counts filled in from the machine.
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.
Downtime¶
On the current row, the Downtime section is a stopwatch:
- When the machine stops — add Notes if useful and click Log Downtime. The stoppage is now running and appears under Ongoing Downtimes.
- When it runs again — with that machine selected, the section shows how long the stoppage has been running, with the reason selectors underneath. Pick the reason, add notes if useful, and click Close stoppage.
Reasons narrow in three steps — choose the Category, then the Subcategory, then the specific Reason — so finding the right one stays quick even once you've set up a lot of them. The list comes from Reason Codes.
A reason is required to close a stoppage. A stoppage with no reason still counts against Availability but tells you nothing about why, and reasons are what the Summary groups by.
One stoppage at a time per machine
A machine can only have one stoppage running at once. If the section offers Log Downtime when you expected to close one, check that the Machine selected is the one with the stoppage running.
On a past row, the section books a stoppage that already happened:
- Enter the stoppage's start and end — they must fall within the shift row's window shown above; Enture won't let you backdate a stoppage outside the row it belongs to.
- Pick the reason (Category, Subcategory, Reason).
- Click Reconcile Entry.
Letting the machine tell you how long it was down¶
If the machine has a runtime parameter mapped (see Runtime Parameters), a panel appears above the start and end fields on a past row. It leads with how many minutes of that shift row are still unexplained, then shows where the row actually went — Ran, Already logged and Unexplained as one bar adding up to the row's length.
Fill in start & end puts those minutes into the start and end fields — you still pick the reason and save. Click it again to split the remaining time across several entries with different reasons.
The panel is a prompt, not a rule: you can ignore it, type your own times over it, or log downtime that the meter didn't notice.
Machines that log their own downtime¶
A machine can be set up to record its downtime by itself: a stoppage starts when the machine goes offline and ends when it comes back online, already carrying the machine's default reason. When you pick such a machine, the whole Downtime section is greyed out with a note saying so, and you can't log, close or backdate a stoppage for it. Production works as usual.
To give one of its stoppages a better reason, use Update reason under Ongoing Downtimes while it's still running.
Counts filled in from the machine¶
If the machine counts its own pieces and a cycle time standard points at those counters, the Production section fills the counts in for a past row 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.
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.
Counts are only filled in for a past row. Entries on the current row 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 it without you¶
Automation can record yesterday's counts and unexplained downtime once a day, from the same counter readings and runtime meter described above, without anyone opening this screen.
- Generated entries appear in Downtime History and Production Entries like any other, with a note saying they were generated.
- A generated stoppage uses a reason code you choose in advance — something that reads as not yet classified. Correct its reason and that sticks: automation refreshes the times on later passes but never touches a reason or notes once the entry exists. Filtering Downtime History by that reason gives you a worklist of everything still unexplained.
- Counts you logged by hand are 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 a stoppage you left open¶
Ongoing Downtimes lists every stoppage still running, for every machine — not just the one selected in the form, and regardless of any filter. A stoppage you started and then navigated away from is otherwise easy to lose track of, and it keeps counting the whole time. The tab also shows how many are running.
Each row shows the machine, when it started and how long it has been going (and counting). Close stoppage on a row opens a dialog for that stoppage: pick the reason (Category, Subcategory, Reason), add or change the notes, and click Close stoppage. The Log Entry form isn't touched, so anything you were in the middle of entering there stays as it was.
Stoppages the machine started itself¶
A stoppage started by a machine that logs its own downtime is marked Automatic. It ends by itself when the machine is back online, so the row has no Close stoppage. Instead, Update reason opens a dialog where you pick the reason (Category, Subcategory, Reason), change the notes if you like, and click Save reason. The stoppage keeps running.
The Reason column shows the reason each running stoppage has right now.
If the machine never comes back online
Users with beta access also see Close stoppage on these rows. Use it only when the machine won't report back, for example when its connection is gone for good, so the stoppage doesn't keep counting.
A stoppage someone started by hand can always be closed as usual, even on one of these machines.
Tip
If a stoppage has been running far longer than seems plausible, it was probably never ended. Close it with the right reason rather than deleting it — the time genuinely was lost, and deleting it just moves the problem into Availability.
Downtime History¶
Stoppages that have ended, with their Machine, start and end, Duration (to the second — 1h 05m 20s), Shift Time and Reason. The list isn't limited to one machine — until you pick one, it covers every machine in the organisation.
Shift Time is the row of the shift the stoppage fell in, as its clock window and name — 06:00–14:00 · Day.
Shift Time is worked out, not typed
A downtime entry records when the machine stopped, not which shift row that was — Enture works the row out from the start time, the same way the OEE figures do. So the row shown is the row the stoppage is measured against.
A stoppage at 01:00 on a night shift that began at 22:00 is attributed to the previous day's row, because that is the row it belongs to. A stoppage logged outside every row of its shift shows only the shift name, with the row left blank.
There is no product column
A stoppage records that a machine stopped, not what it was making. The only product link is the optional Work Order, so for most entries there is nothing to show.
Finding an entry
- Search matches machine name and work order number.
- The machine picker narrows the list to one machine.
- The funnel icon shows the filters: From / To (the last 7 days by default, both inclusive), and Category, Sub-category and Reason. The three reason filters narrow each other in order and only offer values that appear in the entries listed; choosing a broader level clears the narrower ones. Clear resets the dates, reason filters and search together.
Splitting a stoppage¶
A stoppage often has more than one cause — a machine jams, then needs a tool change before it can restart. Split (in the row's menu) divides one stoppage into pieces, each with its own reason, so each cause gets the time it really took.
- Click Split on the stoppage. The dialog shows the machine and the stoppage's start, end and duration, and starts with two pieces cut halfway.
- For each piece, set where it ends and pick its reason. The first piece always starts when the stoppage started and the last always ends when it ended; each piece starts where the one before it ends, so moving one piece's end moves the next piece's start.
- Add piece for more than two; the × on a piece removes it and gives its time to the piece next to it.
- The line under the pieces shows they add up to the whole stoppage. Click Split stoppage.
The pieces then replace the original stoppage in the list, each marked Split · 1 of 3 and so on. Together they cover exactly the same time as the original, so Availability doesn't change — only the reasons do (unless a piece is given a Planned reason, which moves that time out of Availability the same way it would for any stoppage).
A split is final
A split can't be undone, and a piece can't be split again. You can still Correct a piece's reason and notes like any other entry. Anyone who can log downtime can split a stoppage; only stoppages that have ended can be split.
Production Entries¶
Logged counts, with their Machine, when they were logged, the SKU, and the Good, Scrap and Rework counts.
Search matches machine name and SKU, the machine picker narrows to one machine, and the funnel icon shows From / To (the last 7 days by default).
Logbooks¶
Logbooks brings the process's checklists and manufacturing logbooks into the Shopfloor Log, so an operator can fill them in without leaving the page. Checklists and logbooks are listed together in one table; the Type column says which is which.
It shows only what is waiting for you to fill in:
- checklists and logbooks at the maker stage (for logbooks, also the power maker stage) whose maker group you belong to, and
- only those linked to the process selected at the top right. A checklist or logbook that isn't linked to any process isn't shown here, so link them first (see Checklists and Manufacturing Logbooks).
It has two tabs, each with a count:
| Tab | What it shows |
|---|---|
| Ongoing | Open checklists and logbooks you can fill in. One that someone else has already started isn't listed. |
| Refill | Ones sent back to you to fill in again. |
Use the search box, the date range and the name filter to narrow the list, the same way as on the Ongoing checklist and logbook pages.
Start filling opens the checklist or logbook, and Resume filling takes you back to one you have started. Filling in, saving and submitting work exactly as they do from the checklist and logbook pages. You can Cancel a checklist you haven't started, giving a reason.
If you have access to it, Generate checklist creates a manual checklist, as on the Ongoing checklists page.
Correcting an entry¶
Engineers (in engineering mode) see Correct and Delete on each row of Downtime History and Production Entries.
- A stoppage — Correct changes the reason and notes. Start and end times aren't editable: they are what was actually observed, and Availability is measured from them. If the times are wrong, delete the entry and log it again with the real times.
- A count — Correct reopens the good, scrap and rework steppers. The product and machine aren't editable; if output went against the wrong product, delete it and log it again on the right one.
- Delete removes the entry entirely. Use it for something that never happened; don't use it to hide time that genuinely was lost.
Note
Every figure is worked out from these entries rather than stored, so a correction takes effect immediately and everywhere — the Summary, the work order's OEE and the job card's alike.
Tip
Operators can't correct entries; only engineers can. So it's worth getting it right at the time — and never work around a mistake with a compensating or negative entry: 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.