Choosing the Right Machine Signals for OEE
Learn how to select the right machine signals for reliable OEE monitoring, depending on your production process, cycle times, and available machine data.
Why Signal Selection Matters
Before connecting a machine to Good Solutions, it is important to determine which signals are available and what information they provide.
Different production processes require different approaches to collecting data.
For example:
- A high-speed packaging machine may generate several production pulses every second.
- A machining center may take several minutes to complete one product.
- A continuous production line may provide a reliable running/stopped signal but no individual cycle pulses.
The correct signal configuration depends on how the machine operates and what you want Good Solutions to measure.
The objective is to collect reliable information about:
- Availability – When the machine is running or stopped.
- Performance – How much the machine produces compared with its expected performance.
- Quality – How much production is approved versus rejected.
Step 1: Understand Your Production Process
Start by answering these questions:
- Does the machine produce individual units or operate continuously?
- Does the machine generate a pulse for every production cycle?
- How long is a typical production cycle?
- Does one cycle produce one unit or several units?
- Is there a reliable ON/OFF signal indicating whether the machine is running?
- Can scrap and rework be detected automatically?
These answers help determine which signal types are appropriate.
Step 2: Choose How to Measure Produced Amounts
Option A: Cycle Signal
Use a Cycle Signal when the machine provides a pulse for each production cycle.
A Cycle Signal can register produced quantities and provide information about cycle times.
When production cycles are sufficiently short, the same signal can also support stop detection.
Example: High-speed packaging machine
- Typical cycle time: 5 seconds.
- One pulse for each completed package.
- One product per cycle.
A Cycle Signal can provide the information needed to count production and detect interruptions based on missing cycles.
Option B: Counter Signal
Use a Counter Signal when you want to count produced amounts separately from machine running time.
This is useful when the machine has longer production cycles or when running/stopped information is already provided by another signal.
Example: Machining center
- Typical cycle time: 180 seconds.
- One pulse per completed product.
- Separate ON/OFF signal indicating machine operation.
A Counter Signal counts completed products, while the Production Time Signal monitors whether the machine is running.
Step 3: Determine How to Detect Production Stops
Stop detection is an important part of Availability measurement.
Good Solutions supports two principal approaches.
Approach A: Stop Detection Using Cycle Signals
When a machine has short production cycles, the time between cycle pulses can provide information about production stops.
If the machine normally completes a cycle every five seconds, an unusually long interval without a cycle may indicate a stop.
The original Good Solutions machine signal documentation provides the following guideline:
For cycle times shorter than 60 seconds, a single Cycle Signal can be used for both produced amounts and running/stopped information.
This can be an efficient solution because only one signal is required.
However, the suitability of this approach depends on how consistently the machine produces cycle pulses.
Approach B: Stop Detection Using Production Time Signals
For machines with longer cycles, a separate Production Time Signal is generally more appropriate.
A Production Time Signal indicates whether the machine is running, independently of when the next product is completed.
The original documentation recommends:
For cycle times longer than 60 seconds, use a Production Time Signal for running/stopped information and a Counter Signal for produced amounts.
This provides more reliable information when the time between completed products is relatively long.
Important Consideration
The 60-second distinction is a guideline from the original machine connectivity documentation, not a universal technical limit.
The appropriate setup should also consider:
- Variations in cycle time.
- Whether the machine runs continuously or intermittently.
- How the machine indicates running and stopped states.
- The accuracy required for stop detection.
Step 4: Decide Whether Quality Signals Are Needed
Once produced amounts and running time are configured, consider whether quality information can also be collected automatically.
Scrap Signal
Use a Scrap Signal when the machine can identify rejected products.
For example, a rejection sensor on a packaging line may generate a pulse whenever a package fails inspection.
This can automatically register scrap in Good Solutions.
Rework Signal
Use a Rework Signal when the machine can identify products requiring additional processing.
For example, an inspection station may generate a signal when a product is diverted for rework.
Scrap Difference Signal
Use a Scrap Difference Signal when rejected quantities can be calculated from the difference between production counters.
This can be useful when products enter and leave a process at different points, but there is no reliable signal for every rejected product.
Recommended Signal ConfigurationsThe following examples illustrate common machine configurations.
| Production scenario | Recommended signals | Purpose |
|---|---|---|
| High-speed machine with short cycles | Cycle Signal | Produced amounts and stop detection |
| Machine with long production cycles | Production Time + Counter | Running/stopped information and produced amounts |
| Continuous machine with ON/OFF signal | Production Time | Running/stopped information |
| Continuous machine with production counter | Production Time + Counter | Running/stopped information and produced amounts |
| Machine with automatic scrap detection | Scrap Signal in addition to production signals | Automatic scrap registration |
| Machine with automatic rework detection | Rework Signal in addition to production signals | Automatic rework registration |
Note: A Production Time Signal alone does not provide produced amounts. Additional counting information is needed when production quantities are required for the intended OEE configuration.
Step 5: Configure the Signal Factors
Some machines produce several units during each production cycle.
Good Solutions must therefore know how many units each signal represents.
For example:
| Machine | Signal pulses | Units per pulse | Produced amount |
|---|---|---|---|
| Machine A | 100 | 1 | 100 |
| Machine B | 100 | 2 | 200 |
| Machine C | 100 | 4 | 400 |
The same principle applies to Scrap and Rework Signals, where a factor determines how many units are registered for each signal.
Incorrect factors can lead to incorrect production quantities and misleading performance or quality calculations.
Step 6: Validate Your Configuration
After configuring the machine signals in GS Desktop, verify that they behave as expected.
Check Production Counting
- Run a known number of production cycles.
- Compare the physical production count with the amount registered in Good Solutions.
- Verify that any configured amount factors are correct.
Check Running and Stopped States
- Start the machine and verify that the running state is registered correctly.
- Stop the machine and confirm that the stop is detected.
- Check that normal production cycles are not incorrectly interpreted as stops.
Check Quality Registration
If Scrap or Rework Signals are configured:
- Generate a controlled scrap or rework event.
- Verify that the correct quantity is registered.
- Confirm that the correct Measure Point and reason code are associated with the event.
Review the Results in Good Solutions
Use the Timeline and relevant Reports in Good Solutions Web to review the collected production information.
If results appear incorrect, return to GS Desktop and review the signal configuration.
Common Configuration Mistakes
Incorrect I/O input: The signal connection points to the wrong physical input, causing missing or incorrect production data.
Incorrect Measure Point: The signal is associated with the wrong machine or production line.
Incorrect amount factor: One pulse is interpreted as the wrong number of products.
Using cycle-based stop detection for long cycles: Normal production time may be mistaken for a stop.
Incorrect ON/OFF interpretation: The machine may appear stopped when running, or running when stopped.
Incomplete quality configuration: Scrap or Rework Signals may be connected without the intended factor or reason code.
Key Takeaways
- Select machine signals based on how the production equipment operates.
- Cycle Signals can provide both produced amounts and stop detection when cycles are sufficiently short.
- Longer production cycles generally benefit from separate Production Time and Counter Signals.
- Scrap and Rework Signals can automate quality data collection.
- Signal factors and Measure Point connections must be configured correctly.
- Always validate the configuration against actual machine behavior before relying on the resulting OEE data.