Configure Production Time and Runtime Signals
Learn how to configure a Production Time Signal in GS Desktop so that Good Solutions can determine when a machine is running or stopped.
Overview
A Production Time Signal, also called a Runtime Signal, indicates whether a machine is running.
Unlike a Cycle Signal, which registers individual production cycles, a Production Time Signal monitors the machine's operating state.
It is typically an ON/OFF signal:
- ON: The machine is running.
- OFF: The machine is not running.
Good Solutions uses this information to identify running and stopped periods, supporting Availability calculations and production loss analysis.
Production Time Signals are particularly useful for machines with long production cycles.
When Should You Use a Production Time Signal?
Consider a machine that produces one part every three minutes.
If Good Solutions only receives a signal when a part is completed, it may be difficult to distinguish normal production from a machine stop.
A separate running signal provides information about whether the machine is operating between completed products.
A common configuration is:
| Signal | Purpose |
|---|---|
| Production Time Signal | Detect running and stopped states |
| Counter Signal | Register produced quantities |
Together, these signals provide information needed for monitoring machine availability and production output.
Before You Begin
Make sure that:
- The machine provides a suitable running/stopped signal.
- The signal is connected through an IoT device or another supported interface.
- You know which I/O interface and input carry the signal.
- The relevant Measure Point exists in GS Desktop.
- You have permission to configure Machine Data.
If you are using an IoT device, make sure it has been configured before creating the Production Time Signal connection.
Step 1: Create a Production Time Signal Connection
- Open GS Desktop.
- Navigate to Settings → Machine Data.
- Select Production Time Signal Connections.
- Click Create.
A new connection is created.
Step 2: Select the Machine Input
- Locate the I/O-Interface Input field.
- Click the connection icon.
- Select the correct I/O interface and input.
- Click Save and Close.
Make sure the selected input represents the machine's running state rather than a production cycle pulse.
Step 3: Connect the Signal to a Measure Point
- Locate the Measure Point connection field.
- Click its connection icon.
- Select the Measure Point that should use the signal.
- Click Save and Close.
- Save and close the signal connection.
Good Solutions now knows which Measure Point the running/stopped information belongs to.
Step 4: Configure Pulse Input Status
For IoT-connected running signals, an additional input setting is required.
- Return to Settings → Machine Data.
- Open RS-IoT/RSBlackBox.
- Select the IoT device containing the running signal.
- Click Open.
- Navigate to Inputs.
- Scroll horizontally until you find the Pulse Input Status column.
- Enable Pulse Input Status for the input used as the running signal.
- Click Save and Close.
Important: Pulse Input Status should be enabled only for running signals, not Cycle Signals.
Step 5: Verify Running and Stopped States
After saving the configuration, verify that the signal behaves as expected.
Test 1: Machine Running
- Start the machine.
- Confirm that the running signal is active.
- Check that Good Solutions registers the machine as running.
Test 2: Machine Stopped
- Stop the machine.
- Confirm that the running signal changes state.
- Check that Good Solutions registers the machine as stopped.
Test 3: Review the Timeline
Open the Timeline in Good Solutions Web and select the relevant Measure Point.
Review the displayed production activity and confirm that running and stopped periods correspond to actual machine behavior.
Understanding Running and Stopped States
A Production Time Signal provides the machine's operating state.
However, the signal alone does not necessarily explain why the machine stopped.
For example, the machine might stop because of:
- Equipment breakdown
- Material shortage
- Changeover
- Planned maintenance
- Operator intervention
Stop Reasons can be registered separately in Good Solutions to explain the causes of production losses.
Machine signals can also be used in configurations for automatic Stop Reason or Station coding, using the appropriate event-handling functionality.
How Production Time Signals Affect OEE
Availability is one of the three components of OEE.
OEE = Availability × Performance × Quality
A Production Time Signal helps Good Solutions determine how much of the planned production time the machine was running.
For example:
- Planned Production Time: 8 hours
- Running Time: 6 hours
- Stopped Time: 2 hours
Availability would be:
6 ÷ 8 = 75%
This simplified example assumes that all eight hours are included in Planned Production Time and that the running/stopped information is interpreted correctly.
The actual calculation also depends on production schedules and other Good Solutions settings.
Common Problems
The machine appears stopped when it is running
Check the input selection and how the machine's ON/OFF signal is interpreted.
The machine appears to run continuously
Verify that the signal changes state when the machine stops.
Running time is not registered
Check the I/O connection, Measure Point association, and Pulse Input Status setting.
Production amounts are missing
A Production Time Signal does not count completed products. Configure a suitable Counter Signal if production quantities are required.
Unexpected stops appear in the Timeline
Verify the incoming signal and confirm that the running-state configuration reflects actual machine behavior.
Key Takeaways
- Production Time Signals monitor when machines are running or stopped.
- They are particularly useful for machines with longer production cycles.
- The signal must be associated with the correct Measure Point.
- Pulse Input Status must be enabled for the relevant IoT running input.
- A separate Counter Signal is needed when production quantities must also be collected.
- Always validate running and stopped states against actual machine operation.