Status Statistics

calServer analyses statuses in two ways: as a count per status (distribution) and as a processing time between a start and a stop status.

Count per status

The status distribution shows how many records are in each status.

• Displayed via the Status overview dashboard widget (pie chart), which renders the counts per inventory status using each status's colour.
• The data comes from the GET /statuses/counts?type=inventory endpoint, which returns title, colour and count per status (including statuses with count 0).

Processing-time variables

A status variable measures the time a record spends between a start status and a stop status (e.g. "Incoming" → "Done").

Element	Description
Name	Display name of the metric (free text); without one, the technical name is shown
Technical name	Assigned automatically on creation (V1 scheme {area}_processing_time[_N])
Area	Data area (e.g. inventory); calibration variables measure the inventory status, as in V1
Start status	Statuses that start the measurement — multi-select from the area's statuses
Stop status	Statuses that end the measurement — multi-select; empty = "still running"
Extra option	Which start→stop run counts (see below)
Format	Duration display format (d:h:m:s, h:m, …)

Extra option

The extra option is the structured replacement for the free-text comparison formula from calServer V1 (which was evaluated via eval() there and is deliberately not ported):

Option	Effect
Last run (default)	The most recent start→stop run counts (V1 default behaviour)
First run	The first start counts; later starts do not reset the measurement
Last calibration only	Only the run around the latest active calibration counts: the last start up to and including the calibration day, ended by the first stop after it; records without a calibration yield no measurement

Free-text expressions migrated from V1 remain stored and visible but are not evaluated (default behaviour applies); editing lets you switch to one of the structured options.

Create a variable

1. Navigate to Administration › Status.
2. Select the Statistics tab.
3. Define name, area, start/stop statuses, extra option and format — the technical name is assigned automatically.
4. Save.

Managing variables requires the Basic settings (admin) permission. Evaluation currently covers the inventory area; variables of other areas are stored but not yet measured.

Measurement and analysis

Processing times are computed from the status history (audit log) and materialised — unlike calServer V1, where they were recomputed on every list render. For each record, the time counts from the last entry into a start status to the stop afterwards; a record still in the start status is considered "running".

A variable's measured values can be inspected in the Statistics tab via the Measurements action (record, start, stop, formatted duration).

Rebuild

Measurements are rebuilt automatically every day and can be recomputed manually after changing the start/stop status:

php artisan status:rebuild-processing-times
php artisan status:rebuild-processing-times --variable=<UUID>

Not to be confused with filter statistics

Filter statistics (result counts of saved advanced filters at reference dates, filter-statistics:save, FilterStatisticWidget) are a separate feature and not part of status statistics.