Cycle Time Standards¶
A Cycle Time Standard is the time one piece should take on a given machine. It's the yardstick Performance is measured against — without one, Performance can't be worked out at all.
Setting these up is an engineer's job.
What a standard holds¶
| Field | Description |
|---|---|
| Machine or Line | What the standard describes. Set one or the other, never both — a machine standard measures that machine, a line standard measures the whole line |
| SKU | The product this standard applies to |
| Ideal Cycle Time (sec/unit) | How long one piece should take under ideal conditions, in seconds |
| Setup Time (min) | Optional — changeover time before the run proper begins |
| Operation Sequence | Optional — which operation this is, where a product passes through the same machine more than once |
| Counter parameters | Optional — the machine's own counters for good, scrap and rework pieces. Machine standards only. See Counter parameters below |
Ideal, not average
The ideal cycle time is the best sustained rate the machine can achieve for that product — not the average it currently manages. Setting it to the current average guarantees a Performance near 100% and hides exactly the losses the measure exists to reveal.
Adding a standard¶
Click the + icon at the top of the page to add one. Use the search box above the list to find an existing standard by machine, line or SKU name.
Changing a standard¶
Standards are versioned rather than overwritten. Adding a new standard for the same machine, product and operation supersedes the previous one from that point onward; the old version stays attached to the periods it applied to.
This means improving a standard never rewrites past performance figures. Last quarter's Performance continues to be measured against the standard that was actually in force at the time, which is what makes comparing quarters meaningful.
Only the current standard for each machine and product is listed. Use a row's History action to see every version it has had — each one's effective date, its cycle and setup times, and which is in force today.
Updating a whole process at once¶
When the same product runs on many machines in one process, you can set its cycle time for all of them in one go instead of one machine at a time. Click Update for a process at the top of the page. You can also open it from a process's ⋮ menu on the Processes screen, with that process already picked.
- Pick the process and the SKU. If the process has its own SKU list, only the SKUs it may use are offered.
- Enter the ideal cycle time (seconds per unit) and, optionally, the setup time.
- Choose Apply to: Machines (the default), Lines, or Both. Machine and line standards are separate, so this decides which kind is updated.
- Choose Which ones:
- Already have a standard (the default) only updates machines and lines that already have a standard for this SKU. Nothing gets a standard for a product it never runs.
- All also adds a new standard to the ones that don't have one yet.
-
Click Preview. Every machine or line in the process is listed with its current cycle time, the new one, and what will happen:
What happens Meaning New version It has a standard with a different value, and will get a new version New standard It has no standard for this SKU yet, and will get one (only with All) Already this value Its current standard already has this cycle time and setup time, so nothing changes No standard for this SKU Left alone, because Already have a standard is selected -
Untick any machine or line that needs its own value, then click Update.
The update is all-or-nothing: either every ticked row is saved or none is. Each machine and line still gets its own standard with its own history, exactly as if you had added them one by one, and each keeps its counter mapping.
Which machines belong to a process
A process's machines are the machines on its lines. A machine that isn't on one of the process's lines is not included, even if it is tagged with the process. The Lines & machines view on the Processes screen shows exactly what an update will cover, and lists any machines that are left out.
If the process changed after you previewed
If a ticked machine or line was moved out of the process between the preview and the update, nothing is saved and you are asked to preview again.
Changing any field after previewing clears the preview, so what you update is always what you last saw.
Deleting a standard¶
A standard that has never been used can be deleted with the bin icon. One that production counts already reference cannot be deleted — Enture will say so, because removing it would leave those counts pointing at a standard that no longer exists. Supersede it instead by adding a new one, which is what the versioning is for.
Counter parameters: filling counts in automatically¶
If a machine already counts its own pieces — a counter on the PLC, wired into Enture as a parameter — you can point a standard at it and stop typing those counts by hand. Production Entry's Reconcile form will then fill them in for you.
A standard has three optional slots: Good count, Scrap count and Rework count. Set any, all or none of them.
Use the gauge icon on a row to set or change the mapping, or fill the three pickers in when first adding the standard. Each picker lists that machine's own parameters, with its counters shown first and marked. Pick — Not mapped — to clear one.
Mapping only the good counter is normal
Most plants have a good-piece counter on the machine but count scrap by hand at an inspection bench. That's exactly what the three independent slots are for — map the good counter and leave the other two empty, and Reconcile will fill in the good count and leave scrap and rework for you to enter.
A few rules worth knowing:
- One counter can't be used for two of the three. The same parameter can't be both your good and your scrap counter — it would count the same pieces twice.
- Machine standards only. Counters belong to a machine, so a line standard has nothing to point at and the slots don't appear.
- Changing a mapping does not create a new version. Unlike the cycle time itself, the counter mapping isn't versioned — it records where a number comes from rather than what the standard is, so correcting it leaves the version history alone.
- A new version keeps the mapping. Superseding a standard with a revised cycle time carries the counter mapping across, so you don't have to set it up again each time you improve a standard.
The Counters column in the list shows how many of the three are mapped, so you can see at a glance which standards are set up for this.
You can skip the Reconcile step entirely
Once counters are mapped, Automation can record the counts for you once a day, without anyone opening Reconcile. It uses the same readings and the same plan-proportional split described there, and still subtracts anything already entered by hand.
A brand-new parameter may not be mappable straight away
Parameters are created in the configuration side of Enture and reach OEE through a regular sync. If you create a parameter and immediately try to map it as a counter, you may see:
That parameter is not available in MES yet. Parameter changes sync from the configuration service, and some types take until the next sync to appear.
That message means the parameter exists but hasn't arrived here yet, not that you did anything wrong. Some parameter types sync within moments; others wait for the overnight run. Try again later — the parameter itself is safe, and nothing needs re-creating.
When Performance can't be worked out¶
If a machine and product pair has no active standard, the OEE figures show Availability and Quality, and Performance is left blank with an explanation. This is the most common reason for a blank Performance.
A line needs its own standard
A machine standard is never used to measure a line, and vice versa — they describe different things, and a line's rate is not the sum or the average of its machines'. So if line OEE shows a blank Performance, add a standard scoped to that line; adding one for a machine on it won't do.
These standards also build your production plans¶
Beyond measuring Performance, cycle time standards are what the Machine Production Planner calculates a plan from — both the Calculate planned qty switch on a single plan and, more significantly, Auto Generate, which builds a whole week of plans with no typing at all.
Two consequences worth knowing before you run it:
- A machine with no machine-scoped standard generates nothing. Auto Generate names those machines rather than failing quietly, but they have to be planned by hand until a standard exists. Line standards are not used — Auto Generate plans machines.
- Every product a machine has a standard for gets planned on it. A machine with standards for three products has its shift row split three ways. If a standard is there for measurement only and that product isn't actually scheduled on that machine any more, superseding or deleting it keeps it out of generated plans as well.