Naming Convention for Customized Reports, Zones, Rules, etc.

Because there are 19 cabinets in the State Fleet Management (SFM) group, we have adopted a standard naming convention to be used throughout the MyGeotab system. We ask that all of our users adhere to this naming convention when creating custom reports, zones, rules, or any other available element or function that is specific to their agency. This will allow SFM staff to easily identify the agency to which the functions belong.


IMPORTANT REMINDER: Please note the URL to access the Geotab system has changed since this webinar was recorded. The correct URL to access SFM's MyGeotab database is https://gov.geotab.com/coloradofleetmanagement/. Remember to bookmark this!


Generic Naming Convention for Zones, Reports, Rules, etc. 

See image in next section for the naming convention specific to EV Charging Home Reimbursement.


Always label your elements with your cabinet's abbreviation, followed by " - ".


Additional specific expectations are required for zones that are being used for EV Charging reporting. 

Example of naming convention for a customized report showing DPA as the cabinet code, MOTOR POOL as the Dept and Unit, and Vehicle Efficiency Score as description. This example shows the cabinet abbreviation for Department of Personnel & Administration, which is "DPA", followed by a space, a dash and another space. The remaining report name is "MOTOR POOL" identifying a child department of DPA, and finally the actual description of the report: "Vehicle Efficiency Score (Last Month)".

Naming Convention for EV Charging Home Reimbursement Zone Type

This image displays an example of a zone type name for agency-level EV Charging Home Reimbursement program naming example with DPA as the Cabinet/Agency Code and Home Charging. Thee example begins with the cabinet abbreviation for Department of Personnel & Administration (DPA) followed by a space, a dash and another space. The end of the name is exactly "Home Charging" indicating the purpose of the type.

Naming Convention for EV Charging Home Reimbursement Zone

This image shows an example of the zone naming convention for a charging zone. The example begins with the cabinet abbreviation for Department of Personnel & Administration (DPA) followed by a dash. An arbitrary name for the zone that does not include PII, but which will be associated with billing coding follows the dash, it reads "EMP A". Finally, the required tag for home charging zones is the "~" tilde character, added at the end of the zone name to allow our billing automations to identify this zone for reimbursement.

Vehicle Naming Convention

Although agency Group Administrators are not able to rename their assets, it is still beneficial to understand the components of our asset titles in MyGeotab. SFM has established a specific naming convention for vehicles in MyGeotab.


You can view this webinar (Vehicle Naming Convention in Geotab), which explains this in more detail.

This screenshot shows a table indicating the components of the asset names: First, license plate number, followed by a space, a dash and a space; second, the year, make, and model of the vehicle, followed by a space, a dash and a space; third, the asset ID number followed by a space; fourth, a tag beginning with an asterisk ("*") indicating the asset's powertrain: NEV for non-electric vehicle / EV for electric vehicle / PHEV for plug-in hybrid vehicles; and finally another tag beginning with an asterisk ("*") followed by a two-character body type code


Things NOT to Include in your Element Names

There are several characters that SFM uses downstream to identify important asset information when processing the large amounts of data both within MyGeotab and in will interfere with the way report processing works that you should be mindful not to include when applying names to zones, assets, rules or anything else within MyGeotab:

  • Do not include the comma symbol: " , "
  • Do not include the dash symbol: " - "
  • Unless your zone or asset name meets the specific criteria above, do not include the asterisk or tilde symbols: " * " or " ~ "