From machine alert to documented service action
Condition monitoring and remote support solve two different parts of the same service problem. Monitoring detects a change in a measured value, condition or threshold. Remote support then helps an expert and the person at the machine assess the real situation together. Connecting both steps turns a technical signal into a traceable service case.
ADTANCE PVM provides machine data, conditions, thresholds and alerts in the relevant asset context. ADTANCE Support adds live image and sound from the real working environment when required. Ticketing and Workflow record responsibility, checks, decisions and follow-up tasks. The case stays in one connected digital service process from the first signal to the next action.
Why the two capabilities belong together
Alert with machine context
Service and maintenance teams see more than a message. They can assign it to the affected machine, plant and relevant operating condition.
Visual check instead of guesswork
If measured values do not provide a clear diagnosis, the person on site can show the expert components, displays, sounds and work steps live.
Result with a follow-up process
Findings and decisions can move into a ticket, workflow, documentation, spare parts clarification or a better-prepared on-site visit.
What monitoring and remote support each contribute
Condition monitoring with PVM
PVM visualizes existing machine and sensor data, operating conditions, runtimes, cycles and defined thresholds. Deviations become visible and easier for service teams to assess.
View ADTANCE PVMVisual remote support
Support connects the person at the machine with a remote expert by smartphone, tablet, smart glasses, PC or camera. The expert sees the real situation and guides the check.
View ADTANCE SupportThe connected process
PVM provides the signal and machine context. Support adds the view from the site. Ticketing and Workflow turn the findings into an assigned, documented and traceable action.
How a PVM alert becomes a remote support case
PVM visualizes a relevant measured value, a change in operating condition or a defined threshold violation.
The service team reviews the signal, time, operating condition and affected machine to determine whether a clear action is already available.
Depending on the process, the deviation is assigned to a responsible person, a ticket or a digital workflow.
If data alone is insufficient, ADTANCE Support connects the expert with the person on site so both can inspect the real machine situation.
Checks, observations, the decision and the result are recorded in the service process and remain available for further work.
The case is closed or handed over to a workflow, spare parts clarification, further analysis or a prepared on-site visit.
Practical example: a deviation on a packaging machine
A horizontal flow wrapping machine provides condition and process values from its sealing station, film feed and pneumatic system. PVM can make visible, for example, that the sealing temperature repeatedly deviates from its approved range during production or that cycle times change. The alert alone does not yet explain whether sensors, settings, material, mechanics or another cause needs to be checked.
The service team first reviews the timeline, the operating condition and the affected machine. If this does not lead to a clear action, the case is assigned to the appropriate expert and a remote support session is prepared. The person on site can show the sealing tool, film path, displays or completed checks by live video. The expert combines these observations with the machine context already available.
The outcome is not an isolated video conversation, but a documented decision: check a setting within the approved specifications, complete a defined workflow, observe additional data, clarify a spare part or prepare an on-site visit with the information already collected. Existing safety rules, approvals and responsibilities for work on the machine remain unchanged.
Before the session
Signal, machine, time and previous trend narrow down the case and help select the right expert.
During the session
Live image, sound and guided visual checks add the real situation on site to the available condition data.
After the session
The result, open points and next task are recorded instead of remaining in personal notes or an isolated video call.
When is one module enough, and when does the combination help?
PVM on its own
Suitable when conditions and thresholds are clear and the responsible team can derive an approved action directly from the available data.
Remote Support on its own
Suitable when a specific incident, acceptance test or maintenance task is already known and the main need is visual collaboration with a remote expert.
PVM and Support together
Useful when monitoring detects a deviation but technical assessment also requires a view of the real machine, a component or a work step.
Add Ticketing and Workflow
Important when responsibilities, recurring checks, records and follow-up tasks need to be handled consistently across several people or organizations.
Start with one clearly defined service case
A pilot does not require the entire machine fleet to be connected. A recurring case with clearly defined data, responsibilities and a potential need for a remote check provides a more useful starting point.
Define one machine type, one recurring condition and the service or customer teams involved.
Use only values that can trigger a real check or decision. Relevant thresholds need technical approval.
Define who assesses a signal, when a ticket is created and under which conditions remote support is started.
Define required checks, result fields, permissions and handovers into existing service processes.
Evaluate response time, time to decision, cases clarified remotely, repeated alerts and better-prepared on-site visits.
ADTANCE modules for the complete process
PVM Monitoring
Provide machine data, conditions, thresholds, alerts and separate expert and customer views.
View PVMSupport
Connect experts with employees, technicians or customers at the machine by live image and sound.
View SupportTicketing
Handle deviations, responsibilities, communication and follow-up tasks as structured service cases.
View TicketingWorkflow
Document recurring checks, checklists, results and service actions in a consistent process.
View WorkflowThe modules can be introduced step by step and connected with customer, machine and plant information in the ADTANCE service platform. The use case Condition monitoring as a service explains how this process can become a sellable digital service offering.
Frequently asked questions about condition monitoring and remote support
What is the benefit of connecting condition monitoring and remote support?
Condition monitoring detects relevant conditions and deviations. Remote support adds a visual assessment of the real machine situation when required. Together they help teams assess signals, document actions and prepare follow-up processes more effectively.
Does every PVM alert automatically start a support session?
No. The service process defines which alert creates a ticket, starts a workflow or requires a remote support check. Responsible people decide on the next step based on the signal and machine context.
Does Remote Support replace direct access to a machine control system?
No. ADTANCE Support provides image and sound from the real working environment and supports collaboration with a remote expert. Technical remote access to control systems is a different category and can complement visual support.
Which data is required to get started?
Useful inputs include existing machine and sensor data such as conditions, runtimes, cycles, temperatures, pressures or approved thresholds. The key requirement is that a value can support a concrete service check or decision.
What happens if a case cannot be resolved remotely?
Findings, completed checks and open points can be transferred into a ticket, workflow, spare parts clarification or preparation for an on-site visit. The next person starts with more context.
Can the process be tested with a single machine?
Yes. A clearly defined pilot with one machine type, a small number of decision-relevant signals and an agreed response process is a practical starting point.
Want to take alerts all the way to a service action?
We will review a concrete machine case with you and show how PVM, Support, Ticketing and Workflow can work together.
Review a connected service process View service platform