Requirements¶
Under Administration > Requirements (/v2/admin/requirements), the normative master data is maintained: test standards, SI prefixes, physical quantities, quality provisions (each with full CRUD via /test-standards, /admin/si-prefixes, /admin/physical-quantities and /admin/provisions, operation basic_setting_admin except for reading test standards), resources (resource_view / _edit / _delete) and Feldvorgaben (field defaults, see below).
Feldvorgaben (field roles, customer search and counters)¶
The Feldvorgaben tab answers which field takes which system role and how customers appear in pickers. The values were free-text fields in the basic settings until ADR-031 and lived in field management until 2026-08-17; here the field registry is available, so an assignment is picked instead of typed.
| Assignment | Effect |
|---|---|
| Status field | Field holding the device status; the e-mail actions insert it as the Status_Field placeholder |
| Additional status field | Second status field when the workflow needs two separate ones |
| Type field | Field holding the device type; drives device-type blueprints and the specification match |
| Certificate field | Field holding a calibration's certificate number (V1 only: V1 finds the number there in the calibration view, report view and mail dispatch; V2 addresses calibration fields by their api_name) |
| Customer e-mail field | Field the recipient address for customer e-mails is taken from |
| Inventory description | Fields an inventory picker displays (order matters) |
| Customer search | Fields a customer picker displays (order matters) |
The picker shows label and api_name, because only the api_name is a field's identity: on an installation set up with db:install --v1 the status field is called I4211, and in the factory default the name column carries the label "Kundennummer".
A value outside the list is kept. A V1 takeover stores V1 codes here that the registry does not necessarily list, so the control accepts free text and never discards a stored value — otherwise merely opening the page would blank a working configuration.
Global counters¶
Number ranges for default values, in the same tab. A counter is inserted into a default value via [GLOBAL_COUNTER_N] and incremented atomically (ADR-018). Four counters exist by default; Zähler hinzufügen / Letzten Zähler entfernen adjusts how many, non-destructively. A reset can be enabled per counter — daily, weekly (Monday), monthly (1st) or yearly (Jan 1st); the nightly php artisan counters:reset resets due counters to 0.
Storage is unchanged: properties under settings/calibration and settings/customer, operation basic_setting_admin. Without it the page hides the tab.
Factory defaults: SI prefixes and physical quantities¶
Both catalogs ship pre-filled. Before that, every installation had to enter prefixes and units by hand before the SI(Symbol) and UNIT(Symbol) field types, the procedure and specification editor and the DCC export had anything to offer.
SI prefixes — all 24 decimal prefixes from quetta (10³⁰) to quecto (10⁻³⁰), including hecto/deci/centi (hPa, dm, cm) and the ronna/quetta/ronto/quecto added by the CGPM in 2022.
Physical quantities — the quantities common in DAkkS-accredited calibration (DIN EN ISO/IEC 17025): the seven SI base quantities, electrical quantities (V, Ω, S, F, H, C, Hz, W, J, Wb, T, dB, dBm), temperature and humidity, pressure (Pa, bar), force/torque/stress/hardness (N, Nm, N/mm², HRC, HV, HBW), geometry and angles, kinematics and rotational speed, flow, chemistry (pH, S/m, mol/l, ppm) as well as photometry and acoustics.
Three things worth knowing:
- Mass is listed as gram. The prefix selection prepends to the unit symbol, so only
gyieldsmg/g/kg. The SI base unit column still readskg. - The dimension column carries the ISO 80000 dimension symbols (L, M, T, I, Θ, N, J), for example
ML²T⁻³I⁻¹for voltage — not the unit symbol a second time. - Torque is spelled
Nm, without a multiplication dot: that is what the DCC export's unit translation expects.
Seeding is additive: only missing entries are inserted. An existing symbol — for instance the four rows V, A, Ω and Hz inherited from V1 — is neither duplicated nor overwritten. Every entry can afterwards be edited or deleted like a self-created record.
V1 installations
The Yii migration m260803_000001_seed_si_prefixes_and_physical_quantities delivers the same defaults to systems still running V1. uIDs and content are identical on both sides so that a later V1→V2 takeover (v1:sync) hits the same rows instead of inserting the catalog twice.
Overview¶
The AdminProvisionController manages quality provisions that serve as the basis for compliance with quality standards. Provisions define requirements that must be met during calibrations and tests.
Structure¶
Provisions are hierarchically organized:
Hierarchical structure
Each provision can contain multiple detail entries, which are ordered by a sort value.
Managing Provisions¶
Overview¶
Under Admin > Settings > Provisions, all quality provisions are listed:
| Field | Description |
|---|---|
| Name | Name of the provision |
| Description | Detailed explanation |
| Status | Active / Inactive |
| Sort Order | Display order |
Create New Provision¶
- Navigate to Admin > Settings > Provisions
- Click New Provision
- Enter name and description
- Set the sort order
- Save the provision
Measurement Ranges¶
Each provision carries rows describing one measurement range each, with the measurement uncertainty achievable there. Reachable via the row action Messbereiche on the provisions grid.
| Field | Description |
|---|---|
| Designation | What is measured, e.g. "Gleichspannung" |
| Mode | e.g. DCV, ACI, resistance. It counts for the accreditation scope: if calServer recognises a measuring function in it (without mode, in the designation), the row covers only measuring points of that function. The CMC check still matches by unit and range only |
| 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, such as a frequency band; the accreditation scope reads it as a frequency band in Hz |
| Uncertainty | What is achieved in this range |
| Resolution | Smallest step the measuring equipment resolves |
| Order | Position in the list |
Example: DC voltage capability
Provision: DAkkS Elektrik
- Gleichspannung, DCV, 0 ... 10 V, uncertainty 0.002 V, resolution 0.001 V
- Gleichspannung, DCV, 10 ... 100 V, uncertainty 0.02 V, resolution 0.01 V
Capability, not a requirement
The rows state what the laboratory can do (CMC) — not what has to be met. The completion check reads them as a lower bound: a measurement row stating a smaller uncertainty than the annex allows gets a notice. Environmental requirements such as "room temperature 23 +/- 2 °C" can at most go into the description as free text; a target range that ends up on the calibration certificate is maintained under Resources.
Accreditation scope per measuring point
From the same rows calServer derives at capture whether a measuring point lies within the accreditation scope; the certificate marks points outside with "*". Only provisions with the holder "Own lab" (or without holder) count, valid on the calibration date by "Valid from" and "Valid until", and rows with a unit. Details: Accreditation scope.
Sort Order¶
The sort order determines the sequence in which provisions and their details are displayed. Lower values appear first.
Sort order: 10 --> displayed first
Sort order: 20 --> displayed next
Sort order: 30 --> displayed last
Gaps in sort order
Use increments of 10 (10, 20, 30, ...) to allow inserting additional entries later without having to change existing sort orders.
Usage¶
Quality provisions are referenced in the following areas:
- Calibration orders: Assignment of relevant provisions to the order
- Test reports: Documentation of compliance
- Device records: Storage of device-specific requirements