Calibration of o-sensors? Is that possible? Some inputs from the last meeting in Berlin

on . . Hits: 15739

wg41 berlin meeting  Two points of view. Two ways of seeing calibration of Instrument Odour Monitors (in short here, o-sensors). The 29th and 30th of August, the Working Group (WG) 41 committed to the new standard on o-sensors, met in Berlin, Germany to discuss a bit more about the text. This time, there were some very hot discussions on the interesting issue of o-sensor calibration. The tense atmosphere was broken from time to time by the pause for coffees, but all in all, everybody was enjoying the fascinating discussions being hold in the meeting room of the Institute for Materials Research and Testing in Berlin.

   Like in tennis matches, the ball went from one side to the other side of the court. The question is the following: Could a non-specific o-sensor be used on any application? That is, could an o-sensor that is performing fine in a composting site, be used also in an oil refinery? In that case, is there any way to prove that the quality of the results is transferable? should we define procedures to calibrate o-sensors on site? Which is the Certified Reference Material (CRM) to calibrate the o-sensor? is it possible to design a CRM for quality procedures? These and more questions were addressed during these 2-day meetings.

    There are two kinds of o-sensor vendors: the goodies and the baddies. Both sell o-sensors for many applications, but one of them follows the (would be) EN standard on Instrumental Odour Monitoring and the other one doesn't. One of them will invest time and economic resources for a better product and the other one will not. This is one of the reasons why standards are for, to define the filter between good and bad practices.

   Now, who defines what is right or wrong? in this case an open group formed by over 20 experts from different fields and different European countries who reach to a set of standards through consensus. However, consensus was at stake this time. That is why an important part of the task group dedicated to o-sensor calibration met in the last ISOEN conference in Montreal. After that meeting in Montreal, a document was produced and sent to the WG. Three months later, the content of this document was discussed in Berlin.

   As mentioned before the essence of this document is that it is important to consider at least two different types of situations for instrumental odour monitoring: o-sensors that are designed and provided directly connected to the final application/user and 'multi-purpose' instruments that are designed and provided to be used in different situations, which are not specifically defined at the moment the instrument is installed.

   According to the EN 14181, there are three Quality Assurance Levels (QAL):

  • QAL1 relates to the certification of the instrument. The QAL 1 sets a procedure to demonstrate that the o-sensor is suitable for the intended purpose before installation.
  • QAL2 is the calibration against the standard reference method (in this case dynamic olfactometry). This is made on-site.
  • QAL3 determines whether zero and span drift are within defined limits along the time. This is usually made through the Continuous Quality Assurance Procedure of the operator

  These quality assurance levels are set for Automatic Measuring Systems (AMS), however the o-sensors are a very specific type of AMS. Do the o-sensors need to comply with these three QAL? This and more questions are being addressed at this moment. The final answer?... well as mentioned, there is no consensus yet ;-).

  Here a picture of the whole team:

wg41 berlin

   If your country is not represented in this Working Group (WG), why don't you join in? you can get access to the around 100 documents of this WG2. There is always a place here for any person interested on this subject. Feel free to contact your national standardization body in the case of CEN members to get in touch with this group. Even if you are not European, you can get access to all the documentation published in this group, provided that your country has an organization member of the ISO. Just contact your national representative body and ask them to link you to the CEN Technical Comittee 264 Working Group 41. You are more than welcome!

   If you find this article interesting, you might also be interested in these articles:

Comments (0)

There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.
Attachments (0 / 3)
Share Your Location

Please note that this site uses cookies in order to work properly.

See more about our cookie policy Learn more

I understand

Please read the following to learn more about our cookies policy:


What are cookies?

   A cookie is a text file stored in a user’s web browser on any device they use to access a website that holds information regarding the user’s visit, such as preferences. When the user returns, the browser provides the cookie with the stored information to the site.

What cookies are used for?

   Cookies are used for adjusting a website’s content to fit a user’s preferences and optimize the website. They store useful information that improve the user’s experience of a website. They are most commonly used for:

  •     Recognizing the type of device a user is browsing with and any preferences applied to optimize the website specifically for the device.
  •     Creating statistics that help website owners to understand how their users interact with their website, which allows them to improve their structure and content.

What types of cookies are used?

   There are two types of cookies: persistent cookies and session cookies. Persistent cookies remain on your hard drive for a period of time specified in the cookie’s file parameters or until removed manually. When you return to a website and it requires you to login again despite previously storing your login information, it is usually because the persistent cookie expired; this helps to increase security while maintaining accessibility.

   Session cookies, on the other hand, are used temporarily and expire once the website or browser is closed. They are used to track user activity on a website during a single visit. When a website requires that you verify your age or location once every visit before allowing you to view content and without requiring additional personal details, that is a session cookie at work.

Do cookies include personal data?

   If there is a need for the collection of personal information, such as for creating accounts, then cookies may store personal information. However, it is required by data protection law that users are informed of the collection of personal data. This data will also be encrypted to render it inaccessible for unauthorized users.

Managing cookies

   By default, browsers are configured to accept cookies. However, these settings may be changed to block cookies entirely, or to inform the user each time they are used. Detailed information about cookies and the options associated with them are available in each browsers’ settings.

Which cookies does collect collect cookies for 2 purposes:

  • Register statistical data.
  • Set language preferences.

   In addition we use third party cookies through Statcounter to collect different data.

StatCounter Analytics Cookies

   StatCounter is a web analytics service. We use StatCounter to track activity on our website. These stats help us to understand how people are interacting with our website and to improve the design and functionality of our site so that we can offer a better online experience to our visitors. If you visit, a StatCounter analytics cookie (called "is_unique") may  be placed in your browser.  This cookie is used only to determine whether you are a first-time or returning visitor and to estimate unique visits to the site. No personal information is stored in the cookie.

Refuse Statcounter cookies.

You may set your browser to refuse/accept StatCounter analytics cookies by clicking here.


    • Your decision to refuse/accept StatCounter analytics cookies applies to all websites which use the StatCounter service (including the StatCounter site itself).
    • If you refuse all StatCounter analytics cookie, a refusal cookie (called "refusal_cookie") will be set to remember this preference and any existing StatCounter analytics cookies in your browser will be destroyed.
    • If you delete/remove/destroy the refusal cookie, you must revisit this page in order to re-set your preference.
    • The refusal cookie is set only for your current browser and machine. If you use multiple browsers/machines, you must set a refusal cookie in each case.
    • You can also change your cookie settings directly in your browser. Learn more about cookies and how to manage them here:
    • Or you can learn about how to adjust cookie settings for specific browsers here: