Glossary
Short definitions for terms used across RD Analytics. For status badges, see Scan statuses. For roles, see User roles and permissions.
Core workflow
| Term |
Definition |
| Location |
Physical or logical site. Groups Sources. |
| Source |
Video input (typically a video file or batch of files) attached to a Location. The source holds the media — it is not the analysis itself. |
| Scan |
Analysis setup on a Source (AI modules, geometry, outputs). You configure it, run processing, then use the results in Reports. One source can have several scans. A scan is not the video file. |
| Report |
Dashboard of widgets (tables, charts, filters, totals) over scan or merged-scan data. |
| Report view |
Report page with the widget grid and Apply. |
| Merging |
Optional workflow that combines results from multiple scans into a merge job. Report mode Merged scans can use those results. |
| Merge |
A single merge job/definition and its run status. |
Configuration panels (scan)
| Term |
Definition |
| AI processing settings |
First panel on the scan configuration page — choose detectors/processors and module parameters. Only ACTIVE AI-Models appear here. |
| Draw settings / Geometry editor |
Panel for drawing geometry on the video frame (lines, areas, and geometry zones). |
| Output settings |
Panel for what the pipeline writes when the scan runs (for example SystemDB, optional video/SQL/webhook outputs). |
| Geometry |
Drawn counting lines, areas, and geometry zones on the scan canvas. Not the same as organizational Zones. |
| SystemDB |
Default output that persists metrics, tracks, and events for reports. |
| Module |
Pipeline component (detector, tracker, output). See Pipeline modules for the built-in catalog. Custom packages are managed under System → Modules. |
System and licensing
| Term |
Definition |
| AI-Models |
Shipped neural network cores managed under System → AI-Models. Enable them so they appear in scan AI processing slots. |
| ACTIVE |
AI-Model status — loaded and available for scans. |
| COMPILING |
AI-Model status — GPU engine compile in progress (often several minutes on first enable). |
| INACTIVE / FAILED / RESTART_REQUIRED |
Other AI-Model states — see AI-Models. Model OFFLINE means the engine is not connected. |
| Class groups |
Buckets of raw detector class names into report-friendly labels and colors (System → Class groups). |
| 50fps |
License pricing tier with a 50 FPS file-processing budget. |
| Pro |
License pricing tier with an unlimited (uncapped) file-processing FPS budget — hardware still limits throughput. |
| Zone |
Organizational / security grouping for locations and users (Administration → Zones). Distinct from geometry zones drawn on a scan. |
| Authority |
User role (SYS_ADMIN, ENGINEER, VIEWER) controlling menu access and mutations. |
| Engine |
Background GPU service that runs scan pipelines. |
Reports and UI actions
| Term |
Definition |
| Apply |
Report action that refreshes data widgets using the current filter state and time range. Does not save layout. |
| Widget |
Single element on a report (table, chart, filter, control, total). |
| Scene overview |
Report widget (image.scan) showing scan reference images. |
| Single scan / Merged scans |
Report data modes — one completed scan, or merged-scan results. |
| DRAFT / PENDING |
Scan lifecycle — editable configuration vs ready to queue. Toggle before processing. See Scan statuses. |
Related pages