Fleet Fields

ID Fields

Fleet Rec ID *

The system-generated unique ID for the fleet record.

Fleet ID **

The user-defined ID for this record. The Fleet ID is made up of two fields: 1) a required, user-defined, numerical code and 2) a description or name.

Remember: When choosing a Fleet ID, the number must be unique in order to represent only one vehicle. Do not use a long, complex number, such as a vehicle identification number (VIN), or a number that is subject to change, such as a license plate. Instead, use a permanent number that may be easily seen when viewing the vehicle. Also, remember to retire the Fleet ID number when the vehicle is retired. The Fleet ID may be alphanumeric. For example, CAD12345.

* Required

* Must be Unique

 

Linking Fields

Building ID

Allows users to assign the vehicle to a specific building. The list of buildings comes from the Facility > Building > Building module.

Note: If the agency does not own the Facilities program, this field is not available.

Site ID

Allows users to assign the vehicle to a specific site. The list of sites comes from the Facility > Site > Site Inventory module.

Note: If the agency does not own the Facilities program, this field is not available.

Work Employee

 

Assigns an employee to the vehicle. The list of employees provided in this field comes from the Work > Work Flow Setup > Employee module.

Note: If the agency does not own the Work program, this field is not available.

Note: The vehicle will show up on the selected employee record's Issued grid.

WO Equip Code

 

Links a record in the Fleet Inventory to a record in the Work Flow Setup > Equipment module. This function allows the fleet vehicle to be used as a resource on a work order instead of as an asset. (A work order asset is the asset that is being worked on. A work order resource is an object being used to complete the work order.)

  • Enter the Equipment ID for the Work Flow Setup > Equipment record to associate it with this record or,
  • Enter a new number in this field to automatically create a matching record in the Work Flow Setup > Equipment module.
  • Press F5 within the field to automatically insert the Fleet ID.

Note: If the agency does not own the Work program, this field is not available.

 

Status Related Fields

These are fields on the fleet record that have to do with the assets operational status.

 

Operating Status

Indicates the status of the asset (e.g., operational, out-of-service, sold).

Note: Any record with a status code above 950 is considered out of service. Anything below 950 is considered operational. No PMs can be generated for nonoperational vehicles (those with a status greater than 950).

MTBF

The Mean Time Between Failure. Automatically calculated to display the Mean Time Between Failure. This is calculated by:

  1. Adding the Units Since Failure fields from the Status grid records.
  2. Dividing the sum by the number of Units Since Failure fields that were actually filled out (not by the total number of equipment status records).

Manuf MTBF

Enter the manufacturer's expected Mean Time Between Failure. This allows an agency to determine whether the vehicle needs to be replaced because it is failing more often than expected.

Email Notification Fields

These is a field on the fleet record that has to do with the assets operational status.

Operator Email

Indicates the operator's e-mail address. When an address is provided, the operator automatically receives related fleet notifications.

Inspection Related Fields

These are fields found on the fleet record that store information about inspections.

Last Inspection

The last date the asset was inspected. Automatically filled out from the Inspection Date field of the most recent inspection record.

Inspection Freq

The number of (date) units between inspections.

Inspection Freq Units

The type of date units between inspections.

Next Inspection

The date the next inspection should occur. This is calculated in one of two ways.

  • If the Inspection Freq and Inspection Freq Units fields are populated, the system will calculate this field automatically based on the Last Inspection date field.
  • If a user manually enters the Next Insp Date on the previous inspection.
  • If the Inspection Freq and Inspection Freq Units fields are filled out and the user fills out the Next Insp Date on the inspection the program uses whichever the closer date.
  • Example: An inspection was completed on 8/15/2014. The user filled out the Next Insp Date as 12/3/2014 but the calculated date is 8/15/2015. This field will display 12/3/2014.
  • Users can filter records by the Next Inspection Date to identify facilities that need to be inspected.

Fueling Related Fields

These are fields found on the fleet record that store information about fuelings.

 

Fuel Total Units

Calculates the sum of the Fuel Amount fields for all fueling records found in the Fueling grid.

Fuel Total Cost

Calculates the sum of the Total Fuel Cost fields for all fueling records found in the Fueling grid.

Total Fluid Cost

Calculates the sum of the Other Fluids fields for all fueling records found in the Fueling grid.

 

Cost Related Fields

Purchase Date

The date the vehicle was purchased.

Purchase Amount

The dollar amount of the vehicle at purchase.

Received Date

The date the vehicle was taken possession of.

Service Life

The number of years that the vehicle is expected to be used before being retired.

Full Dep. Date

The date that the vehicle will no longer be used. This date is auto-calculated as: Received Date + Service Life = Depreciation Date.

Salvage Value

The dollar amount for which the vehicle can be sold or salvaged.

Dep. Amount

The current worth of the vehicle, which is calculated as follows:

  • Determine the number of Months of Service Life (MSL):  Service Life*12 = MSL
  • Determine the date of Last Full Month (LFM) by noting the current date and determining the last day of the previous month. For example, if system date = 4/7/2005 then LFM = 3/31/2005; if system date = 3/31/2005 then LFM = 2/28/2005.
  • Determine the First Month of Depreciation (FMD) by looking at the Received Date. If the Received Date is during the first half of the month (14th and before), that month is used. If the Received Date is during the second half of the month, the system considers the next month the FMD. For example, a Received Date of 4/14/2001 would set the FMD to 4/1/2001. A Received Date of 4/16, 2001 would be set to 5/1/2001.
  • Determine the Months of Depreciation (MD): LFM - FMD = MD
  • Final calculation: [MD(Purchase Amount - Salvage)]/MSL = Depreciation Amount

Book Value

The remaining value of the vehicle, which is calculated as:

Purchase Amount - Depreciation Amount = Book Value

Replace Cost

The dollar amount necessary to replace the vehicle.

Hourly Cost

The price of operating the vehicle for one hour. This calculation adds all costs related to the vehicle.  That number is then divided by the total average hours to reach the Hourly Cost value.

Total costs/Total Average Hours = Hourly Cost

This field is calculated for all equipment with an operating status less than 950.  

Total Ins Cost

The sum of the Amount fields from all records in the Insurance Costs grid.

Evaluation Fields

These fields help agencies estimate the running cost of a vehicle and assess its life span based on running costs and recorded usage.  Some of these fields are entered by the user. (These fields appear in white in the module.) Other fields are calculated automatically by the system. (These fields are grayed out in the module.)

User Populated Fields

Calculated Fields

Tire Related Fields

These fields record how many rear tire slots are on a vehicle. This is required if you are going to attach tires to the vehicle.

# of Rear Axles

Indicates how many rear axles are on the vehicle. The program assumes there is one front axle.

This tells the tire tools how many axles to display.

Axle 1

Axle 2

Axle 3

Records whether each rear axle has 1 tire or 2 tires on each side. The program assumes that the front axle has 1 tire on each side.

Common Fields

Last Modified Fields

Last Modified By

The login ID of the last Lucity user to modify the record.

Last Modified Date

The date that the record was last modified.

 

Custom Fields

Lucity Web includes a variety of empty fields that an agency can customize to meet its needs. The number of custom fields available varies by module.

Custom fields can be designed as one of the following types:

Pick-List

Lets users select a value (code/type) from an agency-defined list.

Alphanumeric

Allows users to enter letters or numbers in any combination.

Check-box

Used to indicate yes/no or on/off.

Numerical

Accepts numbers only.

Date

Provides a pop-up calendar to enable the user to select a date.