Snowflake Reader Account Views A-M

A unique identifier for this address, used within Fleet and the Analytics server alike. Use ADDRESS_ID for joining or grouping by this view.

A two-character code for the address's country.

The country of the address.

The region of the address.

The state of the address.

The city of the address.

The street of the address.

The postcode of the address. Applicable in countries that use a postcode.

The ZIP code of the address. Applicable in the United States.

The suburb of the address.

In the United States the zone can be US-North, US-South, US-East, and US-West. Outside the United States the zone is usually empty.

A unique identifier for this app_event, used within the Analytics server. Use app_event_key for joining this view.

A unique identifier for this app_event, used within Fleet. Use APP_EVENT_ID for grouping by this view.

A unique identifier for the driver, used within the Analytics server. Use DRIVER_KEY for joining this view.

A unique identifier for the event_type, used within the Analytics server. Use EVENT_TYPE_KEY for joining this view.

A JSON object that contains all the unparsed data for the event.

Name of the mobile app.

Version of the mobile app.

The time of the event.

Additional information for the event.

A unique identifier for the video_course, used within the Analytics server. Use VIDEO_COURSE_KEY for joining this view.

Device identification information.

The time, in UTC, when this app_event database entry was created.

The time, in UTC, when this app_event database entry was last updated.

A unique identifier for the condition, used within the Analytics server. Use CONDITION_KEY for joining this view.

A unique identifier for the condition, used within Fleet. Use CONDITION_ID for grouping by this view.

The name of the condition, as defined by the creator in Fleet.

The type of condition.

The user id of the user who created the condition.

The severity index of this condition.

The severity color of this condition.

The period of time the condition must be satisfied before it triggers an alert.

Whether or not the condition should be triggered using the aggressive criteria.

The group type for this condition.

The reason why this condition might have been disabled.

Whether or not this condition is available to include on a Scorecard in Fleet.

JSON that contains properties relating to how the condition is handled.

Whether or not this driver database entry is current or has been replaced by a newer copy.

The time at which this condition entry was created, in UTC.

The time at which this condition entry became historical, in UTC.

The time, in UTC, when this entry was last updated.

A unique identifier for the vehicle, used within Fleet.

A unique identifier for the vehicle, used within the Analytics server.

A unique identifier for the device, used within Fleet.

The date at which the device was linked to the vehicle/unit.

The date at which the device was unlinked from the vehicle/unit. Null value when the device is currently linked.

The time, in UTC, when this database entry was last updated.

A unique identifier for the device, used within the Analytics server.

A unique identifier for the device, used within Fleet.

The serial number of the device.

The SIM number of the device.

The IMEI number of the device.

The MDN number of the device.

The wireless provider the device connects to.

The technology used to communicate with the provider.

Whether this vehicle database entry is current or has been replaced by a newer copy.

The time at which this entry was created, in UTC.

The time at which this entry became historical, in UTC.

The time, in UTC, when this entry was last updated.

A unique identifier for this particular form instance xml.

A unique identifier for the form instance that this form instance xml belongs to. A form_instance_id can have up to three different form_instance_xml_ids.

The time that the form instance xml is created on the driver''s device (in UTC).

A number representing the status of this particular form instance xml. If the form instance xml is submitted, status = 1, else not submitted.

A number representing the version of this form instance xml. The version_number can be 1, 2, or 3. The version number will be incremented when a new form instance xml is created on the same form instance.

The time that the form instance xml is submitted (in UTC).

A unique identifier for this driver, used within Fleet. Use DRIVER_ID for grouping by this view.

A unique identifier for this driver, used within the Analytics server. Use DRIVER_KEY for joining this view.

A unique identifier for the vehicle, used within Fleet. Use VEHICLE_ID for grouping by this view.

A unique identifier for the vehicle, used within the Analytics server. Use VEHICLE_KEY for joining this view.

An identifier for the job related to this form instance xml, used within the Fleet and Analytics server alike. Use JOB_ID for joining to this view.

The name of this job.

The time that the job is deleted (in UTC).

The time that the job is hard deleted from the database (in UTC).

The name of the template used for this form instance xml.

An identifier for the template used for this form instance xml.

A unique identifier for the specific version of the template used for this form instance xml.

A number representing the version of the template used for this form instance xml.

The location at which the form instance xml is created.

The street number of the address.

