Using the Equipment table for vehicles

If you do not need the full feature set of Fleet Management, you can enter the vehicles you are using as storage locations into the Equipment (eq) table. Having vehicles in the Equipment table means that, just as with any other piece of equipment, the vehicles can be subject to preventive maintenance and asset management tasks without much customization.

The process is as follows:

1. You first create an equipment record for the mobile storage units (vehicles or carts). See Adding Equipment .
2. You then define the mobile storage as a storage location, entering the Equipment Code in the Mobile Asset Code field. See Defining Storage Locations.
3. A supervisor or craftsperson can use the Maintenance Console to reserve parts from the mobile storage locations. See Estimating parts and storage locations.
4. Use tasks, such as the Manage Parts Inventory to track and mange parts for these mobile storage locations. For example, you could add parts as newly received if a craftsperson purchases parts and stores them in their vehicle. Or, you can put in a supply requisition to transfer parts to a vehicle if the parts are needed there. See Managing Parts Inventory.
5. Create preventive maintenance schedules for maintenance on this vehicle, just as you would for other types of equipment. See Define PM Schedules.

Using the Archibus Fleet Management application

If you plan to use the Fleet Management application either now or at a later date, it is best to manage the fleet as vehicles from the start. In this case, we suggest that you update your schema to include the Vehicles table, as well as adding a foreign key from the Parts in Storage Locations table (pt_store_loc_pt) to the Vehicle table. This would enable you to migrate to Fleet Management in the future with reduced data-migration requirements.

The following table shows the suggested fields to include in the Vehicles table when you update your schema.