The mobile app's AI Assistant generates answers from information stored in Spotilla. You can open it in the details view of a Spot, task or service request on both Android and iOS. The available actions depend on the view and the interface language.
Requirements
You need an internet connection and permission to access the information being processed. The Spot must be active, meaning it has not been deactivated. When using the assistant through a task or service request, you also need access to its associated Spot. The assistant does not extend your access permissions.
Your organization must accept the AI terms of use and enable AI feature enabled for mobile users. The service must also be available to your organization, with some of the shared AI quota remaining. The browser settings for administrators and managers are not required for mobile use. If necessary, ask an administrator to check the AI settings and usage limits.
Save any relevant changes before launching the assistant. The source data for a new answer is compiled from information saved on the server at the time of processing, using your current permissions. Availability is also checked again when processing begins.
Open the assistant and select an action
- Open the details view of the Spot, task or service request you want to use. Check the item's name.
- Tap the AI button with a face icon in the bottom right corner. On Android, it is above the bottom tab bar.
- Read the action names and descriptions in the AI Assistant window. Tap the action you want.
Selecting an action may start processing immediately. Not all actions open a separate source data form. If you see No actions available., no usable action was returned for that view and language. One missing action does not mean that all AI actions are disabled.
Select the source data
An action may use, for example, the Spot's basic information, tasks, service requests or history. The source data relates to the Spot associated with the open item: an action opened from a task view may therefore also process other information about the Spot. Do not assume the answer is based only on the open task or service request.
If a selection form opens, check the selection in every requested field and press Continue at the bottom of the form. The button becomes available once all required selections have been made.
- Android, Spot view: select each requested item yourself, even if there is only one option. Open the selection field and tap an option. You can filter the list by typing in the field; entering search text alone does not select an item.
- Android, task or service request: no separate selection form opens. The current task is used when a single task is required, and the current service request when a single service request is required. If the action requires other selections, it may stop with the message No selectable data is available. If the same action is available in the Spot view, you can make the selections there.
- iOS, Spot view: the required data is shown on a selection form. If there is only one option, it may be preselected, but check the selections and press Continue.
- iOS, task or service request: the current record is used if it is among the options. Otherwise, the only available option is selected automatically, or you are asked to choose from multiple options. When all data can be selected automatically, processing starts without a form.
If there are no options for a required selection, processing cannot start. Up to 100 options of each type are retrieved for the lists. Tasks and service requests are limited to that Spot and your access permissions, with the most recently updated first. A missing option alone therefore does not show that the information does not exist.
What data can the answer use?
The action determines which of the following data is sent to the AI. All Spot information or its entire history is not sent automatically.
| Data | Contents and limits |
|---|---|
| Spot basic information | The saved name, description, and the names and values of up to 50 Device Card fields, in field order. |
| Tasks and service requests | Up to 20 of the most recently updated records of each type that the user is permitted to access, without a separate status filter. Completed work may also be included. An action using a single record receives the selected task or service request. Comments are excluded from condensed data, and descriptions are shortened further. |
| Maintenance history from completed tasks | A separate dataset containing up to 20 completed tasks, ordered by completion time, newest first. It includes descriptions, completion notes and a limited number of comments, task product details and Spot spare part details, subject to access permissions. |
| Messages | Up to 20 of the most recently updated messages of the selected message type for that Spot, subject to your access permissions. |
| Data field history | The current value of the selected field and up to 20 of its most recent saved value changes. |
| Running machine hours | The Spot's current running machine hours reading and up to 20 of the most recent meter history entries. This data concerns the equipment's meter, not employees' time entries. |
Standard task and service request data includes up to five of the most recent comments per record, with a maximum of 100 comments retrieved in total. The corresponding limits for maintenance history data are ten comments per task and 100 in total. In addition, up to ten product associations per task are retrieved, with a maximum of 100 in total, along with up to 50 spare part associations.
The usual maximum text length in the data is 1,000 characters; condensed task and service request descriptions are limited to 256 characters. After a timeout, the service may use a fallback model and an even smaller dataset. The answer cannot confirm that the entire history has been examined. The record count in a task summary is also not the total number of all tasks for the Spot.
Wait for processing to finish
When the assistant shows Generating result..., keep the view open. The completed answer appears in the AI Result view. An error message means that no usable result could be displayed; it does not always mean that processing on the server has ended.
A user can have only one unfinished request started within the last 24 hours at a time, even across different items. Wait for it to finish or fail before starting a new request. The message AI unavailable or busy may relate to either this limit or service availability.
Closing does not cancel processing on the server
- Android: Close at the bottom of the waiting view, the cross at the top and the back arrow stop the app from checking for the result and reset the local processing state.
- iOS: Cancel at the bottom of the waiting view stops local checks for the result. The cross in the top right only closes the window and leaves the checks running. Opening the assistant again in the same details view restores the waiting view if processing is still in progress.
These controls do not send a cancellation request to the server. Processing that has already started may finish and consume the shared quota even if you close the assistant. Do not use closing as a way to clear the unfinished request limit.
Check and use the result
Read the completed answer in full; you can scroll the result area. Check that it concerns the correct Spot, and verify the source data used and the key details of the suggestion against the item's original information. Compare maintenance instructions with the manufacturer's instructions and your organization's practices before doing the work.
You can copy the result to the clipboard using the Copy text button below it. The button text is in English even in the Finnish version of the app. Close the completed result using Close at the bottom or the cross at the top.
Generating or copying an answer does not change the Spot, task or service request, mark work as completed or create a task template. If you use a suggestion to change an item's information, make and save the change separately using the normal editing process. Reopen the saved information and check the outcome. See, for example, Editing a Spot's data field in the mobile app.
Reusing and retaining previous results
Both apps may offer to reuse a result saved on the same device for one hour when you open the same item in the same view and select the same action and source data. Select Yes in the dialog to open the previous answer. This does not send a new AI request or increase AI usage.
To generate a new answer, select Reload again on Android or Reload again on iOS. The iOS button is shown in English even in the Finnish version of the app. New processing retrieves the saved source data again, and a successful answer consumes the organization's shared token quota. Usage is based on the amount of text processed, rather than just the number of requests.
Changing the source information does not by itself stop the previous result from being offered: the comparison is based on the item, action and identifiers of the selected data. If you have changed information, choose to generate a new answer to avoid using an old suggestion.
The result is not a permanent archive. Only the user's own requests created within the last 24 hours can be retrieved from the server, and cleanup removes older requests and their contents. This is a different time limit from the app's one-hour reuse period. Save a separate copy of any checked content you need.
If an action fails
If the AI button is missing or access is blocked, check your internet connection and ask an administrator to check that mobile use is enabled, the terms have been accepted, quota remains, and you have access to the item and its Spot. Changes to information or access permissions after the request was sent may also prevent an answer.
On Android, a network or server error stops checks for the result. You can return from the result retrieval error view using its Back to actions button. If loading the action list itself fails, close the assistant using the cross at the top and open it again. iOS continues checking after a temporary server error, but other errors may end the checks. You can close the iOS error view using Cancel at the bottom or the cross.
Resolve the cause of the error before trying again. Remember that local checks ending does not prove that the server request has ended: a new attempt may still be blocked by the unfinished request.