While classic condition monitoring is usually used locally on individual machines, symmedia SP/1 monitoring can monitor many machines worldwide simultaneously. This creates completely new possibilities for machine manufacturers. These can now support their customers much more extensively in maintenance. They can gain knowledge about the condition and production behaviour of the machines and derive new, demand-oriented products from it. Availability commitments, productivity consulting (also: OEE Overall Equipment Effectiveness) or operator models can now be effectively supported.
Beyond data collection, the data can be individually calculated, aggregated and combined.
Suitable visualization tools are available for both live data and stored data: Live Data Logger, Plant App, Dashboard, OEE App and Reports.
Machine manufacturers learn from the centrally collected data, their customers use the machine data locally to optimize their production.
The data from machine use, such as output, duration, performance etc. enable innovative price models for the use of machines or their material requirements.
Action and escalation concept for certain events, indications of malfunctions or anomalies in machine operation.
The idea of condition monitoring is based on the collection of machine data. The symmedia SP/1 concept, specially designed for mechanical engineering, reduces the flood of data and converts relevant values into a uniform basic format.
In order to be able to monitor the condition of a machine, a wide variety of data must be recorded and evaluated. One of the greatest challenges of condition monitoring is to extract significant values from the flood of data: Because a machine first of all provides a very large amount of different data completely unfiltered. This " raw data " can, for example, come from the controls of a machine (then it is live data) or from databases (historical data and log files).
The first step is unification. One could imagine the flood of data from various sources as an orchestra in which each instrument plays according to its own internal rules. In the noise of this chaos the melody completely sinks.
The symmedia SP/1 Dashboard serves to illustrate the data collected from the machine in the monitoring (e.g. pressure, temperature, rejection rate, etc.) and, for example, to display it over time, compare it and put it into a logical context. For this purpose, the dashboard can be configured and assembled individually and role-based according to the needs of the user. Collected and calculated data is clearly illustrated in different graphics and diagrams. Deviations from the standard can be identified and displayed via previously defined threshold values.
Those who think of condition monitoring often already see the red flashing light of an alarm in front of their inner eye. In fact, the most common monitoring action is first and foremost the local recording of values, and if necessary with an extremely high data rate.
symmedia SP/1 creates monitoring diagrams from locally recorded and derived data on the machine, which, for example, display an overview of the current status or the last actions of the machine. This data can be viewed locally or centrally in the Live Cockpit (Dashboard).
The alarm is a core function of monitoring: It is triggered when a defined threshold value is exceeded or not reached and informs the operator and/or manufacturer of a machine about serious events.
Such an event can be a current problem or even a machine standstill. Ideally, however, this is information about an emerging problem.
symmedia SP/1 Monitoring offers different forms of notification, depending on how urgent the alarm is and to whom it should be sent. The simplest form of escalation is an email, SMS or push notification in the symmedia app. The highest level is the initiation of a Service Request to the manufacturer (which enables a connection back to the machine).
In addition to the escalation of alarms, individual rules can also be defined for the event that no response to an alarm has occurred within a certain period of time. For example, an urgent alarm could have triggered a Service Request, but the responsible service technician is on the road and did not notice the alarm. After the Service Request has not been processed for 30 minutes, it is automatically forwarded to a colleague and the service manager is informed: In this way, symmedia SP/1 Monitoring supports manufacturers in complying with service level agreements.
Neben der Eskalation von Alarmen können auch individuelle Regeln für den Fall definiert werden, dass auf einen Alarm innerhalb eines bestimmten Zeitraumes keine Reaktion erfolgt ist. Beispielsweise könnte ein dringender Alarm einen Service Request ausgelöst haben, der zuständige Servicetechniker ist aber unterwegs und hat den Alarm nicht bemerkt. Nachdem der Service Request 30 Minuten unbearbeitet geblieben ist, wird er automatisch an einen Kollegen weiter geleitet und der Serviceleiter informiert: Auf diese Weise unterstützt symmedia SP/1 Monitoring Hersteller dabei, Service Level Agreements einhalten zu können.
OEE reporting allows the presentation of the overall equipment effectiveness, i.e. the product of "quality", "availability" and "performance" in various views of the entire machine park.
Individual machines/components can be viewed in detail or entire machine parks in summary or comparative views.
Most important is the presentation of trends: am I on the right track or is my system efficiency declining?