The street name of the address.

The city of the address.

The state of the address.

The zip code of the address.

The country of the address.

The latitude coordinate of where the form instance xml is created.

The longitude coordinate of where the form instance xml is created.

The content of the form instance xml in json format.

The type of the form instance xml; for example, standard, dvir.3rdSignature.

A boolean indicating whether the walkaround has been completed or not.

The total number of passed vehicle parts.

The total number of failed vehicle parts.

The total number of fixed vehicle parts.

The total number of not applicable vehicle parts.

The total number of non-critically failed vehicle parts.

The time that this form instance xml entry is last updated (in UTC).

A unique identifier for this driver, used within the Analytics server. Use DRIVER_KEY for joining this view.

A unique identifier for this driver, used within Fleet. Use DRIVER_ID for grouping by this view.

The driver's full name (first, middle, and last, where available).

The driver's first name.

The driver's middle name.

The driver's last name.

The first field of the driver's address details.

The second field of the driver's address details.

The third field of the driver's address details.

The city that this driver lives in.

The state that this driver lives in.

The region that this driver lives in.

The ZIP code for the area that this driver lives in. Applicable in the United States.

The postcode of the area that this driver lives in. Applicable in countries that use a postcode.

The country that this driver lives in.

The driver's primary phone number.

The driver's secondary or alternative phone number.

The driver's mobile phone number.

The driver's employee number.

The date when the driver was hired.

The date when the driver left the organization.

The driver's unique driver's license number.

The state in which the driver's license was issued.

The class of driver's license issued to the driver.

The expiration date of the driver's license.

The driver's insurance carrier.

The driver's insurance account number.

The expiration date of the driver's insurance policy.

An array of hierarchy node names from top-level node down to the node that the driver is in. Note: Full Hierarchy, will need to parse to report on individual hierarchy.

An array of hierarchy node IDs from top-level node down to the node that the driver is in. Note: Full Hierarchy, will need to parse to report on individual hierarchy.

An array of names for the teams that the driver is part of.

An array of IDs for the teams that the driver is part of.

The driver's email address.

A unique identifier for the Fleet user that this driver is supervised by.

The driver’s WorkPlan version.

The HOS rule set ID for the driver.

The name of the driver's depot.

Whether this driver database entry is current or has been replaced by a newer copy.

The time at which this video course entry was created, in UTC.

The time at which this video course entry became historical, in UTC.

The time, in UTC, when this entry was last updated.

A unique identifier for the driver, used within Fleet. Use DRIVER_ID for grouping by this view.

A unique identifier for the driver, used within the Analytics server. Use DRIVER_KEY for joining this view.

The date for which the aggregation is done.

The distance that the driver has driven, across vehicles, on the given date, in meters.

The total time the driver spent idling on the given date, in seconds.

The number of hard acceleration events recorded for the driver on the given date.

The number of hard braking events recorded for the driver on the given date.

The number of seat belt violation events recorded for the driver on the given date.

The number of events recorded where the driver was speeding 10 MPH over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 10 MPH over the posted speed limit on the given date.

The total engine running time recorded for this driver and date, in seconds.

The amount of fuel the driver used on the given date, in gallons or liters.

The total time the driver spent in non-productive idling on the given date, in seconds.

The total time for which the PTO (power take off) is active on the given date, in seconds.

The total time for which the seatbelt was not in use for this driver on the given date.

Trip_duration used to calculate trip values for DRIVING_WITHOUT_SEATBELT metric.

The distance that the driver has driven, across vehicles, on the given date, in meters.

The amount of fuel the driver used on the given date, in gallons or liters.

The number of speeding events recorded where the driver was in the high band on the given date.

The number of speeding events recorded where the driver was in the medium band on the given date.

The number of speeding events recorded where the driver was in the low band on the given date.

Total time the driver was driving within a good economical range (1500 - 2500 RPM) on the given date.

The number of events recorded where the driver was traveling at a speed over 65 MPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 75 MPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 80 MPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 90 MPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 100 MPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 105 KPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 110 KPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

The number of events recorded where the driver was traveling at a speed over 120 KPH on the given date. Counts the first speed event. Does not count consecutive events. The vehicle's speed must drop below the threshold then rise back above the threshold before an additional event is counted.

Indicator of the driver’s activity on the given date. Equal to 1 if the driver was sufficiently active, and 0 otherwise.

