<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>digical Blog</title>
    <subtitle>Insights on digital calibration, metrology software and what we learn building digical.</subtitle>
    <link href="https://digical.net/blog/en/feed.xml" rel="self"/>
    <link href="https://digical.net/blog/en/"/>
    <updated>2026-09-06T00:00:00Z</updated>
    <id>https://digical.net/blog/en/</id>
    <author>
        <name>digical UG (haftungsbeschränkt)</name>
    </author>
    <entry>
        <title>Reading a digital calibration certificate: the free DCC Viewer</title>
        <link href="https://digical.net/blog/en/dcc-viewer/"/>
        <updated>2026-09-06T00:00:00Z</updated>
        <id>https://digical.net/blog/en/dcc-viewer/</id>
        <summary>What a Digital Calibration Certificate (DCC) is, why it comes as an XML file, and how to read, check and export it as a PDF with our free DCC Viewer.</summary>
        <author>
            <name>digical team</name>
        </author>
        <content type="html">&lt;p&gt;More and more calibration laboratories deliver their results as a &lt;strong&gt;Digital
Calibration Certificate&lt;/strong&gt;, or DCC for short. The first encounter is usually
the same: an e-mail arrives with an &lt;code&gt;.xml&lt;/code&gt; attachment, you open it, and you
see a wall of tags instead of a certificate. The data is all there, but it is
written for machines. This post explains what a DCC is, why it looks the way
it does, and how to read one in seconds with the
&lt;a href=&quot;https://dcc-viewer.digical.net/&quot;&gt;DCC Viewer&lt;/a&gt;, a free tool we built for
exactly this moment.&lt;/p&gt;
&lt;h2 id=&quot;what-is-a-digital-calibration-certificate&quot; tabindex=&quot;-1&quot;&gt;What is a Digital Calibration Certificate? &lt;a class=&quot;heading-anchor&quot; href=&quot;https://digical.net/blog/en/dcc-viewer/#what-is-a-digital-calibration-certificate&quot; aria-hidden=&quot;true&quot;&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A calibration certificate documents that a measuring instrument was compared
against a reference, what the deviations were, and with which uncertainty. For
decades it has been a PDF or a sheet of paper. That is fine for reading, but
every value that needs to go into an instrument database, a quality report or
a control chart has to be typed off by hand.&lt;/p&gt;
&lt;p&gt;The DCC replaces the paper with a &lt;strong&gt;structured XML file&lt;/strong&gt;. The format was
developed by the Physikalisch-Technische Bundesanstalt (PTB), Germany&#39;s
national metrology institute, together with partners from industry and
accredited laboratories. It is defined by a published XML schema, so a DCC
from one laboratory has the same structure as a DCC from another and can be
processed by software without any guesswork.&lt;/p&gt;
&lt;p&gt;A DCC has two main parts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Administrative data&lt;/strong&gt;: the laboratory, its accreditation, the customer,
the item under test with its serial number, the responsible persons and the
calibration date.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Measurement results&lt;/strong&gt;: the measured quantities, reference values,
deviations and uncertainties. Quantities and units are expressed using the
D-SI model, a machine-readable notation for SI units, so a value like
&amp;quot;23.4 °C&amp;quot; carries its unit unambiguously.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The schema is versioned. PTB publishes new releases as the format evolves,
and every certificate states which version it was written against. A DCC can
also carry a digital signature, which lets the recipient verify that the file
is unchanged since the laboratory issued it.&lt;/p&gt;
&lt;h2 id=&quot;why-this-matters&quot; tabindex=&quot;-1&quot;&gt;Why this matters &lt;a class=&quot;heading-anchor&quot; href=&quot;https://digical.net/blog/en/dcc-viewer/#why-this-matters&quot; aria-hidden=&quot;true&quot;&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The point of the DCC is not to make certificates harder to read. It is to make
them &lt;strong&gt;usable by software&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Measured values can flow directly into instrument management, quality
systems or statistical evaluation, with no transcription errors.&lt;/li&gt;
&lt;li&gt;Expiry dates and conformity statements can be checked automatically.&lt;/li&gt;
&lt;li&gt;A certificate can be validated against the official schema, so a broken or
incomplete file is detected on arrival rather than during an audit.&lt;/li&gt;
&lt;li&gt;Laboratories and customers exchange one file in one format, whatever
systems they use.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For laboratories working under ISO/IEC 17025 and for companies with a large
instrument inventory, this removes a lot of manual work. The catch is that the
XML file itself is unreadable for humans. That is where a viewer comes in.&lt;/p&gt;
&lt;h2 id=&quot;the-dcc-viewer&quot; tabindex=&quot;-1&quot;&gt;The DCC Viewer &lt;a class=&quot;heading-anchor&quot; href=&quot;https://digical.net/blog/en/dcc-viewer/#the-dcc-viewer&quot; aria-hidden=&quot;true&quot;&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&quot;https://dcc-viewer.digical.net/&quot;&gt;DCC Viewer&lt;/a&gt; is a free web application
that turns a DCC into something you can read, check and hand on. There is no
account and no sign-up. You open the page, drop the XML file onto it, and the
certificate appears as structured blocks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;certificate information and calibration laboratory,&lt;/li&gt;
&lt;li&gt;customer and item under test,&lt;/li&gt;
&lt;li&gt;responsible persons and statements of conformity,&lt;/li&gt;
&lt;li&gt;calibration methods, measuring equipment and influence conditions,&lt;/li&gt;
&lt;li&gt;the measurement results as data tables and as charts.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;From these blocks you assemble your own report. Add the sections your
documentation needs, leave out the ones it does not, and export the result as
a &lt;strong&gt;PDF&lt;/strong&gt; with one click. Laboratories use this to give customers a readable
companion to the XML; customers use it to file a certificate the way they
always have while keeping the machine-readable original.&lt;/p&gt;
&lt;p&gt;A few details we consider important:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The certificate is validated.&lt;/strong&gt; The viewer reads the schema version
declared in the file and checks the certificate against the matching
official PTB schema, so any published DCC version is handled.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Nothing is stored.&lt;/strong&gt; The file is parsed in memory and discarded. It is
never written to disk, and nothing is sent to an AI service or any other
third party. Parsing is deterministic, which is what makes the tool usable
for calibration data at all.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two languages, kept apart.&lt;/strong&gt; The interface is available in English and
German. The certificate content is shown in whichever languages the DCC
itself declares, so a German user can read an English-only certificate with
a German interface.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The viewer handles one file at a time. It is meant for the moment a
certificate lands in your inbox, not for managing hundreds of them.&lt;/p&gt;
&lt;h2 id=&quot;when-one-file-is-not-enough&quot; tabindex=&quot;-1&quot;&gt;When one file is not enough &lt;a class=&quot;heading-anchor&quot; href=&quot;https://digical.net/blog/en/dcc-viewer/#when-one-file-is-not-enough&quot; aria-hidden=&quot;true&quot;&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;If you receive calibration certificates regularly, the next step is to keep
them together with the instruments they belong to. That is what the
&lt;a href=&quot;https://app.digical.net/&quot;&gt;digical app&lt;/a&gt; does: it stores DCCs alongside your
instruments, validates them on upload, tracks expiry dates and sends an e-mail
before a certificate becomes invalid. The report builder in the DCC Viewer is
the same one you will find there.&lt;/p&gt;
&lt;p&gt;Until then, the DCC Viewer is the quickest way to find out what is inside that
XML attachment. &lt;a href=&quot;https://dcc-viewer.digical.net/&quot;&gt;Try it with your next certificate.&lt;/a&gt;&lt;/p&gt;
</content>
    </entry>
    <entry>
        <title>Welcome to the digical blog</title>
        <link href="https://digical.net/blog/en/welcome/"/>
        <updated>2026-09-05T00:00:00Z</updated>
        <id>https://digical.net/blog/en/welcome/</id>
        <summary>Why we started this blog and what you can expect to read here.</summary>
        <author>
            <name>digical team</name>
        </author>
        <content type="html">&lt;p&gt;Welcome! On this blog we will write about digital calibration certificates,
metrology software, and what we learn while building digical.&lt;/p&gt;
&lt;h2 id=&quot;what-to-expect&quot; tabindex=&quot;-1&quot;&gt;What to expect &lt;a class=&quot;heading-anchor&quot; href=&quot;https://digical.net/blog/en/welcome/#what-to-expect&quot; aria-hidden=&quot;true&quot;&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Practical guides on digital calibration certificates (DCC)&lt;/li&gt;
&lt;li&gt;Updates on new features in the digical app&lt;/li&gt;
&lt;li&gt;Insights from metrology and quality assurance&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;get-in-touch&quot; tabindex=&quot;-1&quot;&gt;Get in touch &lt;a class=&quot;heading-anchor&quot; href=&quot;https://digical.net/blog/en/welcome/#get-in-touch&quot; aria-hidden=&quot;true&quot;&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Have a topic you would like us to cover? Write to us and let us know.&lt;/p&gt;
</content>
    </entry>
</feed>
