![]()
Instandhaltungssoftware für Industrie, Versorger und Windkraft
How can technical assets such as meters, inverters, or other components be replaced in a structured way while being fully documented?
In GS-Service, the replacement of an existing object can be managed through a standardized task. The field technician records all relevant information on the asset to be removed and the new asset to be installed directly on site. The actual creation of the new asset object is then carried out in a controlled manner by the back office (foreman, supervisor, operations engineer, shift/team leader, etc.).
When a device is replaced, the technical information is first documented as results within the replacement task. Once the work is completed, the data can be automatically transferred via a macro to create the new asset object. The previous asset remains historically traceable and can be moved to the archive of its former installation location.
This creates a clear separation between field service and the back office in the office, workshop, and municipal yard, while establishing a consistent and traceable data basis in the maintenance system.
Replacing technical assets requires the reliable recording of extensive information. This includes, for example, serial numbers, meter readings, technical parameters, setting values, and condition data. If this data is recorded manually or in different places, transmission errors can occur, making it harder to trace the replacement afterward.
The GreenGate solution maps the entire replacement process through a standardized task. The field technician receives the task for the on-site assignment and first documents the data of the asset to be removed. The physical replacement is then carried out, and the newly installed asset is recorded with its relevant technical data.
The data of the new object is initially saved as results within the replacement task. Once the work is completed, the back office reviews the details and technically closes the task. A macro can then automatically create a new asset object and populate it with the previously recorded information.
The removed asset is not overwritten with the data of the new device. It remains historically traceable and, depending on the individual system configuration, can be deactivated and moved to the archive of its former installation location.
This standardizes replacement processes, reduces master data errors, and transparently documents the history of technical systems and components.
The solution is suitable across industries for organizations in which technical assets are regularly replaced, maintained, or renewed.
A typical example application is the replacement of an existing meter. In the existing object structure, an installation location for the meter already exists. In addition, a defined area is available for managing the life cycle records of previously used assets.
For the planned replacement, the field technician is provided with a corresponding task. Within this task, the individual activities and information of the replacement are documented.
First, the data of the meter to be removed is recorded. This may include, for example:
The physical replacement of the meter is then carried out on site. After installation, the field technician records the data of the new asset. This may include, for example:
The information for the newly installed meter is initially saved within the replacement task. This means the field technician does not need to create a new asset object in the system on site.
After the on-site assignment is completed, the task is reviewed by the back office and technically closed. As part of this closure, a macro can automatically generate a new asset object. The information previously recorded in the task is then transferred directly into the properties of the new object.
The previous asset remains traceable as a historical object. Depending on the process definition, it can be deactivated and then moved to the designated archive area of its former installation location.
This approach ensures that the new asset is managed as an independent object while the history of the previous one is preserved. At the same time, the information recorded on site is transferred into the master data of the new asset without the need for repeated manual entry.