The total time for which the seatbelt was not in use by the driver for more than 5 miles on the given date.

The total time for which the seatbelt was not in use by the driver’s passenger for more than 5 miles on the given date.

The total time for which the seatbelt was not in use by the driver for more than 10 miles on the given date.

The total time for which the seatbelt was not in use by the driver’s passenger for more than 10 miles on the given date.

The total time for which the seatbelt was not in use by the driver for more than 2 minutes on the given date.

The total time for which the seatbelt was not in use by the driver’s passenger for more than 2 minutes on the given date.

The total time for which the seatbelt was not in use by the driver for more than 10 minutes on the given date.

The total time for which the seatbelt was not in use by the driver’s passenger for more than 10 minutes on the given date.

The total time for which the seatbelt was not in use by the driver at the speed of more than 35 MPH on the given date.

The total time for which the seatbelt was not in use by the driver’s passenger at the speed of more than 35 MPH on the given date.

The total time for which the seatbelt was not in use by the driver at the speed of more than 60 MPH on the given date.

The total time for which the seatbelt was not in use by the driver’s passenger at the speed of more than 60 MPH on the given date.

Total count of trips the driver makes on the given date.

Total count of RPM 767 events the driver makes on the given date.

Total amount of fuel used while the driver’s vehicles were idling on the given date. If the vehicle reports fuel usage, this KPI is based on reported fuel usage during idle time. If the vehicle does not report fuel usage, this KPI is calculated based on a fixed value of 0.8 gallons per hour (3.028 liters per hour) multiplied by idle time.

The total time for which the PTO (power take off) is active on the given date, in seconds. Data based on diagnostic readings.

The total time for which the driver was actively driving on the given date.

The number of events recorded where the driver was harshly cornering on the given date.

The first driver’s address ID reported for the day.

The last driver’s address ID reported for the day.

The number of events recorded where the driver was speeding 5 MPH over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 10 MPH over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 10 KPH over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 20 KPH over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 10% over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 20% over the posted speed limit on the given date.

The number of events recorded where the driver was speeding 5 MPH over the posted speed limit for 2 minutes on the given date.

The number of events recorded where the driver was speeding 10 MPH over the posted speed limit for 2 minutes on the given date.

Total duration of events recorded where the driver was speeding 10 MPH over the posted speed limit for 2 minutes on the given date.

The number of events recorded where the driver was speeding 10 KPH over the posted speed limit for 2 minutes on the given date.

The number of events recorded where the driver was speeding 20 KPH over the posted speed limit for 2 minutes on the given date.

The number of events recorded where the driver was speeding over 75 MPH for 2 minutes on the given date.

The number of events recorded where the driver was speeding over 85 MPH for 2 minutes on the given date.

The number of events recorded where the driver was speeding 10% over the posted speed limit for 2 minutes on the given date.

The number of events recorded where the driver was speeding 20% over the posted speed limit for 2 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for a duration between 0 and 5 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for a duration between 5 and 10 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for a duration between 10 and 15 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for a duration between 15 and 30 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for a duration between 30 and 60 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for a duration between 60 and 1440 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for longer than 5 minutes on the given date.

Total count of events where the driver was not moving and the engine was on for longer than 10 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for longer than 15 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for longer than 30 minutes on the given date.

Total count of events where the driver was not moving and the engine is on for longer than 60 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for a duration between 0 and 5 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for a duration between 5 and 10 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for a duration between 10 and 15 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for a duration between 15 and 30 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for a duration between 30 and 60 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for a duration between 60 and 1440 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for longer than 5 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for longer than 10 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for longer than 15 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for longer than 30 minutes on the given date.

Total count of events where the driver’s vehicle was not moving, the engine was on, and the PTO sensor was off for longer than 60 minutes on the given date.

The number of events recorded where an airbag was deployed for the driver on the given date.

The number of events recorded where the seat belt warning light was active for the driver on the given date.

The amount of energy used by the driver’s electric vehicle's motor on the given date.

The amount of energy generated by the driver’s electric vehicle's motor on the given date.

The amount of energy used by the HVAC (Heating, Ventilation, and Air Conditioning) systems in the driver’s electric vehicle's on the given date.

The amount of energy used by auxiliary systems (for example, lights and radio) in the driver’s electric vehicle's on the given date.

