# WARM: Wearable AR and Tablet-Based Assistant Systems for Bus Maintenance
## 3 Solution Approach
### Tablet-Based Solution  
A new graphic user interface has been developed to gather all the controls and information required by the WARM system. The participation of the mechanics in the design of the interface showed to be fundamental for the success of the subsequent tests. The whole flowchart associated with the Tablet application is shown in Figure 2.  
The navigation through WARM has been done in a simple and intuitive way so that the operators do not spend too much time to fill in the maintenance lists. Once the user has logged into the system (Figure 3a), the next screen (Figure 3b) offers the operator the following options are shown:  
* Capture multimedia, to take photographs and record videos to describe new incidences found during reparations or prior to begin with them.
* Select a bus to begin/continue the work orders (WO) associated with the user logged in, which opens the corresponding checklist.  
The \"Maintenance sheet\" screen (Figure 4) will load the list of the checks required for the type of maintenance that will be performed on the vehicle (ITV, M1, M2... ). The user can see the fields that have not yet been evaluated with a red background and clicking on them they will be verified and change their background color to white with a green verification symbol. The user must mark the field to record that the revised component works correctly or leave it unchecked to warn otherwise.  
Figure 1: Description of the Wearable Augmented Reality (AR) Maintenance Assistant System (WARM) featuring its integration with the GIM system, already deployed in DBUS company. Red boxes refer to new developments; blue boxes and lines refer to the implementation of the standard EN13149 (new development as well); black boxes refer to previously available features.  
Figure 3: WARM system (Android mobile app). Images corresponding to the login (**a**) and the main menu (**b**).  
Figure 2: Flowchart for the Tablet application.  
In the event that an item is not functional, and additional information needs to be attached, the user has to press and hold the item in the list and the \"Notify Incident\" screen (Figure 5) will show up. This last screen allows you to upload an image or video previously taken, to capture a new photo, video or audio, or to annotate a comment to enrich the description of the incident. A field that has received an incident notification will appear on the screen with a blue background.  
Clicking on the \"Send file\" button on the \"Maintenance sheet\" will mean that the maintenance of the vehicle has been completed and it will cause the application to generate a PDF. The complete maintenance information (Figures 5(b) and 6(b)) that will be attached to an email, also generated by the application, that will be sent to the server and the person in charge of the vehicle maintenance.  
Figure 4: Maintenance sheet M1 with unedited field (**a**) and maintenance sheet M1 with incident notification (**b**). Red background marks not yet started tasks and blue background marks reported tasks.  
Figure 5: Notify incident screen (**a**) and notify incident screen with attached image (**b**).  
Figures 6 and 7 compare the current reports produced by DBUS mechanics (handwritten document) with the digital reports produced by WARM (shown in pdf format). Notice the picture complementing the annotations of the mechanic.