Service events

After selecting the 'Events' action from the main menu, the user is presented with a list of service events that are assigned to him. This allows us to quickly check and act on events for which we are responsible.

Filters allow you to quickly find a filter. We can use the general search box that searches through comments and resource names, or select the filter button and display a detailed filter.

When you open the filters, additional controls appear that allow you to filter service events as expected.

Filters available:

Selecting the 'For all' option displays all active reports.

After selecting any event, we are redirected to the details page of a given service event.

The service module has an integrated map view. We can go to it via the globe button in the main view.

The view shows a map (or plant plan) with service events marked on it in their geolocation.

To add a new event on the map, select the (+) button and then select a point on the map. After selecting this point, the event registration window opens with the geolocation already filled in.

Further adding the event as usual, as in the case described earlier.

The service event detail view shows information about a given service event. The common information includes information about the related resource affected by the event, description, type, number (unique identifier), creation dates, assigned person and a list of comments that were created during the event handling.

The main actions allow you to add a new comment and add a new service (explained later). Shortcuts allow you to display a list of services added to a given event and a list of photos/photo notes created for a given event.

If the ticket currently being viewed has the option of changing its status to another, the system additionally displays quick actions to be performed. All allowed state changes appear in the list. Selecting any state will AUTOMATIC select that state and save the user who made the change.

Selecting the '(+) Comment' action allows you to add a comment to the event.

In an action, it is possible to describe the actions we perform, but also to change the assignment of the event to another person and to change the state in which the event is located. If the state requires saving an electronic signature, the Signatures button will be active. The 'Attachments' tab allows you to send attachments. They will be included in the list of all service event attachments and the comment will be extended with information about adding files.

Choosing to create a new event opens a window where you select the device (resource) to which the event applies, the type of event, the description, and select the person assigned to the event.

The window allows you to specify additional elements such as location, geolocation, type, status, description, assignment to the order, etc.

The list of resources allows you to filter resources and select the appropriate device, to assign an event to it.

In the 'Attachments' tab you can add photos or other related files to the report. The 'Client' tab, active only in the multi-client version, allows you to enter identification data and service information.

After selecting the list of users, a window appears where you select the person to whom the event will be assigned. He or she will be notified that the event has been created (with the appropriate event configuration in the extended application).

The services mechanism is used to enter additional information about the external costs of an event. The service categories are definable and can be, for example, external invoices, warehouse documents or hours worked on an event. We define the types of service categories in the extended application. In this view, we select only the type of service and enter information about costs, etc.

Once a service is entered, information about it is available in the list of services from the event.

After selecting the 'Events' action from the main menu, the user is presented with a list of service events that are assigned to him. This allows us to quickly check and act on events for which we are responsible.

When you open the filters, additional controls appear that allow you to filter service events as expected.

Filters available:

After selecting any event, we are redirected to the details page of a given service event.

The service event detail view shows information about a given service event. The common information includes information about the related resource affected by the event, description, type, number (unique identifier), creation dates, assigned person and a list of comments that were created during the event handling.

The main actions allow you to add a new comment and add a new service (explained later). Shortcuts allow you to display a list of services added to a given event and a list of photos/photo notes created for a given event.

If the ticket currently being viewed has the option of changing its status to another, the system additionally displays quick actions to be performed. All allowed state changes appear in the list. Selecting any state will AUTOMATIC select that state and save the user who made the change.

Selecting the '(+) Comment' action allows you to add a comment to the event.

action, it is possible to describe the actions we perform, but also to change the assignment of the event to another person and change the state in which the event is located.

Access to service protocols in the mobile view is possible through the main menu Protocols.

By default, after entering the list of protocols, only protocols assigned to the currently logged in user are displayed, which are not closed.

After selecting the filter button, additional options appear that allow you to additionally limit/extend the presented data. Selecting Show Closed will display the protocols assigned to the user that already have the complete flag. Selecting For all will display the logs for all users on the system. Selecting a counterparty will limit the protocols to the selected counterparty only.

After selecting any protocol, the execution details of that protocol are displayed. They contain all information entered during execution of this protocol.

In the case of not closed protocols, we have the option to Edit the protocol or mark the protocol as completed Completed. After confirming completion, the protocol is finalized and the available functions in the protocol change.

After approval of the protocol, the functions Check become active, which calls the window for checking/accepting the protocol, and Report, which allows you to generate a report from the protocol

In the service log details view, you can follow the log check procedure by the person coordinating such work. Calling it displays a window with the possibility of entering data and marking the status of the protocol execution.

The protocol can be generated as a PDF report. All data entered into the protocol appears in the report. The report can be saved locally or sent by email.