Quality Provisions¶
Named sets of measurement capabilities — Administration > Requirements > Quality provisions, measurement ranges behind the row action "Messbereiche".
This page described something else until 2026-08
It presented quality provisions as environmental requirements ("room temperature 23 +/- 2 degrees Celsius", "freedom from vibration") and listed compliance tracking plus templates for ISO 17025 / ISO 9001 / DAkkS including "create from template". None of that exists in the code. The fields were wrong too: the provision head has neither a sort order nor an active flag.
What a quality provision is¶
A name, a description — and below it rows describing one measurement range each, with the measurement uncertainty achievable there and the resolution. That is a calibration and measurement capability (CMC) statement: it says what the laboratory can do, not what has to be met.
A notice, not a conformity assessment
Since 2026-10 the release completion check reads these figures as a bound for the uncertainty stated on a certificate — as a notice in the release report, never as a blocker. Anyone looking for automatic conformity assessment of the measured values will still find it at the specifications and test steps, not here.
Until 2026-10 this said "Nothing in the program compares measured values against these figures". That is no longer true.
Fields¶
Head (quality_provision):
| Field | Meaning |
|---|---|
| Name | Designation, e.g. "DAkkS Elektrik" |
| Description | Free text |
| Annex owner | Empty or "own laboratory" = this installation's own annex. "External laboratory" = a subcontractor's |
| External laboratory name | Only with owner "External laboratory". Named in the release finding, so it says whose annex it means |
| Accreditation number | e.g. "D-K-99001-01-00" |
| Valid from / until | Validity period of the accreditation |
The description's free text may contain anything — including sentences about environmental conditions. There is no schema for it, and nothing evaluates it.
Whose annex it is¶
A provision without an owner is the annex of this installation's own laboratory. That was its only meaning before 2026-10, and existing rows keep it without any action.
With owner "External laboratory" it describes what a subcontractor can do. That changes which certificates it is read against: a calibration produced by that laboratory is measured against this annex instead of the own one. It is linked on the calibration in the field "Performing laboratory (quality provision)", so the single reference carries both the laboratory's identity and the uncertainty to expect from it.
Where a validity period is maintained, the release checks it against the calibration date. On a subcontracted calibration an expired accreditation blocks the release; elsewhere it is a notice. No maintained validity is no statement and blocks nothing.
Measurement ranges (quality_provision_detail, one row per range):
| Field | Meaning |
|---|---|
| Designation | What is measured, e.g. "Gleichspannung" |
| Mode | e.g. DCV, ACI, resistance |
| Range from / to | Lower and upper bound |
| SI prefix, unit | Symbols from the prefix and unit catalogue |
| Second range from / to | Optional second range on the same row |
| Uncertainty | What is achieved in this range |
| Resolution | Smallest step the measuring equipment resolves |
| Order | Position in the list |
Assignment¶
Provisions hang off the procedure, not off a device. The link lives in
procedure_provision; the release completion check deliberately does not use it
— the annex applies to the laboratory, not to a single test run.
The second assignment is the owner (see above): it decides which certificates are read against which annex.
Permissions¶
Head and measurement ranges sit under basic_setting_admin.
Difference from V1
V1 had its own triad quality_provision_view/edit/delete for this. V2 does
not carry it; whoever may change basic settings may change provisions.
Endpoints¶
GET /api/v2/admin/provisions
POST /api/v2/admin/provisions
PUT /api/v2/admin/provisions/{id}
DELETE /api/v2/admin/provisions/{id}
GET /api/v2/admin/provisions/{id}/details # measurement ranges of a provision
POST /api/v2/admin/provision-details
PUT /api/v2/admin/provision-details/sort-order
PUT /api/v2/admin/provision-details/{id}
DELETE /api/v2/admin/provision-details/{id}
Related pages¶
- Requirements — the collective page with all catalogues
- Resources — where the climate target range for the certificate lives