Updated: 20 September 2026
A Digital Calibration Certificate (DCC) is a structured calibration record designed for both people and software. Rather than presenting results only through a conventional document layout, it identifies values, units, uncertainties, methods, instruments, and related information in a form that digital systems can process.
The Physikalisch-Technische Bundesanstalt (PTB) describes the DCC as an XML-based digital counterpart to a conventional calibration certificate. It can carry the information required for reporting under ISO/IEC 17025 while making that information available for automated exchange.
This distinction matters because most calibration certificates are still prepared mainly for human readers. A technician opens a PDF, confirms the instrument identity, reviews the results and measurement uncertainty, checks the conditions, and decides whether the calibration is suitable for its intended use.
That process works, but it becomes costly when an organisation manages hundreds or thousands of instruments. Certificate data often has to be copied into calibration-management software, asset registers, enterprise systems, or quality databases. Every manual transfer takes time and introduces another chance for error.
A DCC is intended to close this gap between the calibration laboratory and the customer’s systems.
What Is a Digital Calibration Certificate?
A DCC represents calibration information as structured data. PTB’s approach uses XML, or Extensible Markup Language, to identify what each element means and how it relates to the rest of the certificate.
This makes a DCC different from a document that is merely electronic. PTB distinguishes between two important properties:
- Machine-readable: Software can import the information automatically.
- Machine-interpretable: Software can recognise the meaning of the information and process it without a person mapping every field.
A PDF can be a complete and valid calibration certificate. Yet software may see it only as text, coordinates, tables, and formatting. A DCC records the relationships among measurement values, units, uncertainties, methods, instruments, environmental conditions, and administrative information.
DCC vs. a Conventional PDF Certificate
| Feature | Conventional PDF certificate | Digital Calibration Certificate |
|---|---|---|
| Primary reader | Human | Human and software |
| Structure | Visual document layout | Structured XML data |
| Automatic import | Usually requires extraction, mapping, or manual entry | Designed for automated processing |
| Meaning of fields | Inferred from labels and layout | Defined through a structured schema |
| System integration | Possible with additional processing | A core design purpose |
| Human-readable display | Built in | Can be rendered in a readable format |
A PDF does not become a DCC simply because it is stored or sent electronically. The defining feature is structured, machine-interpretable calibration data.
Does a DCC Replace ISO/IEC 17025?
No.
A DCC changes the way calibration information is represented and exchanged. It does not replace the requirements for laboratory competence, valid methods, metrological traceability, suitable equipment, or correct evaluation of measurement uncertainty.
PTB states that a DCC can contain the information supplied by a conventional certificate and support ISO/IEC 17025 reporting requirements while adding machine readability and interpretability.
The same technical questions still have to be answered:
- Was the calibration performed competently?
- Are the results technically valid?
- Was measurement uncertainty evaluated and reported correctly?
- Is metrological traceability established where required?
- Is the calibration scope suitable for the instrument and its intended use?
A different file format cannot turn poor calibration work into sound calibration work.
Why DCCs Received More Attention in 2026
DCC development has been underway for several years. During 2026, more of the discussion shifted from general architecture to practical use in individual calibration disciplines.
Temperature and Humidity
PTB published Expert Report DKD-E 5-3, providing guidance and XML examples for digital calibration certificates in thermodynamic calibration.
The examples address:
- Temperature calibration using a Pt100 thermometer
- Relative-humidity calibration using a hygrometer
These examples show how a general DCC schema can be applied to normal calibration work. Laboratories can study a working representation rather than relying only on an abstract data model.
Force
PTB also published Expert Report DKD-E 3-1 on applying the DCC schema to force calibration.
The report explains how DCC elements can be used for calibrations associated with ISO 376 and provides XML examples for force-calibration cases. This gives laboratories working with force transducers, load cells, proving instruments, and related equipment a practical reference point.
Laboratory-Wide Generation in Mass Metrology
A September 2026 article in Measurement: Digitalization describes a laboratory-wide digitalisation framework developed at TÜBİTAK UME’s Mass Laboratory. The study examines automated, interoperable DCC generation as part of a broader system for exchanging calibration results.
This reflects a useful change in focus. The question is no longer only, “What should a DCC contain?” Laboratories are also asking, “How can we generate, review, issue, and exchange DCCs during routine work?”
What Does a DCC Contain?
PTB’s schema documentation describes a structured certificate with major sections for administrative data and measurement results. The root structure may also contain optional documents or comments.
A simplified conceptual example could look like this:
<digitalCalibrationCertificate>
<administrativeData>
laboratory
customer
calibrated item
responsible persons
certificate information
</administrativeData>
<measurementResults>
measurement values
units
uncertainty information
environmental conditions
methods
</measurementResults>
</digitalCalibrationCertificate>This example is illustrative only. A laboratory implementing DCCs should use the current official schema and relevant discipline-specific guidance instead of creating an incompatible local XML format.
Why Structured Units and Quantities Matter
Consider a result written as:
10.002 mm
A person can separate the numerical value from the unit and may understand the measurement from the surrounding table. Software needs those relationships to be stated explicitly and consistently.
A digital system may need to identify:
- The numerical value
- The unit
- The quantity being measured
- The calibrated item and measurement point
- The uncertainty associated with the result
- Any correction, deviation, or interpretation attached to the value
Structured data reduces the need to infer these relationships from labels and page layout.
How Manufacturers Could Use DCC Data
The main benefit appears when calibration data can move directly into the customer’s existing processes.
A manufacturer could use structured certificate data to update equipment records, import results into calibration-management software, monitor drift, or connect calibration information with quality and manufacturing systems. Approved rules could also flag results that need technical review.
Possible uses include:
- Updating an instrument’s calibration record
- Importing results into asset, maintenance, or quality-management software
- Comparing results with internal acceptance criteria
- Tracking drift across successive calibration events
- Connecting results with manufacturing systems or digital twins
- Transferring correction and uncertainty data without retyping it
- Triggering a review when a result crosses a defined limit
- Maintaining a searchable calibration history
Not every decision belongs in an automated workflow. Software can identify exceptions, but fitness-for-use decisions, measurement-risk assessments, and reviews of possible product impact may still require competent technical judgment.
DCCs and Calibration Drift
Historical analysis is one of the clearest applications for structured calibration data.
Suppose a micrometer is calibrated repeatedly over several years. If every result exists only in a separate PDF, a quality engineer may have to open each certificate and build a trend table manually.
If the same measurement points are stored in a consistent structure, software can compare results across successive calibrations. This can make it easier to investigate:
- Long-term drift
- Changes in correction
- Changes in reported uncertainty
- Repeated out-of-tolerance behaviour
- Whether the current calibration interval remains appropriate
A DCC does not determine the correct calibration interval. It makes the supporting evidence easier to retrieve and analyse.
DCCs and Measurement Uncertainty
Measurement uncertainty shows both the value and the risk of machine-interpretable calibration data.
A structured system can preserve the relationship between a result, its unit, and its associated uncertainty. Problems arise when downstream software treats uncertainty as a standalone number without understanding how it was defined.
A system may need to distinguish among:
- Standard and expanded uncertainty
- Coverage factor
- Relevant coverage assumptions
- Correction and measured deviation
- Different uncertainties at different calibration points
Machine-readable data still needs correct metrological meaning. Better formatting does not remove the need for informed interpretation.
Digital Signatures, Integrity, and Authenticity
Digital calibration is not just a formatting task. Customers need confidence that a certificate is authentic, complete, and protected against undetected changes.
A mature DCC process may need controls for:
- Identifying the issuing laboratory
- Recording responsible and authorised persons
- Protecting document integrity
- Managing versions, corrections, and revisions
- Securing transmission
- Preserving records for the required period
- Validating the certificate against the applicable schema
These controls should cover the full information flow, from data capture to long-term storage. Adding them after an XML file has been generated is rarely enough.
Could DCCs Help NABL-Accredited Laboratories in India?
The DCC work discussed here is international and closely associated with PTB and related digital-metrology programmes. It does not follow that every NABL-accredited laboratory in India must issue DCCs.
Unless NABL, a regulator, an applicable scheme, or a customer contract establishes a specific requirement, laboratories should not present DCC adoption as a general condition of NABL accreditation.
The practical opportunity is still significant. Indian laboratories serving automotive, aerospace, electronics, pharmaceutical, automated manufacturing, and other data-intensive industries may receive more requests for results that can pass directly into customer systems.
Learning the DCC architecture can help a laboratory prepare for those requests without claiming that a mandatory requirement exists.
Requirement and readiness are not the same thing. DCC capability is best treated as preparation for structured digital exchange unless a competent authority or contract makes it compulsory.
Calibration Fields With DCC Guidance or Examples
| Measurement area | Published material | Practical significance |
|---|---|---|
| Mass | Existing guidance and a September 2026 laboratory-wide implementation study | Demonstrates progress toward automated certificate generation at laboratory scale |
| Gauge blocks | DKD-E 4-3 and a good-practice XML example | Supports dimensional calibration and industrial quality control |
| Temperature | DKD-E 5-3 and a Pt100 example published in 2026 | Provides a practical thermometry example |
| Humidity | DKD-E 5-3 and a relative-humidity example published in 2026 | Extends structured calibration data into humidity calibration |
| Force | DKD-E 3-1 guidance and XML examples published in 2026 | Shows how DCC elements can be mapped to ISO 376-related calibration |
Before beginning an implementation, laboratories should check the current schema and the latest guidance for the relevant discipline. DCC documentation continues to develop as laboratories gain practical experience.
How Calibration Laboratories Can Prepare
A laboratory does not need to replace its entire certificate system at once. A small, controlled pilot is usually the better place to start.
First, map the existing certificate process. Identify where instrument details, methods, environmental conditions, results, uncertainty information, and traceability records originate. Then locate every point where staff re-enter the same data into another system.
Internal standardisation should come before external automation. Consistent equipment identifiers, units, terminology, and data-ownership rules make later exchange far easier.
The laboratory can then review the current DCC schema and select one calibration family for a pilot project. Generated certificates should be validated against the schema and compared with the laboratory’s approved technical records. Human review should remain in place where results are unusual or professional judgment is required.
Automating a weak process rarely repairs it. More often, it lets the same weakness travel faster and become harder to spot.
What Customers Should Ask Their Calibration Laboratories
Customers interested in structured calibration data can ask:
- Can you provide calibration results in a machine-readable format?
- Is a DCC available for this calibration discipline?
- Which schema and version do you use?
- Can the data be imported into our asset, quality, or calibration system?
- Do you also provide a human-readable rendering?
- How do you protect authenticity and document integrity?
- How are revisions and corrected certificates issued?
For many services, the answer will still be “PDF only.” Asking is still worthwhile. It reveals how prepared the calibration supply chain is for structured exchange.
What Should Not Be Automated Blindly
DCCs can remove a great deal of clerical work. They should not allow software to make silent technical decisions that the available data cannot support.
Extra care is needed when dealing with:
- Acceptance decisions based on incomplete tolerances
- Assessments of previous measurements after an out-of-tolerance result
- Changes to calibration intervals
- Fitness-for-use decisions
- Unusual drift
- Uncertainty interpretation for a new application
Software can organise evidence, apply approved rules, and flag exceptions. It should not conceal assumptions or produce conclusions that the calibration data does not justify.
A Practical DCC Workflow
A digital calibration workflow might proceed as follows:
- The instrument enters the calibration laboratory.
- The laboratory information system identifies the item and applicable method.
- Measurement equipment records or transfers results digitally.
- Validated software processes the data.
- An authorised technical reviewer confirms the results.
- The system generates a DCC using the applicable schema.
- The customer receives the structured certificate and, where required, a human-readable rendering.
- The customer’s software validates and imports the DCC.
- Approved values update the instrument history.
- Configured exceptions are sent for competent review.
The crucial requirement is validated software.
An incorrect mapping does not become safer when it is automated. It just moves the error faster.
Why DCCs Matter to Digitally Managed Manufacturing
Modern production systems generate large amounts of structured information. Calibration often breaks that flow.
A production line may create thousands of machine-readable records, yet the measuring instrument supporting that process can return from calibration with a PDF that someone must open, read, and transcribe.
A DCC addresses that disconnect. It allows calibration information to join the same data infrastructure as asset records, manufacturing results, quality information, and measurement history.
Why 2026 Matters
No single publication makes 2026 decisive. The signal comes from several related developments:
- Continued maintenance of a formal XML schema
- More guidance for individual calibration disciplines
- Practical examples for temperature and humidity
- New guidance for force calibration
- Existing examples for gauge blocks
- Research on automated DCC generation across a mass laboratory
- International work on implementation, software, schemas, and semantics
Together, these developments suggest that DCC work is moving from conceptual design into operational digital metrology.
Adoption remains uneven, and PDF certificates will stay common for some time. The direction is clearer, though. Calibration data is beginning to move from documents intended mainly for people toward structured records that people and systems can use together.
Frequently Asked Questions
What is a Digital Calibration Certificate?
A DCC is a structured digital representation of calibration information. It allows software to read and interpret certificate data automatically. PTB’s approach uses XML for structured information exchange.
Is a PDF calibration certificate a DCC?
Not by itself. A PDF may be a valid electronic calibration certificate, but a DCC contains structured, machine-readable and machine-interpretable data. The distinction concerns data structure, not merely electronic delivery.
Can a DCC meet ISO/IEC 17025 reporting requirements?
PTB states that a DCC can contain the information provided by a conventional certificate and support ISO/IEC 17025 reporting requirements while adding machine readability and interpretability. The laboratory must still meet all applicable competence and technical requirements.
Are DCCs mandatory for NABL-accredited laboratories in India?
DCC issuance should not be described as a general NABL requirement unless a current NABL document, regulation, applicable scheme, or customer contract establishes that requirement. In other cases, DCC capability is best understood as preparation for structured digital exchange.
Which calibration areas have DCC guidance or examples?
PTB and DKD materials include work related to mass, gauge blocks, temperature, humidity, and force. Implementers should check the current schema and latest discipline-specific guidance before starting a project.
Why are DCCs useful for manufacturers?
Structured data can reduce manual entry, connect calibration results with asset and quality systems, support drift analysis, and make exception-based review easier. These benefits depend on accurate mappings, validated software, and suitable technical oversight.