Follow-up / small additional task
First, the change and its effect on the system need to be understood. Depending on the agreed scope, the adjustment may be part of follow-up support or a small separate service.
The project continues after startup
Warranty and support after commissioning
The system is running.
The support continues.
Handing over the program is part of the job. After commissioning, the next step is a clear transition into everyday production, with someone to turn to for technical questions.
POLJAKOVAUTOMATION
From project to ongoing support
- The logic is understood
- The handover is prepared
- A contact remains available
Wladimir Poljakov
Ongoing support
The connection to the project continues beyond its first successful start.
01
Handover is not the end of the project.
Each stage creates the foundation for the next. Familiarity with the system, documentation and agreed access help when questions arise during operation.
- Engineering
- Programming
- Commissioning
- Handover
- Ongoing support
After startup, the customer still has someone to turn to.
12months
of remote follow-up support
of remote follow-up support
For systems developed, programmed and commissioned by Poljakov Automation, one year of remote follow-up support is provided where suitable technical remote access is possible.
The exact scope and conditions are defined in the quotation or contract for the individual project.
- 01Month
- 03Month
- 06Month
- 09Month
- 12Month
CommissioningFurther cooperation by agreement
This line shows the support period, not a schedule of mandatory checks.
02
After startup comes everyday production.
Testing verifies how the system works. Production brings different loads, operator questions and process changes. It helps when the specialist already knows the installation's technical history.
- Clarify an HMI message or operation
- Refine a delay time
- Discuss a new product or recipe
- Review a sensor replacement
- Assist with a drive replacement
- Assess changed process parameters
- Investigate a fault arising later
The nature and scope of each request are reviewed first. These topics are not automatically warranty cases.
PLC/HMI, commissioning and operator documentation handover in published Case 003.
View the project ↗03
What happens after startup?
Choose a situation. This example separates follow-up support, fault investigation and a new engineering task.
Diagnostics / remote support
Messages, states and recent changes are collected first. The cause may lie in software, hardware or external conditions. Warranty relevance is assessed after the cause has been established.
System upgrade / separate task
A new function changes the agreed system scope. Requirements, effects on the existing logic and necessary checks are established first, followed by a separate quotation.
The task and scope are agreed first. Selecting a situation alone does not establish warranty coverage or a price.
04
Three distinct responsibilities.
Warranty, follow-up support and development address different needs. Their boundaries are agreed for the individual project.
01
Warranty
For my own completed workIf the cause relates to work I performed, the issue is addressed within the agreed warranty scope.
02
Follow-up support
Assistance after commissioningQuestions about the system, state analysis and smaller technical matters within the agreed support scope.
03
System development
New functions and capabilitiesAdditional operating modes, components and upgrades are treated as a new engineering task.
05
A clear scope before work begins.
What follow-up support may include
Depending on the project and agreement:
- Advice on system operation
- Remote diagnostics
- Analysis of messages and states
- Minor parameter adjustments
- Assistance with component replacement
- Software version checks
- Recommendations for continued operation
What is not automatically a warranty case?
The cause and its relationship to my work need separate assessment:
- Failure of third-party equipment
- A defective sensor, motor or drive outside my own supply
- Subsequent wiring changes
- PLC program changes by the customer or a third party
- A request for a new function
- New production requirements
- A mechanical defect
- Power supply or external infrastructure
You can ask for help with these matters too. The next steps depend on the cause, the work required and the project agreement.
06
Know which version is running on the machine.
A change should have a clear reason and a recorded result. When the next question arises, the actual system can be compared with its previous state.
Example change history
Initial startup
The starting software configuration after commissioning is recorded.
HMI wording clarified
An operator's feedback leads to a revised explanation on the screen.
Drive added
A separate upgrade: additional hardware and functions are agreed and tested.
Alarm logic refined
Agreed changes to the display and handling of messages are documented.
Fictional example, unrelated to any particular customer or operating installation.
Depending on the agreement, handover or updates may include:
- PLC project / backup
- HMI project / backup
- Parameters
- Documentation
- Change record
07
Close to the system. Even from a distance.
With suitable, agreed remote access, many questions can first be investigated online: PLCs, HMI, drives, communication, states and messages. Measurements or work on hardware may require someone at the installation.
Engineer
Your system
Agreed access
Remote access is arranged with the customer where technically feasible.
In Case 001, an engineering PG was prepared for remote service after commissioning.
View the project ↗08
Good support starts during commissioning.
A recorded starting point makes later support easier. Preparing a handover includes:
- Saving the agreed software configuration
- Recording relevant parameters
- Checking states and operating modes
- Checking how the system is operated
- Preparing handover documentation
I know the system because I helped develop it.
Wladimir PoljakovEngineering · programming · commissioningAbout my work ↗
The architecture, logic and project-specific details are already familiar. With later questions, that often helps get to the point sooner and choose a well-founded next step.
09
Straight answers about follow-up support.
How long does follow-up support last?
For systems developed, programmed and commissioned by Poljakov Automation, one year of remote follow-up support is provided where technical access is possible. Scope and conditions are defined in the project quotation or contract.
How do warranty and remote support differ?
A warranty matter concerns my own completed work and the agreed conditions. Remote support is a way to help with a technical question. It does not by itself determine warranty coverage or cost.
What happens if hardware fails?
The cause and affected component are investigated first. Failure of third-party hardware does not automatically make it a warranty case for my work. The possibility and scope of assistance are assessed separately.
Are new functions included?
New operating modes, components and additional HMI screens are treated as system upgrades. Requirements, scope and a quotation are agreed separately.
Can support be provided remotely?
Yes, where suitable agreed access and the necessary data are available. Some checks need measurements or a technician at the installation.
What if another engineer changes the software?
Explain what changed and when, ideally with the current project and a change description. The versions and effects are assessed first, then the next steps are agreed.
The project continues after startup
Questions after startup?
Or would you like to know in advance how support will be organized after commissioning? Let's discuss it before the project begins.
The task, access and support scope are clearly agreed.