The amount of energy used by the driver’s electric vehicle's while idle on the given date.

The raw amount of electricity consumption that occurs during electric vehicle recharge for the driver on the given date.

The amount of energy used when recharging the driver’s electric vehicle's on the given date.

The gain in battery energy that occurs when recharging an electric vehicle for the driver on the given date.

The difference between power used recharging and battery level gained for the driver on the given date.

The time duration that electric vehicles spend recharging for the driver on the given date.

The distance traveled by electric vehicles inside a good economical range (1500 - 2500 RPM) for the driver on the given date.

The amount of CO2 emission prevented by using an electric vehicle for the driver on the given date.

The total amount of energy used by an electric vehicle for the driver on the given date.

The longest engine running time on each particular day for the driver on the given date.

Total number of times the Anti-Lock Braking System (ABS) was engaged for the driver on the given date.

Total number of times the Roll Over Protection (ROP) engine control unit or ROP brake control was engaged for the driver on the given date.

Total number of times the Anti-Slip Regulation (ASR) was engaged for the driver on the given date.

Total count of events when the driver’s vehicle was speeding more than 5 MPH over the posted speed limit and the speed was faster than the Smart Speed.

Total count of events when a driver’s vehicle was speeding more than 5 MPH over the posted speed limit for a duration of more than 2 minutes, and the speed was faster than the Smart Speed on the given date.

Total count of events when the driver’s vehicle was speeding more than 10 MPH over the posted speed limit and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 10 MPH over the posted speed limit for a duration of more than 2 minutes, and the speed was faster than the Smart Speed on the given date.

Total count of events when the driver’s vehicle was speeding more than 10 KPH over the posted speed limit and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 10 KPH over the posted speed limit for a duration of more than 2 minutes, and the speed was faster than the Smart Speed on the given date.

Total count of events when the driver’s vehicle was speeding more than 20 KPH over the posted speed limit and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 20 KPH over the posted speed limit for a duration of more than 2 minutes, and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 10% over the posted speed limit and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 10% over the posted speed limit for a duration of more than 2 minutes, and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 20% over the posted speed limit and the speed was faster than the Smart Speed on the given date.

Total count of events when a driver’s vehicle was speeding more than 20% over the posted speed limit for a duration of more than 2 minutes, and the speed was faster than the Smart Speed on the given date.

The number of speeding events recorded where the driver was in the low band and the speed was faster than the Smart Speed on the given date.

The number of speeding events recorded where the driver was in the medium band and the speed was faster than the Smart Speed on the given date.

The time, in UTC, when the last entry for the driver was inserted in the Analytics database on the given date.

The time, in UTC, when the last entry for the driver was updated in the Analytics database on the given date.

The total time the driver was working on the given date, in seconds.

A unique identifier for this driving period, used within Fleet and the Analytics server alike. Use DRIVING_PERIOD_ID for joining to this view.

A unique identifier for the vehicle, used within the Analytics server. Use VEHICLE_KEY for joining this view.

A unique identifier for the vehicle, used within Fleet. Use UNIT_ID for joining this view.

Enumeration providing the status for this driving period.

JSON that contains properties like destination, distance and driving duration.

JSON array that contains all ELD events.

The time, in UTC, when this driving period started.

The time, in UTC, when this driving period ended.

Relevant IANA time zone.

A unique identifier for this driving period action, used within Fleet and the Analytics server alike. Use DRIVING_PERIOD_ID for joining to this view.

A unique identifier for associated driving period, used within Fleet and the Analytics server alike. Use DRIVING_PERIOD_ID for joining this view.

Enumeration providing the status for associated driving period.

The time, in UTC, when the action took place.

The time, in UTC, when the row was inserted in the database.

The time, in UTC, when this row was last updated in the database.

Relevant IANA time zone.

A unique identifier for the vehicle, used within Fleet. Use UNIT_ID for grouping by this view.

A unique identifier for the particular event type.

Description of the type of event that this relates to.

The start time of the event (in UTC).

The end time of the event (in UTC).

The value pertaining to an event. Note that not all events have a value.

Indicates whether this event is ongoing, or still occurring as of the latest point received from a unit.

A unique identifier for the hierarchy node.

The name of the hierarchy node.

The unique identifier of the parent node.

The depth (or level) of the hierarchy node within the hierarchy.

