calServer News¶
What has changed in calServer, explained briefly and without release-note prose. Full technical descriptions live in the manual or in the administration section, linked at the end of each post.
2026¶
November 2026¶
- Beta: test plan editor, runs at the workstation and camera reading Test plans are written as scripts, the calServer Runner executes them at the workstation with connected instruments through driver profiles, and the webcam reads displays without an interface. Specification, test plan, driver profile and workstation stay separate and only form the procedure in the calibration.
August 2026¶
- Sealing in calServer: which seal belongs on which certificate Company seals, accreditation seals such as the DAkkS seal, personal signatures and certificates from an in-house PKI. A rule decides which seal may go on which certificate, and the private key stays with the laboratory.
July 2026¶
-
DCC without detours: digital calibration certificates straight from calServer Calibration certificates following the PTB schema 3.3.0 are produced natively, with an embedded PDF, schema validation before delivery and an API endpoint that lets customers and goods-receipt systems collect them themselves.
-
A report engine with a JSON data source: report templates without SQL Report templates no longer contain SQL; they read a defined data set with readable field names. The same template runs on MySQL, PostgreSQL and Microsoft SQL Server, and existing templates keep running unchanged.
-
Procedure editor: build, version and run test sequences Procedures and test steps are maintained in the system instead of in spreadsheets, templates pass through draft, approval and release, and the runtime evaluates every reading immediately.
-
MET/TEAM sync: several instances, one inventory, nothing lost calServer synchronises against any number of MET/TEAM instances at once. A transactional outbox makes sure capture continues even when the far side is currently unreachable.