Incidents can be recorded for the service management and maintenance objects registered in the ERP system. The descriptive data of the object is imported online. The incident can be saved after entering further information (description texts, incident type, damage codes, damage type, damage cause). An incident number is assigned.
There are many options available for processing and reporting on incidents registered in the system. All functions provided by the ERP system are supported — edit, reset, reactivate, preliminary troubleshooting and resolution. Incidents can be enhanced with further information (text, images). All additional information is stored in the document management system.
Planned maintenance is triggered based on actual values (measured values, counters, status information). A planned value can be stored for counters over a certain period of time (e.g. scheduled mileage per year). This is used by the event monitoring system to determine the anticipated due date (planned date) for an event.
Events are used to define planned, periodic or preventive service management measures. In the course of preparatory service management, events can also specify activities in advance. If an event has a cycle in which different activities must be performed each time, the various activities are defined as event packages and their mandatory order is defined as a package sequence belonging to the event. This method can be used to trigger cyclic activities or activities that must be performed in succession during consecutive maintenance sessions (e.g. minor inspection and major inspection alternately every 15,000 km). Due dates for planned events are determined by monitoring elements. Event processing supports early implementation (before the due date) and recording of actual values. Postponement of due dates and regular implementation are displayed in the ERP system.
Service objects (e.g. machines, equipment, vehicles) often consist of many components. During cyclical maintenance or even unplanned incidents, it may be necessary to replace asset structure components. In addition to direct replacement, the single steps "Removal" or "Installation" can also be performed. A serial number can be recorded when replacing or installing components. The application provides the option of displaying context-related journals. These are, in particular: the incident journal, actual value journal and event journal. The display can be limited using suitable filtering.
It is often difficult to record the presence and absence times for field service employees promptly. Hand-written records are often used and transmitted to the responsible bodies within the company in various ways. All of this is an additional burden and can cause errors in this sensitive area. The stamps of mobile employees can be identified in PSIpenta Personnel Time Management. They are processed according to the same rules as stationary stamping. Employees are identified using their personnel or identity card number.
Arrival/departure and departure with reason stamps are supported. Absence reasons correspond to those in the back end system. In this way, consistent processing of both stationary and mobile stamping is guaranteed.
The technological basis of the applications are web-based hybrid technologies (HTML5, CSS3, Java Script). This ensures that widespread mobile platforms are supported and the platform-specific look and feel is maintained. In addition, the existing hardware and sensor systems (camera, GPS etc.) can be used. The online connection of mobile applications with the ERP backbone ensures that the data in use or the transmitted data is always up-to-date and consistent. It also guarantees the traceability of all activities and the documentation of changes to technical systems.