Note: This is an updated version of the FAQ based on Car Maintenance v 2.10.
When the application is first started, there are already several pieces of data pre-set for the user:
All those prepackaged values can be changed before any other operation is executed. We urge all users to customize the Vehicles and Payment Info records with ones having significance for them.
The first step after the application starts is to enable global settings.
The maintenance operations are based on three parameters – time, engine hours and mileage. If the vehicles in the fleet are all using kilometers do not check “Maintenance based on Miles”. If you cannot monitor the engine hours do not check “Maintenance based on Engine Hours”. If you want to be notified BEFORE the maintenance operations are due then check “Allow notifications before due date”.
From Home screen select “Vehicles” option. The screen below will show a short list of the managed vehicles.
One of the important restrictions about vehicles is the license plate has to be unique. The users can specify if they want to monitor maintenance operations based on Engine Hours and the type of odometer (in Kms or Miles). The expiration date for vehicles or Payment Info records are used to notify the user before due date.
For the free version of the applications there is a maximum of two vehicles allowed.
In the “Others” tab there are three important reference data:
For all those tables, the name of each entry has to be unique.
The pictures below shows a situation where just by changing the notification values the status of the operation is different (from state “after notification” to state “in progress”).
The concept of having a notification/warning zone is explained below.
The first three screens are showing how updating the mileage is changing one operation from “in progress” to “notification” state.
The following screens are showing how increasing the mileage over due value (12000 kms) the maintenance operation is switching to “overdue” state. The change is reflected on the main screen (Overdue row is showing one, Notifications row is showing 0) and on the Maintenance screen (the icon is changed to a red triangle).
Following the scenario played previously, if the user choose to close an operation (after it is executed) the system does not allow it because the due value (12000 Kms) is lower than the current value of the odometer (12200 kms). The only option is the enter the correct current value (which should be higher than 12200 kms).
Once the operation is closed, it will show in the Maintenance Screen when “Past” radio button is selected.
Only after the operation is closed the user can attach an expense to it (see the screen below). By selecting Payment Info, the new screen allows to enter the specific information regarding the expense.
After saving the expense information the initial screen about the maintenance operation reflects the change:
At any time the user can add expenses. The only requirement is the expense date cannot be scheduled in the future.
The first screen below show a one time expense. The second screen shows the option to define a recurring payment (which can be dated in the past). The application will fill-up the dates between starting of the payment and current date twice per day (refresh process runs twice per day).
The recurring payment is recognized by the two curbed arrows icon (as in the last screen show above).
The Reports screen can be selected from the drawer navigation window (swipe from left to right on the screen).
For certain reports (summary type) there is a chart available to display. Below there is an example of Expenses By Category, report and chart). For the free version the periodical summary reports and the possibility to email them are not available.
There are two upgrades with Car Maintenance: