Skip to main content

How to Configure Cycle Time Settings in Guidewheel

Learn how to set up and optimize cycle time settings in Guidewheel for accurate performance tracking, unit calculations, and troubleshooting.

G
Written by Grant M
Updated over 3 weeks ago

This guide is for production teams, machine operators, process engineers, and anyone responsible for configuring production data in the Guidewheel platform.


Cycle Time Calculations Overview

Guidewheel uses amperage peaks to determine cycle count and performance. Here's how the core metrics are calculated:

Day Summary

  • Total Cycles: Number of counted cycles within the selected time period.

  • Total Units: Calculated as Units per Cycle × Total Cycles in the Period.

  • Average Cycle Time: A real time measure, averaged over the selected time frame.

  • Performance: Calculated as Standard Cycle Time ÷ Average Cycle Time.


Selected Period Summary

Use the Selected Period Summary and the cycles graph to verify cycle accuracy:

  • Zoom in to 5m or 10m for better cycles resolution; default view is 1 hour

  • Green dots represent detected cycles.

  • Missing green dots suggest misconfigured thresholds or smoothing issues.

  • Graph overlays include

    • Min and Max height thresholds – Cycles will be counted if the amperage falls between these thresholds

    • Idle and Offline thresholds – as seen on the Uptime page

  • Extended Delay Filtering: Cycles that are 3× longer than the standard are excluded to avoid skewed data (e.g., due to long pauses or changeovers).

Cycle Time Settings

To adjust Cycle Time Settings, click on the settings cog on the right side of the “Selected Period Summary” display.

Standard Cycle Time

  • Default example: 15 seconds

  • Set this based on the machine's cycle time goal or standard

  • Extended Delay Filtering: Cycles that are 3× longer than the standard are excluded to avoid skewed data (e.g., due to long pauses or changeovers).

Units per Cycle

  • Configurable per machine or product.

  • Ensure this reflects the actual number of units produced per machine cycle, otherwise your Total Units calculation will be incorrect

Cycle Smoothing Mode (for Multi-Peak Cycles)

  • Use if a single production cycle generates multiple amperage peaks.

  • Configure a smoothing window (in seconds) to combine related peaks into one cycle.

  • Example: a cutting device has an upward and downward motion, this may be represented in two amperage peaks but represents one cycle.

Smoothing Window:

  • Smoothing Window: uses a running average of the last N seconds to “smooth” the cycles data and isolate a repeatable pattern

Algorithm Type:

  • Periodic (sine wave): Best for consistent, rhythmic patterns. (Most Common)

    • Auto Parameter Detection: Guidewheel automatically detects optimal cycle patterns based on amperage signals:

      • Identifies peak frequency and cycle period.

      • Sets minimum/maximum height thresholds (e.g., 100–400 kW).

      • Filters out peaks below the idle threshold to prevent false starts.

      • Toggle off to override these auto-detected values with manual settings for cycle patterns with greater irregularity

  • Square: Ideal for flat plateaus after sharp peaks. (Less Common)

    • Rising to Falling: use when the cycle has a clear rising edge on the left and falling edge on the right

    • Rising to Rising: use when the cycle has a clear rising rising edge on the left, but lacks a clear falling edge on the right


Extended Delay Setting

  • Click on Settings in the left side tool bar

  • Go to Production Settings, then Cycle Time Settings

  • Most plants leave this ON

Troubleshooting: Incorrect Total Units

If the total units seem off, check the following:

  1. Is the Units per Cycle value correct?

  2. Is the selected time period accurate?

  3. Do you need to enable cycle smoothing for multi-peak signals?

How to Validate:

  • Manually count production units; include scrap units in your count

  • Compare this to Guidewheel’s Total Units.

  • REMINDER: Guidewheel shows total output, not throughput (i.e., it includes scrap)

Did this answer your question?