Smoke Detection
The Smoke Detection page shows you every smoking incident in your fleet as individual cases. You can flag important cases, add notes for your team, and download reports for customers who dispute fines.
Before You Start⚓︎
This page appears when the Smoke Detection is active for your fleet. This means your vehicles have the Smoke Detection+ Module installed and configured, and the feature is enabled for your fleet.
How cases are created:
Cases appear automatically when Smoke Detection detects smoking in a vehicle. Each incident becomes an individual case you can manage here. For details on how the detection system works, see How Smoke Detection Works.
When to Use This Page⚓︎
Cases vs. Trips vs. Events:
- Smoke Detection Cases (this page) - Individual smoking incidents reported immediately after detection. Each case appears as soon as the smoking incident is measured and analyzed, even during active trips. Case-centered view.
- Trips page - Complete trip data including smoking incidents, but only displayed after the trip ends (as configured in the Trip Settings). Trip-centered view showing all events within the trip.
- Events page - Timeline of all vehicle events including smoking events, filterable alongside other vehicle events. Vehicle-centered view independent of bookings or trips.
Key difference: Cases appear immediately when smoking is detected. Trips data appears only when the complete journey is finished. Events show the continuous timeline regardless of trip status.
Use this page when you need immediate awareness of smoking incidents and want to respond while trips are still active.
Quick Start⚓︎
- Go to Smoke Detection in the main menu.
- Review smoking incidents using the Preset that fits your workflow or use Filter to create custom views by date, vehicle, or severity.
- Click any case to see details, flag it, or add remarks.
- Download PDF reports when you need them e.g. for customer disputes or archiving purposes.
What You’ll See⚓︎
The main table shows:
- When and where smoking happened
- How long it lasted
- Particle concentration measurements during the incident
- Which vehicle was involved
Key data columns to understand:
- Number of Peaks - Increases in measurements, typically from exhaled smoke
- Duration - Time that smoke levels remained above the detection threshold
- Max Concentration - Highest particle density measured during the incident

Understanding All Table Columns⚓︎
The complete table provides comprehensive data for incident analysis and record keeping:
Column | Description | Use Case |
---|---|---|
Flag | Case status indicator and workflow position | Track progress and assign team responsibilities |
Case ID | Unique identifier for each incident | Reference specific cases e.g. in internal or customer communications |
Vehicle ID | Vehicle where smoking was detected | Identify vehicles with recurring issues or patterns |
Started | When PM2.5 levels first exceeded the detection threshold | Establish precise incident timeline for disputes |
Ended | When PM2.5 levels returned below the detection threshold | Calculate total incident duration |
Remark | Free-text field for notes and information | Add custom information relevant to your workflow |
Average Speed | Vehicle speed during the incident | Determine if smoking occurred while driving vs. parked |
Duration | Time that PM2.5 levels remained above threshold | Assess incident length and exposure time |
Avg. Count Concentration | Average PM2.5 particle density during incident | Baseline particle level throughout the event |
Max. Count Concentration | Peak PM2.5 particle density reached | Highest particle concentration detected |
Number of Peaks | Distinct increases in PM2.5 measurements | Count of separate particle concentration spikes |
Sum. Count Concentration | Total accumulated PM2.5 particle measurements | Overall particle exposure during the incident |
Telematics Unit ID (QNR) | CloudBoxx device identifier (QNR) | Technical reference for support and maintenance issues |
Telematics Brand | CloudBoxx hardware brand/manufacturer | Device identification for technical support |
Doors at Start | Door status when incident began | Initial vehicle access state |
Ignition at Start | Ignition status when incident began | Initial vehicle operation state |
In Motion at Start | Whether vehicle was moving when incident began | Initial vehicle movement state |
Windows at Start | Window status when incident began | Initial vehicle ventilation state |
Doors at End | Door status when incident ended | Final vehicle access state |
Ignition at End | Ignition status when incident ended | Final vehicle operation state |
In Motion at End | Whether vehicle was moving when incident ended | Final vehicle movement state |
Windows at End | Window status when incident ended | Final vehicle ventilation state |
Doors Status at First Measurement | Door status at the moment of first PM2.5 detection | Precise vehicle access state at detection start |
Doors Status Changed since First Measurement | Whether doors opened/closed during the incident | Track access changes during smoking detection |
Windows Status at First Measurement | Window status at the moment of first PM2.5 detection | Precise ventilation state at detection start |
Windows Status Changed since First Measurement | Whether windows opened/closed during the incident | Track ventilation changes during smoking detection |
Ignition Status at First Measurement | Ignition status at the moment of first PM2.5 detection | Precise vehicle operation state at detection start |
Ignition Status Changed since First Measurement | Whether ignition turned on/off during the incident | Track operation changes during smoking detection |
Created | When the case record was created in FleetControl | System timestamp for record keeping |
Updated | When the case record was last modified | Track recent changes to case data |
Managing Cases⚓︎
Flag System⚓︎
Cases can be moved through different flag statuses by clicking the flag icon (cycle through 1-4 clicks) or using the chevron dropdown menu:
- Unflagged → Default status for new cases
- Flagged → Cases marked for attention
- Checked → Cases that have been reviewed
- Issue Detected → Cases requiring ongoing action
The flag system allows you to organize cases according to your workflow needs.
Adding Notes⚓︎
Click Remark to add custom notes and information to the case record.
Vehicle History⚓︎
Click Show Vehicle History to filter the view to show only smoking incidents for the selected vehicle.

Presets⚓︎
Preset | Description | Use Case |
---|---|---|
All Cases | Complete list of all smoking incidents | View entire case history, export comprehensive data |
Unflagged Cases | New incidents that haven’t been reviewed yet | Daily case review workflow, identify cases needing attention |
Flagged Cases | Cases marked for attention or follow-up | Process cases requiring customer contact or escalation |
Checked Cases | Cases that have been reviewed and documented | Review completed cases, verify team progress |
Cases with detected issues | Confirmed violations requiring ongoing action | Track serious violations, manage repeat offenders |

Export and Download⚓︎
Data Retention Limit
FleetControl keeps data for 90 days maximum. Export important smoke detection cases before they’re automatically deleted.
Export Options⚓︎
Individual case: Click the case’s ⋯ menu > Smoke Report (PDF) for a detailed report with graphs and data.
Multiple cases: Select cases, then use the table’s ⋯ menu to get Smoke Reports (PDFs) as a ZIP file.
Spreadsheet data: Use the table’s ⋯ menu to Export to CSV for analysis in Excel or other tools.

Common Tasks⚓︎
Finding a specific case:
Use Case ID, vehicle filter, or date range to locate incidents.
Customer dispute:
- Download the PDF report for the case
- Review particle data and vehicle context
- Mark case as Checked when resolved
For detailed dispute guidance, see Handling Customer Disputes.
Vehicle cleaning planning:
Filter by vehicle to see incident history and plan maintenance.
Team coordination:
Use flags and remarks to track case progress and handoffs.
Tips⚓︎
- Multiple PM2.5 peaks typically indicate active smoking rather than external sources
- Export cases before the 90-day retention limit
- Use vehicle history to identify patterns requiring attention
- Consistent flagging helps maintain organized workflows
Related Information⚓︎
For understanding how detection works and interpreting data, see How Smoke Detection Works.
For detailed dispute resolution guidance, see Handling Customer Disputes.
For viewing smoking incidents within trip context, see Trips.