Monitoring
Equipment status, programs, values and active events in real time.
Kare Signal
Kare SignalMake automation data visible and usable
Bring robot, PLC and other automation status, faults, events, history and production data into one environment. Identify anomalies, capture data around an event, and investigate what happened before the issue.
Kare Signal
A data layer on top of existing automation
Kare Signal is built as a whole that fits the customer’s equipment. It collects status, events and process data from different devices, turns them into history, and makes the information usable in production, maintenance and automation.
Signal can also define events, capture the relevant signals around them, and transfer non-time-critical production and process data between systems.
Diagnostics
A shared event timeline, faults, trends and data captured around an event.
Production
Runtime, production volumes and measured cycle times from the same environment.
Data integrations
Defined data between devices and systems, managed centrally.
Monitoring and diagnostics
See what is happening now — and what happened before the issue
Live monitoring
See the device connection, operating mode, running program, key signals and active events in one view.
Events and alarms
Bring robot messages, PLC alarms, Event Engine events and other states onto a shared timeline — per device and across multiple devices. The summary shows the most frequent and longest-running alarms, and comments stay with the event.
Trends and historical data
Compare signals from multiple devices on the same timeline and open the context around an interesting event for deeper trend analysis.
Event Engine
Define the situations from which Signal creates an event. A trigger can be based on a signal change, a threshold or a device message. Events collect in the Events view — including multi-device cases where the trigger device and related devices stay distinct.
Snapshot and event recording
Capture selected values at the moment of an event, or collect signal history before and after it. From a recording you can move straight into deeper trend analysis.
Production monitoring
Track production volumes and cycle times per device, and compare utilization, runtime, faults and downtime across multiple devices in the same environment.
- See Live status and signals
- Identify Triggers, messages and alarms
- Capture Snapshot and event recording
- Investigate Timeline and trends
Data integration
Non-time-critical data from one system to another, centrally
Signal can transfer defined production and process data between devices and systems. The source, target and data are defined in Signal, after which the transfer happens centrally.
Example
KUKA Robot
JOB.nProductType
Kare Signal
Data mapping
Beckhoff PLC
MAIN.nProductType
Signal complements automation — it does not replace it
Kare Signal sits on top of the actual automation. Fieldbuses, safety, motion control and other time-critical or deterministic communication remain the responsibility of the PLC, robot and automation system.
Signal focuses on making data visible, storing history, diagnostics, capturing events, and system-to-system transfer that does not require fieldbus-level real-time performance.
Built around the equipment you have
Signal is connected to the environment the customer already has
Commissioning starts by choosing the equipment, signals, histories, events and integrations that are needed. The solution can begin with one machine, robot or cell and later expand around the rest of production.
- On-site installation
- On the customer’s production network
- Historical storage
- Browser / HMI
- Expandable
Equipment and automation
Signal is connected to the machines, robots, PLC systems and data sources whose information is needed.
Data from different equipment in one environment
Bring the relevant states, events and process values into the same view, regardless of manufacturer.
Views for the job
Use the data in a browser, on a production dashboard, or as part of an existing HMI.
Examples of current integrations
KUKA KRC
Robot status, operating mode, program data, system and user messages, selected KRL variables, events and historical data.
KUKA Fleet
AMR status, faults, battery data, operating data and history in the same Signal environment.
Beckhoff ADS
PLC signal reading, history, production monitoring and PLC alarms, plus combining operating and safety states from different machine or line areas into shared monitoring. Defined data can also be transferred through Signal.
OPC UA
A standardised way to bring device and system variables and process data into Signal.
In supported environments, Symbol Browser helps find device variables and add them for monitoring without entering addresses by hand.
Other environments can be implemented according to the use case and the equipment in place.
What data from your equipment should be made visible?
Signal can be built around one robot, machine or cell and later expanded to the rest of the equipment.
- On-site installation
- On top of existing automation
- Expandable with the equipment