PTB Digital Calibration Certificate (DCC)
Create and manage DCC calibration certificates in Memida. The free Memida Signing desktop app applies your company seal to the XML files. You can also verify existing seals without a Memida account or a certificate of your own.
Fig. 1: Machine-readable DCC data and a readable PDF representation of a calibration certificate
The Digital Calibration Certificate (DCC) developed by the Physikalisch-Technische Bundesanstalt (PTB) enables laboratories and recipients to exchange structured calibration data. PTB introduces the XML format.
Share structured calibration data
The XML schema defines the structure, required information and data types. An additional PDF representation makes the data readable and printable. PTB explains its structure and purpose.
Memida Signing seals unsealed DCCs of version 3.3.0. The app checks the XML against the PTB schema and for required seal information. It displays errors before approval.
Create, seal and manage DCCs in Memida
Fig. 2: Creating and sealing DCCs with Memida
Import your company certificate into the app and configure it for your company in Memida. You can then hand over calibration certificates directly:
- Create and review the calibration certificate in Memida.
- Select Seal and complete.
- Review the document, company and certificate in the app, then approve the request.
- Wait for confirmation of completion. Memida checks the sealed XML and creates the PDF representation.
The private key stays on your computer. The XML is sealed; the PDF representation does not receive a separate PDF seal. See the guides for details of approval in the app and completion in Memida. They also describe the alternative workflow using an XML download and subsequent upload.
You can seal DCCs from other systems locally without a Memida account. The app saves sealed copies and preserves the originals.
Import existing DCCs
Under Inspection reports → Import, you can import DCCs of versions 3.2.1 and 3.3.0. Review the detected inspection data and assign it to an existing item of inspection equipment. The original file is preserved. The Import calibration certificates guide explains the process.
The import checks the structure and the information that can be imported. Any detected XML signatures are treated as present but unverified. Use Memida Signing for cryptographic verification.
DCC and DAkkS eAttestation
An accredited body can issue a DCC as an eAttestation using its digital accreditation symbol. The calibration must fall within its scope of accreditation; the DCC format alone does not confirm accreditation. DAkkS explains eAttestations in PDF and XML.
Create and use DAkkS eAttestations describes the requirements and setup.
Frequently asked questions about DCC
Does sealing a PDF turn it into a DCC?
No. Memida Signing preserves the file format. A DCC requires a calibration certificate in the supported XML format.
Does seal verification also confirm the measurement results?
No. Seal verification evaluates the signature, certificate trust and, optionally, revocation status. It confirms neither measurement results nor DCC schema compliance or coverage by the scope of accreditation.