Service specifications of mobileX-ServicePlatform

The resource management is called up via the settings. The following resource types are available for creating a new resource:

Customers can be created, displayed, edited and also deleted again. Orders can subsequently be created for these customers. Additional objects can be created for customers, in particular equipment (product with the equipment product group), contacts, locations and documents.

Goods and services intended for sale can be created and managed centrally under the "Products" category in the settings. Currently, it is possible to differentiate between the "Material", "Equipment", "Work time" and "Flat rate service" product groups. Depending on the respective product group, a product is used within different ServicePlatform contexts.

A new order can only be created with a customer reference. The basic data is entered in the form. The release button is activated by default. This means that the order and any associated operations are immediately released for scheduling. An external reference for the order can optionally be entered. This can, for example, be an external order number for a third-party system. Additionally, the operation for the order can be recorded. An order can also be linked to the equipment it refers to. Data such as alternative addresses, appointment periods, preferred dates and attachments related to the order can also be recorded in this section. This module is completed by attributes that can be added to the order, as well as an order history.

Precise scheduling of an operation involves assigning a fixed date with time, duration and travel time as well as a resource. The executing resource, work duration, travel times, start date and explicit end of planning can all be defined. By defining a start time along with an additional explicit end of planning, it is possible to specify the duration of resource utilisation for the respective operation in the scheduling. The period may differ from the duration of the actual work required. In such instances, the operation bar on the planning board indicates the period between the start and the explicit end of planning. For example, operations spanning multiple days can also be considered for resource scheduling. Travel times (arrival and departure) can be specified in hours, with decimal values representing industrial minutes allowed. On the planning board, travel times are displayed separately on the operation bar.

Order confirmations recorded by the technician via mobileX-CrossMIP can be viewed or downloaded in the "Confirmations" tab within the order. Currently supported confirmation types include:

Attribute definitions allow users to structure and organise their data in a variety of ways.

The planning board provides a graphical overview of planned operations and resource absences for a specific period. The desired time display can be set in the upper section of the planning board, while the left-hand section shows resources accessible to the user based on their respective authorisations. Additionally, users can filter the displayed resources using an attribute via the search function or group them within the planning board. On the planning board, users can select the calendar display mode they prefer. They can choose between one-day, two-day, weekly and monthly views.

The mobileX-ServicePlatform offers mobile users the option of using the "Daily report" function in mobileX-CrossMIP to report the actual working times for both orders and non-order-related activities. These times can be analysed and exported for individual resources on a daily basis within the web application.

Instead of manually creating resources and customers in the mobileX-ServicePlatform, they can also be conveniently imported into the system via the file interface. This allows multiple master records to be imported at the same time. The import function can be called up via the hamburger menu in the "Settings".

The dashboard represents the main menu of the mobile client, offering an overview of the number of orders, received messages and the number of unprocessed sync messages (both incoming and outgoing).

The quantity of new messages available to the technician or of those recorded locally but not yet synchronised is displayed here. The message section provides additional details, including the content of push messages, if applicable. The sync button enables technicians to initiate the process of receiving/transmitting data.

mobileX-CrossMIP supports push messages to notify technicians about changes (e.g. new orders). The respective native push system of the operating system is used for this purpose. The exact behaviour of push messages, including when and how they are displayed, may vary depending on the operating system.

The relevant details contained in the product standard are displayed to users here. This allows them to obtain information before or during an operation. To change the status, users click on the asterisk = New status symbol and select the new status, i.e. rejected, travelling, on site, interrupted, technically done, done.

The "Info" tab of an operation shows all the confirmations that have been previously submitted. The following confirmation types can be recorded:

All order-related and non-order-related times of a day are recorded in the daily report. Breaks can also be added here by selecting a gap or entering a new time. At the end of the working day, all the times are checked, and the recorded breaks are booked. Breaks can also be booked from the dashboard. The daily report also offers a graphical representation for an overview of the distribution of the different types of time.

A service report can be generated for an order once all relevant confirmations have been recorded. This service report is then provided in the web frontend of the office staff.

If the mobileX-Plugins module has been purchased, customer-specific forms or functional extensions can be provided to users within the app. They are often used for documentation purposes or as checklists.

The settings contain information about the app, the link to the legal notice, and settings that the technicians can make locally.

Under "Settings", users can access the "Upload diagnostic data" function, allowing them to transmit information to Support and Development in the event of errors. This takes place automatically in case of a critical fault or can be manually triggered by the technician. By default, the local database and the log files are compressed into a zip file and uploaded to the server, where they are accessible in the portal. Optionally, local documents can also be uploaded. If the server is not available, the zip file can alternatively be stored locally using "Share diagnostics" through the operating system’s "Share system" or sent via email, for example.