Procedure editor: build, version and run test sequences¶
24 July 2026
A test sequence sitting in a spreadsheet on a network drive is not a process, it is a file. Nobody knows which revision is authoritative, who touched it last, or whether yesterday's technician worked from the current version. calServer V2 therefore moved the test sequence into the application: create the procedure, define the test steps, release a version, run the measurement against it, all in one place.
Procedure, test steps, template¶
A procedure describes the method: calibration object, calibration method, measurement conditions, underlying standards, scope. It is managed on its own page with a grid, filters and the option to duplicate an existing procedure including its device type assignments.
The test steps are the measurements themselves: label, nominal value, unit, upper and lower tolerance, measurement point, order, remark for the technician. Besides numeric steps there are yes/no checks and ratings, which covers the visual inspection that produces no number.
The template is the frozen state of a sequence that gets instantiated over and over.
Assignment that applies by itself¶
A procedure can be assigned to device types and set as the standard test procedure per type. When a calibration is created, calServer pulls the right sequence automatically instead of making someone search for it. Resolution is unambiguous: an assignment on the device itself beats the type default, otherwise the type default applies.
Evaluation happens immediately¶
The runtime guides the technician through the procedure step by step and evaluates each reading on the spot: tolerances are parsed, limits and guardbands are calculated, tolerance usage and deviation are determined, pass/fail is set. SI prefix arithmetic handles mV, V and kV correctly against each other, including mixed prefixes between nominal value and tolerance. The technician sees the result at the step, not at the end when the report is printed.
For automated sequences the path outward stays open: automatic procedures are handed to Fluke MET/CAL and executed there.
Versions that survive an audit¶
Templates follow a clear lifecycle:
| Action | Effect |
|---|---|
| Upload or save from a calibration | New template at version 0.1 (draft) |
| New version | Minor increment, the previous one loses its "current" status |
| Approve | Major jump to 1.0, status "approved", the file becomes immutable |
| Release | Status "released", only possible for approved versions |
Every version remains individually viewable and downloadable. The audit question "which revision was used on 3 March?" is answered by the system rather than from memory.
JSON instead of Excel as the exchange format¶
Test sequences are serialised in the calserver.procedure format (JSON). That
replaces the old spreadsheet route and turns procedures into something you can
version, exchange between installations and, if you like, keep in source
control. From a running calibration, "save as template" turns the sequence
into a template; conversely "load template" instantiates the test steps into
a calibration.
Permissions are granted separately: viewing, editing and deleting procedures, templates and specifications are individual permissions. Being allowed to test does not imply being allowed to approve.
Details in the manual: Procedures and test steps, Test steps, Procedure templates.