Glossary
Every term you meet in the Fleet Dashboard, in plain words. Labels in bold are exactly as they appear on screen. Each entry links to the guide or concept page that explains it in full.
- Access row: one role in one group, or in Entire company. A user has 1 to 20 access rows, and at least one of them uses a system role. See Groups and access.
- Acknowledge: tell your team that someone is handling an alert. Any user who can see an Open alert can acknowledge it and add a note; the alert then shows Acknowledged with their name. See Alert history.
- Activation speed: a setting on the Safety settings page: the speed from which the dashcam’s AI raises events. Device defaults are 37 mph for ADAS and 19 mph for DMS, and you can set 0–75 mph. See Safety settings.
- Active hours: when an alert rule is on: Always, or chosen days and hours. They are evaluated in the company time zone. See Alert rules.
- ADAS: driver assistance events seen by the road camera (CH1), such as forward collision warning, close following and lane departure. A kit needs the ADAS licence for them. See Safety events.
- AI profile: a saved set of ADAS and DMS settings that can be applied to chosen kits. It starts as a draft and must be published before you apply it. See AI profiles.
- AI settings: the ADAS and DMS settings on the Safety settings page: which events each camera detects, their Sensitivity and the Activation speed. Saving sends them to every kit in your company. See Safety settings.
- Alert: one firing of an alert rule, kept in Alert history. Its status is Open, Acknowledged or Resolved; only kit offline alerts resolve, on their own, when the kit comes back online. See Alert history.
- Alert rule: says what happens, to which trucks, at which times, and which roles are told, in-app or by email. Company rules apply to everyone they name; My rules are personal. Two default rules come ready-made. See Alerts and notifications.
- Amendment: a new version of a locked IFTA quarter. The locked report stays as it is; you give a reason, generate the amendment and lock it again. Its PDF is marked AMENDED. See Lock and amend a quarter.
- Assignment: the link that says which driver drives which vehicle, and since when. There is one active driver per vehicle and one vehicle per driver. Roudiy uses it to decide whose trip or event it is. See Vehicles, drivers and assignments.
- Behavior weight: how much one event of a type per 1,000 miles lowers the safety score, for example 10 for a phone call. Types without a weight do not lower the score. The Behavior breakdown on a score shows it as Weight. See Safety scores.
- Camera & privacy: the settings page that decides who sees the driver-facing camera (CH2), whether audio is recorded, and which channels are saved for each event type. See Camera privacy.
- CH1, CH2, CH3: the three video channels of the JC371 dashcam: CH1 road, CH2 driver and CH3 an optional extra (aux) camera. You pick a channel whenever you ask for video. See Kits and cameras.
- Coachable: a review status: the driver should hear about this event. It goes to the coaching list and still counts in the score. See Safety events.
- Coached: a review status an event gets only inside a coaching session, after you talked it through with the driver. It still counts in the score. See Coaching session.
- Coaching session: a review of one driver’s coachable events (up to 50) with you as the coach, due in 14 days. Nothing is sent to the driver; you hold the conversation yourself. See Start coaching.
- Confidential event: a safety event hidden from users without access to confidential events. It disappears from their lists, counts and reports, but still counts in the driver’s score. See Safety events.
- Connection: whether a kit can talk to Roudiy right now: Online, Offline, Sleeping or Unknown. It is separate from the kit status. See Kits and cameras.
- Cooldown: how long an alert rule stays quiet before it alerts again for the same vehicle and event type: 0 to 1,440 minutes, 10 by default. Collision and SOS alerts ignore it. See Alert rules.
- Credit: a negative net gallons figure in an IFTA report: you paid tax on more gallons in that state than you burned there. Credits show in parentheses, for example (627.5). See IFTA basics.
- Custom role: a role you create, usually by duplicating a system role and adding or removing permissions. A company can have up to 50. See Create a custom role.
- Data quality warning: a problem Roudiy found in a quarter’s IFTA data, such as a GPS gap or an Odometer jump. You tick I reviewed the warnings before you generate the report. See IFTA report.
- Delivery: one attempt to tell one person about an alert on one channel (in-app or email). Each delivery is Pending, Sent, Failed or Skipped. See Alert history.
- Device Hub: the page that lists your kits: JC371 dashcams and KD032 gateways, with their status, connection, cameras and vehicle. It refreshes every 30 seconds. See Device Hub.
- Dismissed: a review status for an event not worth keeping in the score, with a reason: Incorrect, Minor or Other. Dismissed events do not count in scores. See Safety events.
- DMS: driver monitoring events seen by the driver-facing camera (CH2), such as a phone call, eyes closed or distraction. A kit needs the DMS licence for them. See Safety events.
- Driver: a person who drives your trucks: name, phone, CDL number and license state. Drivers are records, not users; they never sign in. See Add a driver.
- ELD platform account: the account you sign in to the Fleet Dashboard with. One account works for all ELD platform products, and a password change applies to all of them. See Sign in.
- Event clip: video Roudiy fetches on its own when a safety event is created. It can take up to 10 minutes to arrive; if it does not, you can request the video from the SD card. See Video.
- Event type: what kind of safety event it is, for example Harsh braking or Phone call. There are 20 types in the categories ADAS, DMS, Harsh, Speeding and Other. Each has a default severity; some types also have a weight that lowers the safety score, others have none (shown as —). See Safety events.
- Fault code: an engine error the truck reports through the KD032 gateway, at level Critical, Warning or Info. An alert rule can fire on a New fault code. See Vehicle health.
- Fleet MPG: worked out for each fuel type for the quarter: total miles divided by total gallons of that fuel type, rounded to 2 decimals. The IFTA report uses it to work out taxable gallons per state. See IFTA basics.
- Fleet View status: the one status each truck has on the map and list: Moving, Idle, Ignition off, Offline or No data. See Trips and GPS.
- Fuel purchase: one fuel stop: date, vehicle, state, gallons and cost. Tax paid at the pump is on by default. You add purchases by hand or import a file; an IFTA report needs them. See Fuel purchases.
- Geofence: an area you draw on the map, a circle or a polygon, with a type such as Yard or Customer site. Vehicle entries and exits are recorded. See Geofences.
- GPS gap: a stretch with no location, for example in a tunnel. History draws it as a dotted line; in IFTA, a gap of more than 10 minutes while the truck moved at least 1 mile is a data quality warning. See Trips and GPS.
- Group: a part of your fleet, such as a terminal or a region. Vehicles and drivers belong to groups, and a user’s group decides which trucks and drivers they see. See Groups.
- GVWR: gross vehicle weight rating, in pounds. Over 26,000 lb makes a vehicle IFTA qualified. See Add a vehicle.
- Home terminal time zone: your company time zone, set in Company profile. Report periods, safety score weeks, alert active hours and IFTA days follow it. Changing it does not recalculate past days. See Company profile.
- Idle: the ignition is on and the truck has not moved for 3 minutes. The engine burns fuel while nothing happens. See Trips and GPS.
- IFTA: the International Fuel Tax Agreement: one quarterly fuel tax return for trucks that drive in more than one state, with miles and fuel per state. See IFTA basics.
- IFTA qualified: a vehicle with GVWR over 26,000 lb or 3 or more axles. Only these count in IFTA reports; a vehicle with Missing GVWR/axles is left out until you fill them in. See Vehicles, drivers and assignments.
- IFTA quarter: one three-month period of the IFTA return. It goes Open, Generated, Locked, and shows Outdated if data changed after you generated it. You can generate it 72 hours after it ends. See IFTA report.
- IMEI: the kit’s device number. Device Hub lists and searches kits by it, and Support asks for it when a kit is faulty. See Device Hub.
- IVDR: individual vehicle distance record: miles per vehicle and state, exported as the Vehicle distance (IVDR) CSV of a generated quarter. See Export the IFTA return.
- JC371 camera: the AI dashcam in the kit. It has 4G and GPS, runs AI on the camera image, records to its SD card and has up to three channels (CH1, CH2, CH3). See Kits and cameras.
- Jurisdiction: a state in the IFTA report. Roudiy reports the 48 states and DC. See IFTA basics.
- KD032 gateway: the part of the kit that plugs into the truck’s engine (ECM) port and reads engine data: odometer, RPM, fuel level, coolant, battery and fault codes. Without it, these show as not available. See Kits and cameras.
- Kit: the hardware in one truck: one JC371 dashcam and one KD032 gateway. Roudiy Support installs it; everything Roudiy knows about a truck comes from its kit. See Kits and cameras.
- Kit status: where a kit is in its life: In stock, Allocated, Allocation failed, Active, Offline, Faulty or Retired. See Kits and cameras.
- Licence: what a kit is allowed to do: Video, ADAS, DMS and FaceID. A licence that is not active shows struck through with (not licensed). See Device Hub.
- Live stream: one camera of a running truck in real time. Only one camera per truck streams at a time, and colleagues can join a running stream. See Live stream.
- Live stream minutes: the monthly allowance of streaming time, by default 10 minutes per camera per month, set by your plan. The button shows what is left, and the allowance resets every month. See Video.
- Lock (IFTA): freezes a generated IFTA quarter: its fuel purchases and mileage can no longer change. It cannot be undone; you fix a locked quarter with an amendment. See Lock and amend a quarter.
- Lock (video): keeps a video or photo past the retention period until someone unlocks it. Collision and SOS videos are locked by the system as Locked (System). See Video requests.
- My reports: the list of your own report runs on the Reports page, newest first, up to the latest 50. Other users’ runs are not shown. See Run a report.
- My rules: personal alert rules. The recipient is always Only you, and each user can have up to 20. See Alert rules.
- N/A — under 100 mi: shown instead of a safety score when a driver drove less than 100 miles in the 4-week window, too little for a fair score. See Safety scores.
- Needs review: the review status every new safety event starts with. It counts in scores; a review takes effect from the next Monday calculation. See Safety Inbox.
- Net gallons: taxable gallons minus tax-paid gallons for one state. Roudiy applies the state’s tax rate to it; a negative number is a credit. See IFTA basics.
- Notification: a message to you in the dashboard (the bell in the top bar and the Notifications page) or by email, for example about an alert or a video that is ready. See Notifications.
- Offline: the kit has stopped reporting. Last seen tells you when it last did, and the map shows its last known location. See Kits and cameras.
- Online: the kit is connected and sending data. See Kits and cameras.
- OUT: the IFTA report row for miles driven outside the IFTA jurisdictions, shown as Outside IFTA jurisdictions (not reported). It has miles only. See IFTA report.
- Outdated: an IFTA quarter whose trips or fuel purchases changed after you generated it, or whose tax rates were re-imported. Generate it again before you lock. See IFTA basics.
- Pairing: linking a kit to a vehicle, so its GPS, events and video belong to that truck. One vehicle has one kit; unpairing stops new data for that vehicle. See Pair a kit.
- Period: the time span of a report: Today, Yesterday, Last 7 days, Last 30 days, This week, Last week, This month or Last month. It is cut at 00:00 in the company time zone, and weeks start on Monday. See Run a report.
- Permission: one thing a user may do, such as viewing the map or reviewing safety events. Roudiy checks permissions, not role names. See Roles and permissions.
- Personal time zone: the time zone you pick in your profile. Times in the dashboard show in 12-hour format (2:03 PM) in your personal time zone if you set one, otherwise in the company’s; reports and exported files stay in the company time zone. The History tab uses 24-hour times. See Edit your profile.
- Place: a known location such as a truck stop, managed by Roudiy and shown as a map layer. Places are read-only. See Map layers.
- Recognized: a review status: you reviewed the event and it needs no coaching. Recognized events do not count in scores. See Safety events.
- Report run: one report you generated on the Reports page. It goes Queued, Running, then Ready or Failed; a ready file is kept for 7 days, then shows Expired. See Run a report.
- Retention: how long Roudiy keeps a video: ready SD card videos are kept for 30 days by default, set by your plan. Lock a video to keep it longer. See Video.
- Retro assignment: assigning a driver to finished trips that had none, up to 50 trips at a time, from the Trips tab. It is all or nothing. See Trips.
- Review status: where a safety event stands: Needs review, Coachable, Coached, Recognized or Dismissed. Scores count Needs review, Coachable and Coached events. See Safety events.
- Role: what a user may do: a named set of permissions. Together with a group it forms an access row. See Groups and access.
- Safety event: a moment of risky driving detected by the kit, or by Roudiy after the trip for posted speeding, with video and details. See Safety events.
- Safety score: a weekly score from 50 to 100, worked out every Monday in the company time zone from the last 4 weeks, in events per 1,000 miles. Unassigned events count only in vehicle scores. See Safety scores.
- Scope: the part of the fleet a user’s access covers: Entire company or chosen groups with their subgroups. Some work, such as generating an IFTA report, needs company-wide access. See Groups and access.
- SD card video: footage the dashcam recorded on its SD card, which you request for a vehicle, channel and time. The card is overwritten over time, so request older video soon. See SD card video.
- Segment: a 3-minute piece of SD card video. One request takes up to 3 segments in a row (9 minutes) from one channel. See SD card video.
- Sensitive permission: one of three permissions that touch privacy or the hardware: driver-facing video, dangerous device commands and confidential events. Give them only to people who need them. See Groups and access.
- Sensitivity: a setting per AI event on the Safety settings page: Off, Low, Medium or High. Most events default to Medium. See Safety settings.
- Severity: how serious an event is: Critical, High, Medium or Low. The default alert rule notifies about Critical and High events. See Safety events.
- Sleeping: the kit is offline because the ignition is off. This is normal; a sleeping kit cannot stream live video or take a snapshot. See Kits and cameras.
- Snapshot: a quick look from one channel: a Photo or a Clip (10 s). The truck must be running. See Snapshot.
- Stop: a time when the truck is not moving, between trips. See Trips and GPS.
- Subgroup: a group inside another group. Groups nest up to 5 levels, and users of a parent group also see its subgroups. See Groups.
- System role: one of the four ready-made roles: Company Admin, Dispatcher, Safety Manager and Compliance Manager. They cannot be changed. See Roles and permissions.
- Taxable gallons: a fleet-level estimate of the fuel burned in one state: the fleet’s miles in that state divided by fleet MPG, for each fuel type (not per truck). See IFTA basics.
- Tax-paid gallons: gallons from fuel purchases with Tax paid at the pump on, per state. They are subtracted from taxable gallons. See Fuel purchases.
- Trigger: what starts an alert rule: Safety event, Kit offline (24 hours) or New fault code. You cannot change it after you save the rule. See Alert rules.
- Trip: one drive. It starts when the truck reaches 5 mph and ends after 5 minutes below 5 mph, or at a state border. See Trips.
- Two-step verification: a 6-digit code sent to your email at every sign-in, on top of your password. The code expires in 10 minutes; you turn it on or off in your profile. See Two-step verification.
- Unassigned: trips and events recorded while no driver was assigned. They count for IFTA and in the vehicle score, but not in any driver’s score. See Vehicles, drivers and assignments.
- Unit #: the name of a truck in your fleet, such as TRK-101. It is unique in your company. See Add a vehicle.
- USDOT number: your company’s US DOT number, up to 8 digits. Saving it activates your company and links it with the ELD platform; after that only Support can change it. See Company profile.
- Vehicle: a truck record: Unit #, VIN, plate, make and model, fuel type, weight and axles. The kit is paired to the vehicle, so GPS, engine data and video belong to it. See Add a vehicle.
- Video request: a request for SD card video. It goes Queued, Waiting for device (truck offline, retried up to 7 days), Uploading, and ends as Ready, Failed or Overwritten. See Video requests.