The full path of hierarchy node IDs up to and including this node (including all ancestors).

The full path of the names of the hierarchy nodes up to and including this node (including all ancestors).

The time, in UTC, when this database entry was last updated.

A unique identifier for this particular insight alert.

A unique identifier for the condition, used within Fleet. Use CONDITION_ID for grouping by this view.

A unique identifier for the condition, used within the Analytics server. Use CONDITION_KEY for joining this view.

The time that the criteria for the alert was satisfied (in local time).

The time that the insight alert ended, and the criteria was no longer satisfied (in local time).

The time that the insight alert was first triggered (in local time).

The time that the criteria for the alert was satisfied (in UTC).

The time that the insight alert ended, and the criteria was no longer satisfied (in UTC).

The time that the insight alert was first triggered (in UTC).

The duration (in seconds) that the insight alert was active for.

The address applicable at the "On" time of the alert.

The street number applicable at the "Trigger" time" of the alert.

The address applicable at the "Trigger" time of the alert.

The address applicable at the "Off" time of the alert.

The speed (in cm/s) when the alert was triggered (if applicable).

The speed limit (in cm/s) that must be exceed in order to trigger the alert (if applicable).

The posted speed limit (in cm/s) when the alert was triggered (if applicable).

The entity that triggered the alert.

The type of entity being targeted by the Insight Alert.

A unique identifier for the vehicle, used within the Analytics server. Use VEHICLE_KEY for joining this view.

A unique identifier for this driver, used within the Analytics server. Use DRIVER_KEY for joining this view.

A unique identifier for this address, used within Fleet and the Analytics server alike. Use ADDRESS_ID for joining or grouping by this view.

A unique identifier for this marker, used within the Analytics server. Use MARKER_KEY for joining this view.

The latitude at the time the alert was triggered.

The longitude at the time the alert was triggered.

The attached job id for the alert (if applicable).

The time, in UTC, when this entry was last updated.

The install type id that this diagnostic parameter belongs to.

The TID (ID) of the diagnostic parameter.

The name of the diagnostic parameter.

Whether this vehicle database entry is current or has been replaced by a newer copy.

The time at which this entry was created, in UTC.

The time at which this entry became historical, in UTC.

The time, in UTC, when this entry was last updated.

A unique identifier for this marker, used within the Analytics server. Use MARKER_KEY for joining this view.

A unique identifier for this marker, used within Fleet. Use MARKER_ID for grouping by this view.

The name of the marker.

The type of the marker.

The latitude coordinate where the marker is located.

The longitude coordinate where the marker is located.

The shape of the marker: "Circle" or "Polygon".

The detailed shape of the marker.

The radius of the marker's area, if the marker's shape is a circle.

The primary category ID that this marker is assigned to.

The primary category tag that this marker is assigned to.

A JSON object that contains all the unparsed data for the marker.

The country that the marker is in.

The postcode of the area that the marker is in. Applicable in countries that use a postcode.

The ZIP code for the area that the marker is in. Applicable in the United States.

The region that the marker is in.

The state that the marker is in.

The city that the marker is in.

The suburb that the marker is in.

The street number that the marker is on.

The street number that the marker is on.

A unique identifier that can be used as stops for jobs and routes.

The primary territory ID that this marker is assigned to.

The tags that are associated with this marker.

The tag IDs that are associated with this marker.

The latitude coordinates where the marker address intersects with the street (where the driveway meets the road).

The longitude coordinates where the marker address intersects with the street (where the driveway meets the road).

The genesis of the marker

The address of the sites associated with the marker.

The description of the site associated with the marker.

Phone numbers associated with the marker.

IANA time zone of the marker.

Unit ID that marker is set to be associated with.

The report color of the marker.

Whether this marker database entry is current or has been replaced by a newer copy.

Whether this marker entry is curated or not.

The time at which this video course entry was created, in UTC.

The time at which this video course entry became historical, in UTC.

The time, in UTC, when this entry was last updated.

A unique identifier for this mobile event type, used within the Analytics server. Use MOBILE_EVENT_TYPE_KEY for joining this view.

A unique identifier for this mobile event type, used within Fleet. Use MOBILE_EVENT_TYPE_ID for grouping by this view.

The name of the mobile event type.

Whether this mobile event type database entry is current or has been replaced by a newer copy.