<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://www.alamsekitar.com.my/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.alamsekitar.com.my/" rel="alternate" type="text/html" /><updated>2026-06-22T09:03:10+00:00</updated><id>https://www.alamsekitar.com.my/feed.xml</id><title type="html">Mesra Alam Sekitar Sdn Bhd | Continuous Emission Monitoring System | Malaysia</title><subtitle>DOE iRemote-registered CEMS consultants since 2010. Mesra Alam Sekitar designs, installs, certifies (QAL 2/QAL 3) and maintains Continuous Emission Monitoring Systems for Malaysian industry — and helped write the DOE CEMS Guidelines.</subtitle><entry><title type="html">MS 1596, ISO 9096 and EN 13284: how Malaysia’s stack-test standard fits the international picture</title><link href="https://www.alamsekitar.com.my/insights/ms-1596-iso-9096-en-13284-particulate-standards/" rel="alternate" type="text/html" title="MS 1596, ISO 9096 and EN 13284: how Malaysia’s stack-test standard fits the international picture" /><published>2026-06-22T02:00:00+00:00</published><updated>2026-06-22T02:00:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/ms-1596-iso-9096-en-13284-particulate-standards</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/ms-1596-iso-9096-en-13284-particulate-standards/"><![CDATA[<p><em>The reference methods behind your CEMS — Part 3 of 5. A series for industry and regulators, drawn from the DOE CEMS Guidelines (Version 8, 2025) we helped develop and the standards-committee work behind MS 1596.</em></p>

<p>When your CEMS is calibrated, the <a href="/insights/qal2-calibration-variability-test-cems/">QAL2 test</a> measures it against a <strong>Standard Reference Method (SRM)</strong> — a <a href="/insights/why-cems-needs-manual-stack-tests-srm/">manual stack test</a> run alongside your analyser. For particulate (dust), that manual method is a <em>gravimetric isokinetic</em> measurement: pull a sample from the flue at the right velocity, catch the dust on a filter, weigh it, report the concentration.</p>

<p>But read three different stack-test reports and you’ll see that same method called by three different names — <strong>MS 1596</strong>, <strong>ISO 9096</strong>, <strong>EN 13284</strong>. It’s a reasonable moment to ask: are these competing methods? Which one applies in Malaysia? And does it matter which your tester quotes?</p>

<p>The short answer: they are <strong>not three methods</strong>. They are <strong>one method, adopted at three levels</strong> — and knowing how they relate tells you a lot about what your dust data can and can’t be trusted to do.</p>

<h2 id="one-method-adopted-three-times">One method, adopted three times</h2>

<p>Strip away the cover pages and all three describe the same physical procedure: isokinetic extraction, filtration, gravimetric determination of mass concentration. What differs is <em>who adopted it</em> and <em>what dust range they tuned it for</em>.</p>

<figure class="fig lineage">
<p class="fig-title">One method, three standards</p>
<div class="lin-cols">
  <div class="lin-col iso">
    <span class="lin-tier">Tier 01 · International root</span>
    <span class="lin-code">ISO 9096</span>
    <span class="lin-full">Stationary source emissions — manual determination of mass concentration of particulate matter</span>
    <dl>
      <dt>Role</dt><dd>The origin method. The other two are adoptions of it.</dd>
      <dt>Range</dt><dd>~20–1000 mg/m³ — the higher-load global baseline.</dd>
      <dt>Current edition</dt><dd>ISO 9096:2017 (3rd) — succeeding 2003 and 1992.</dd>
    </dl>
  </div>
  <div class="lin-col en">
    <span class="lin-tier">Tier 02 · European adoption</span>
    <span class="lin-code">EN 13284-1</span>
    <span class="lin-full">Determination of <em>low-range</em> mass concentration of dust — manual gravimetric method</span>
    <dl>
      <dt>Role</dt><dd>Europe's refinement, sharpened for low-dust (post-abatement) stacks.</dd>
      <dt>Range</dt><dd>Below 50 mg/m³; validated down to ~5 mg/m³.</dd>
      <dt>Plugs into</dt><dd>EN 14181 as the SRM for QAL2 / AST.</dd>
    </dl>
  </div>
  <div class="lin-col ms">
    <span class="lin-tier">Tier 03 · Malaysian adoption</span>
    <span class="lin-code">MS 1596</span>
    <span class="lin-full">Determination of concentration and mass flow rate of particulate in flue gas, stationary sources</span>
    <dl>
      <dt>Live edition</dt><dd>MS 1596:2003 — built on ISO 9096:1992 + ISO 10780.</dd>
      <dt>Status</dt><dd><span class="lin-badge live">2003 · confirmed 2013</span><span class="lin-badge draft">revision in progress</span></dd>
      <dt>Role in Malaysia</dt><dd>The DOE-referenced SRM for compliance stack tests.</dd>
    </dl>
  </div>
</div>
<p class="fig-note">EN 13284 and MS 1596 are <strong>siblings, not a chain</strong> — both adopt ISO 9096 independently.</p>
<figcaption>The same manual gravimetric isokinetic method, adopted at three levels. Each adoption inherits from the ISO root, not from the others.</figcaption>
</figure>

<h2 id="iso-9096--the-international-root">ISO 9096 — the international root</h2>

<p><strong>ISO 9096</strong> is the origin. It sets out the manual gravimetric reference method for measuring dust mass concentration in a flue, and it’s written for the <em>general</em> case — concentrations from roughly <strong>20 mg/m³ up to 1000 mg/m³</strong>. It’s the baseline that national and regional bodies adopt and localise.</p>

<p>It has also moved on over the years: the current edition is <strong>ISO 9096:2017</strong>, the third, which replaced the 2003 edition, which in turn replaced the original <strong>1992</strong> version. That detail matters in a moment, because Malaysia’s standard is anchored to a specific edition of ISO 9096 — and not the newest one.</p>

<h2 id="en-13284-1--europes-low-dust-refinement">EN 13284-1 — Europe’s low-dust refinement</h2>

<p>Europe adopted the same ISO method but ran into a practical problem: modern abated stacks — bag filters, scrubbers, electrostatic precipitators — emit <em>very little</em> dust. Down near a few mg/m³, the baseline ISO accuracy starts to degrade. So CEN published <strong>EN 13284-1</strong>, a version of the method <strong>purpose-built for low dust concentrations below 50 mg/m³</strong>, validated in field tests around <strong>5 mg/m³</strong>.</p>

<p>EN 13284-1 is the <strong>SRM that EN 14181 consumes</strong>. When a European CEMS goes through QAL2 or its annual AST, the manual measurements it’s calibrated against are EN 13284-1 measurements. (We mapped that QA chain — QAL1 → QAL2 → QAL3 → AST — in the <a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">Operating series</a>.)</p>

<h2 id="ms-1596--malaysias-adoption">MS 1596 — Malaysia’s adoption</h2>

<p><strong>MS 1596</strong> is Malaysia’s national adoption of the same method. The edition in force is <strong>MS 1596:2003</strong>, confirmed in 2013, and it is built on <strong>ISO 9096:1992 plus ISO 10780</strong> (the companion standard for duct velocity and flow). It covers a wide range — roughly <strong>0.005 to 10 g/m³</strong> (that is, 5 to 10,000 mg/m³) — and the DOE references it as the SRM for compliance stack testing in Malaysia.</p>

<p>There’s one line in MS 1596:2003 worth knowing, because it explains everything that follows: for concentrations <strong>below 0.050 g/m³ (50 mg/m³), the method’s inaccuracy exceeds ±10%.</strong> That’s not a flaw — it’s the honest limit of the 1992-era method at low dust. And it’s <em>exactly</em> the range that EN 13284-1 was created to handle well.</p>

<h2 id="siblings-not-a-chain">Siblings, not a chain</h2>

<p>Here’s the relationship people most often get wrong. It’s tempting to picture ISO → EN → MS as a single descending line. It isn’t.</p>

<p>EN 13284 and MS 1596 are <strong>both adoptions of ISO 9096, made independently of each other</strong>. Europe took the ISO root and refined it for low dust; Malaysia took the ISO root (the 1992 edition) and localised it for national use. So:</p>

<ul>
  <li><strong>MS 1596 ≈ ISO 9096</strong> (1992 vintage), across a broad dust range.</li>
  <li><strong>EN 13284-1 ≈ ISO 9096</strong> tuned specifically for low concentrations.</li>
</ul>

<p>They are siblings descended from a common parent — not a parent and child. Quoting “MS 1596” and “ISO 9096” on the same report isn’t a contradiction; it’s naming the adoption and its root.</p>

<h2 id="why-the-low-dust-distinction-matters-in-malaysia">Why the low-dust distinction matters in Malaysia</h2>

<p>This isn’t academic. Malaysia’s stacks are getting cleaner. A modern palm-oil-mill boiler with proper abatement can emit dust low enough that it sits in the very range where the <strong>1992-based MS 1596 loses accuracy</strong> — and where <strong>EN 13284-1 is at its strongest</strong>.</p>

<p>That gap is precisely why <strong>MS 1596 is being revised to align with the current ISO 9096</strong> — work now under way in the national standards committee. As the revision moves the Malaysian standard onto the present ISO edition, it inherits much of the low-range thinking that Europe built into EN 13284-1. We’ll cover what that revision actually changes in <strong>Part 4</strong> of this series.</p>

<h2 id="where-this-sits-relative-to-cems-calibration">Where this sits relative to CEMS calibration</h2>

<p>One last clarification, because it’s the source of a lot of confusion: <strong>none of these three standards are the CEMS calibration framework.</strong> They supply the <em>SRM</em> — the manual paired measurements. The calibration framework is the QA programme that <em>consumes</em> those measurements: in Europe, <strong>EN 14181</strong> (QAL2 / QAL3 / AST); in Malaysia, the <strong>DOE CEMS scheme</strong>, which references <strong>MS 1596</strong> as its SRM.</p>

<p>So when your CEMS is certified, the chain is: your analyser is regressed against MS 1596 manual measurements during <a href="/insights/qal2-calibration-variability-test-cems/">QAL2</a>, and that calibration is what makes your continuous data defensible. The standard underneath the SRM is the foundation the whole calibration stands on — which is why it’s worth knowing which one you’re standing on.</p>

<p><strong>Running a compliance stack test or a QAL2 and want the reference method done right?</strong> <a href="/#contact">Talk to us</a> — we run CEMS and reference-method work for facilities across Malaysia, and we sit on the committee revising MS 1596.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/qal2-calibration-variability-test-cems/">QAL2 and the Calibration &amp; Variability Test: certifying your CEMS against the SRM</a></li>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST</a></li>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility, refer to the current Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, the DOE CEMS Guidelines, and the current editions of MS 1596, ISO 9096 and EN 13284, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 3 of our Reference Methods series: the three particulate standards you'll see quoted on a stack-test report — MS 1596, ISO 9096 and EN 13284 — are one manual gravimetric method adopted at three levels. How they relate, where Malaysia's MS 1596 sits, and why the low-dust distinction matters.]]></summary></entry><entry><title type="html">Why a continuous monitor still needs manual stack tests</title><link href="https://www.alamsekitar.com.my/insights/why-cems-needs-manual-stack-tests-srm/" rel="alternate" type="text/html" title="Why a continuous monitor still needs manual stack tests" /><published>2026-06-22T01:30:00+00:00</published><updated>2026-06-22T01:30:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/why-cems-needs-manual-stack-tests-srm</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/why-cems-needs-manual-stack-tests-srm/"><![CDATA[<p><em>The reference methods behind your CEMS — Part 1 of 5. A series for industry and regulators, drawn from the DOE CEMS Guidelines (Version 8, 2025) we helped develop and the standards-committee work behind MS 1596.</em></p>

<p>You installed a Continuous Emission Monitoring System for a good reason: so you wouldn’t need someone climbing the stack with a sampling train every time you wanted to know your emissions. The analyser reads around the clock, the data flows to the DOE, and the job is done — automatically.</p>

<p>So it surprises a lot of plant managers to learn that the rules <em>still</em> send a team up the stack with manual gear, on day one and every year after. If the CEMS is the whole point, why does a manual test keep coming back?</p>

<p>The answer is the subject of this whole series, and it starts with a simple fact about what your CEMS is actually doing.</p>

<h2 id="your-cems-measures-a-proxy-not-the-dust-itself">Your CEMS measures a proxy, not the dust itself</h2>

<p>A continuous analyser doesn’t weigh your emissions. It can’t — there’s no scale on a chimney. Instead it measures something it <em>can</em> sense continuously and quickly: a beam of light scattered or blocked by passing dust, the absorption of a gas at a certain wavelength, and so on. That raw signal rises and falls with your emissions, but it isn’t a concentration. It’s a <strong>proxy</strong> — a number that <em>stands in for</em> the real thing.</p>

<p>To turn that proxy into a defensible “X mg/m³,” the analyser needs to be told what its signal means in real units. And the only way to know what the real value is, is to measure it the slow, honest way: pull a physical sample from the flue, capture the dust on a filter, and <strong>weigh it.</strong> That manual, first-principles measurement is the <strong>Standard Reference Method (SRM)</strong>.</p>

<h2 id="the-manual-stack-test-is-the-truth-the-cems-is-calibrated-to">The manual stack test is the “truth” the CEMS is calibrated to</h2>

<p>The SRM is everything the CEMS isn’t: slow, manual, labour-intensive — and traceable to a physical mass on a balance. It doesn’t infer anything. It collects the dust and puts it on a scale.</p>

<p>That’s exactly why the rules keep it in the picture. The SRM is the <strong>reference</strong> — the trusted measurement that the continuous analyser’s proxy signal gets anchored to. Without it, your CEMS would be producing precise-looking numbers with nothing tying them to reality.</p>

<h2 id="qal2-ties-the-two-together--at-install">QAL2 ties the two together — at install</h2>

<p>The moment those two measurements are formally connected is the <strong>QAL2 test</strong>. A registered tester runs the SRM alongside your CEMS, pairs the readings, and derives the equation — the <em>calibration function</em> — that converts your analyser’s proxy signal into true concentration. From then on, your CEMS reports calibrated, traceable values instead of raw counts.</p>

<p>We covered that test in detail in the Operating series — <a href="/insights/qal2-calibration-variability-test-cems/">QAL2 and the Calibration &amp; Variability Test</a> — and it’s where this Reference Methods series plugs in. QAL2 is <em>built on</em> the manual stack test. Everything QAL2 proves about your CEMS is only as good as the SRM underneath it.</p>

<h2 id="they-drift-apart--which-is-why-its-never-one-and-done">They drift apart — which is why it’s never one-and-done</h2>

<p>If a CEMS stayed perfectly true to its first calibration forever, you’d run the SRM once and never again. But analysers drift. Optics foul, sources age, the flue itself changes. Over months, the proxy signal slowly stops meaning exactly what it meant on calibration day.</p>

<p>So the manual reference test comes back on a schedule. The <strong>Annual Surveillance Test (AST)</strong> re-runs the SRM against the CEMS each year to confirm the calibration still holds, while routine <strong>QAL3</strong> drift checks watch for trouble in between. (The full quality chain — QAL1 → QAL2 → QAL3 → AST — is mapped <a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">here</a>.) The reference method isn’t a one-time hurdle at install — it’s the recurring anchor that keeps your continuous data honest.</p>

<h2 id="so-why-a-continuous-monitor-still-needs-manual-stack-tests">So: why a continuous monitor still needs manual stack tests</h2>

<p>Because the CEMS gives you <em>speed and coverage</em> — a reading every moment, forever — and the manual SRM gives you <em>truth</em> — a value tied to a weighed mass. Neither replaces the other. The continuous monitor watches; the reference method tells the monitor what it’s seeing, and keeps telling it, year after year.</p>

<p>That’s the bridge. The rest of this series is about the reference method itself — the thing your whole CEMS quietly depends on:</p>

<ul>
  <li><strong>Part 2</strong> explains <strong>isokinetic sampling</strong> — why the sample has to be drawn at exactly the flue’s own velocity, in plain English.</li>
  <li><strong>Part 3</strong> maps the standards that govern it — <strong><a href="/insights/ms-1596-iso-9096-en-13284-particulate-standards/">MS 1596, ISO 9096 and EN 13284</a></strong>.</li>
  <li><strong>Part 4</strong> looks at the <strong>MS 1596 revision</strong> now under way.</li>
  <li><strong>Part 5</strong> shows you how to <strong>read a stack-test report</strong> — concentration, mass flow and isokinetic %.</li>
</ul>

<p><strong>Facing your first QAL2, or an AST that has to pass?</strong> <a href="/#contact">Talk to us</a> — we run CEMS and the reference-method stack tests behind them for facilities across Malaysia, against the same DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/qal2-calibration-variability-test-cems/">QAL2 and the Calibration &amp; Variability Test: certifying your CEMS against the SRM</a></li>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST</a></li>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility, refer to the current Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 1 of our Reference Methods series: you installed a CEMS so you wouldn't need a team climbing the stack — so why do the rules still require manual stack tests? Because a continuous monitor reads a proxy signal that has to be anchored to a true, weighed measurement. Here's how the two fit together.]]></summary></entry><entry><title type="html">Valid averages and the 75% rule: when a reading counts, and when it doesn’t</title><link href="https://www.alamsekitar.com.my/insights/cems-valid-averages-75-percent-rule/" rel="alternate" type="text/html" title="Valid averages and the 75% rule: when a reading counts, and when it doesn’t" /><published>2026-06-21T03:00:00+00:00</published><updated>2026-06-21T03:00:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/cems-valid-averages-75-percent-rule</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/cems-valid-averages-75-percent-rule/"><![CDATA[<p><em>Enforcing the Clean Air Regulations 2014 — Part 2 of 5. A series for regulators and compliance staff, drawn from the DOE CEMS Guidelines (Version 8, 2025), which we helped develop.</em></p>

<p>In <a href="/insights/cems-compliance-daily-half-hourly-rule-reg-17-3/">Part 1</a> we set out the two-part compliance test: no daily average above the ELV, and no half-hourly average above twice the ELV. But that test only means something if the averages going into it are <em>valid</em>. An exceedance, the guidelines are careful to say, is an exceedance “as indicated by <strong>valid measurement</strong>.” So before you can ask “did this average breach the limit?”, you have to ask a prior question: <strong>does this average even count?</strong></p>

<p>That question is answered from the bottom up.</p>

<h2 id="averages-are-built-not-measured">Averages are built, not measured</h2>

<p>A CEMS doesn’t record a “half-hour” directly. It records fast, then rolls the data up through three tiers — and each tier has its own validity gate:</p>

<figure class="fig flow">
<p class="fig-title">How a valid average is built · minute → half-hour → day</p>
<div class="flow-row">
<div class="flow-step"><span class="fs-name">1-minute average</span><span class="fs-q">valid data for ≥ 45 sec</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">Half-hour average</span><span class="fs-q">≥ 22 of 30 valid minutes</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">Daily average</span><span class="fs-q">from valid half-hours, over operating time</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step muted"><span class="fs-name">Compliance test</span><span class="fs-q">vs ELV / 2× ELV</span></div>
</div>
<p class="fig-note">● A tier only counts if the tier below it cleared its 75% gate</p>
<figcaption>Validity flows upward. A half-hour built on too few valid minutes is itself invalid — and never reaches the compliance test.</figcaption>
</figure>

<h2 id="tier-1--the-valid-one-minute-average">Tier 1 — the valid one-minute average</h2>

<p>The smallest building block of a half-hour is the <strong>one-minute average</strong>. Under §2.3.2 of the guidelines, a one-minute average is valid only if it contains <strong>valid data readings representing any 45 seconds</strong> of the preceding minute.</p>

<p>Forty-five seconds out of sixty is <strong>75%</strong>. If the analyser was warming up, mid-calibration, or simply not returning good data for more than a quarter of that minute, the minute doesn’t qualify — and it can’t be used as a building block above it.</p>

<h2 id="tier-2--the-valid-half-hour-and-the-22-of-30-rule">Tier 2 — the valid half-hour, and the 22-of-30 rule</h2>

<p>Half-hourly averages are the unit the law actually judges (alongside the daily figure), so this is the tier that matters most for enforcement. The sub-average period for a half-hour is the one-minute average, and under §2.3.1:</p>

<blockquote>
  <p>A valid half-hour average must contain <strong>at least 22 sub-average data within the half-hour period (75%)</strong>.</p>
</blockquote>

<p>Thirty minutes, of which at least 22 must be valid one-minute averages. Twenty-two of thirty is, again, <strong>75%</strong>. Clear the bar and the half-hour stands as a number the regulator can act on. Fall short — 21 valid minutes or fewer — and the half-hour is <strong>invalid</strong>: it isn’t a low reading, a zero, or a pass. It simply isn’t a measurement.</p>

<figure class="fig">
<svg viewBox="0 0 700 250" xmlns="http://www.w3.org/2000/svg" role="img" aria-labelledby="hh-t hh-d" font-family="'Helvetica Neue',Helvetica,Arial,sans-serif">
<title id="hh-t">What makes a half-hour valid</title>
<desc id="hh-d">Thirty cells representing the thirty one-minute averages in a half-hour, arranged in two rows of fifteen. Twenty-four are shaded as valid and six as invalid; because at least twenty-two are valid, the half-hour counts.</desc>
<text x="350" y="26" text-anchor="middle" font-size="16" font-weight="700" fill="var(--ink)">A half-hour = thirty one-minute averages</text>
<text x="350" y="46" text-anchor="middle" font-size="11" fill="var(--muted)">at least 22 must be valid (75%) for the half-hour to count</text>
<g>
<rect x="70" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="109" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="148" y="72" width="36" height="40" rx="3" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.3" />
<rect x="187" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="226" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="265" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="304" y="72" width="36" height="40" rx="3" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.3" />
<rect x="343" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="382" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="421" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="460" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="499" y="72" width="36" height="40" rx="3" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.3" />
<rect x="538" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="577" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="616" y="72" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="70" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="109" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="148" y="132" width="36" height="40" rx="3" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.3" />
<rect x="187" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="226" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="265" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="304" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="343" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="382" y="132" width="36" height="40" rx="3" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.3" />
<rect x="421" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="460" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="499" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="538" y="132" width="36" height="40" rx="3" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.3" />
<rect x="577" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
<rect x="616" y="132" width="36" height="40" rx="3" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.3" />
</g>
<g font-size="11" fill="var(--muted)">
<rect x="70" y="196" width="20" height="14" rx="2" fill="var(--green-tint)" stroke="var(--green-d)" stroke-width="1.2" />
<text x="98" y="207" text-anchor="start">valid minute</text>
<rect x="200" y="196" width="20" height="14" rx="2" fill="#F0F0F0" stroke="var(--grey)" stroke-width="1.2" />
<text x="228" y="207" text-anchor="start">invalid / missing</text>
</g>
<text x="640" y="207" text-anchor="end" font-size="13" font-weight="700" fill="var(--green-d)">24 / 30 valid → ✓ half-hour counts</text>
</svg>
<figcaption>Here 24 of 30 minutes are valid — above the 22 threshold — so the half-hour is valid. At 21 or fewer, the half-hour would be discarded as downtime, not scored as a reading.</figcaption>
</figure>

<h2 id="tier-3--the-daily-average">Tier 3 — the daily average</h2>

<p>The daily figure is <strong>derived, not measured</strong>. Under Regulation 17(4), for each calendar day the owner or occupier calculates the <strong>daily mean value relating to the daily operating time, from the half-hourly mean values</strong>. In other words, the day is the average of the valid half-hours across the hours the plant actually ran.</p>

<p>This is where validity does its quiet, decisive work. Invalid half-hours are <strong>excluded</strong> from the calculation as <em>downtime</em> — the guidelines define downtime as periods of operation yielding invalid or no data (calibration, maintenance, malfunction, audits, out-of-control periods). They are not folded in as zeros, which would artificially drag a daily average <em>down</em> and hide a genuinely high day. The daily mean is built only from the half-hours that actually count.</p>

<h2 id="a-quick-worked-example">A quick worked example</h2>

<p>Why does <em>excluding</em> invalid half-hours matter so much more than it sounds? Take a facility with a daily ELV of <strong>150 mg/m³</strong> that runs a full day — 48 half-hours. Suppose a calibration and a short fault leave <strong>10 half-hours invalid</strong>, and the <strong>38 valid half-hours average 140 mg/m³</strong>.</p>

<p>Done correctly, the daily mean is built from the valid half-hours only: <strong>140 mg/m³</strong> — a day running uncomfortably close to its limit, exactly as it should appear.</p>

<p>Now imagine those 10 invalid half-hours were wrongly counted as zeros instead of excluded. The “daily average” becomes (38 × 140 + 10 × 0) ÷ 48 ≈ <strong>111 mg/m³</strong> — a comfortable-looking day that never happened. Zero-filling doesn’t just blur the picture; it actively hides a facility operating near its ELV. That single modelling choice is the difference between catching a problem and missing it, which is why the guidelines treat invalid periods as <em>downtime to set aside</em>, not data to average in.</p>

<h2 id="why-this-matters-for-enforcement">Why this matters for enforcement</h2>

<p>Three practical consequences follow, and they’re worth holding onto when reviewing a year of data:</p>

<ul>
  <li><strong>A breach must rest on a valid average.</strong> A spike inside an <em>invalid</em> half-hour is not, by itself, a reportable exceedance — though it is a strong signal that something needs explaining.</li>
  <li><strong>Invalid data is a story, not a gap to ignore.</strong> Persistent downtime can mean a CEMS that isn’t being maintained, isn’t holding <a href="/insights/qal2-calibration-variability-test-cems/">calibration</a>, or is being run out of its valid range. Low data availability is itself a compliance concern, even when the valid readings that remain look clean.</li>
  <li><strong>The 75% gates are deliberate.</strong> They tolerate brief, normal interruptions while refusing to let a facility certify a half-hour — or a day — on too little real data.</li>
</ul>

<p>That is the foundation the rest of enforcement stands on: a clear, mechanical rule for which numbers are real. With validity settled, the next question is what an operator must <em>do</em> the moment a valid exceedance — or a CEMS failure — occurs.</p>

<p><strong>Assessing CEMS data and want to read validity the way the guidelines intend?</strong> <a href="/#contact">Talk to us</a> — we work both sides of this, helping operators and regulators interpret the same DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: why your data is valid in the first place</a></li>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For the precise legal position, refer to the Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 2 of our Enforcing the Clean Air Regulations 2014 series: how a valid average is built from the minute up — the 45-second minute, the 22-of-30 half-hour, and the daily mean — and why invalid data is excluded, not counted as zero.]]></summary></entry><entry><title type="html">QAL2 and the Calibration &amp;amp; Variability Test: certifying your CEMS after install</title><link href="https://www.alamsekitar.com.my/insights/qal2-calibration-variability-test-cems/" rel="alternate" type="text/html" title="QAL2 and the Calibration &amp;amp; Variability Test: certifying your CEMS after install" /><published>2026-06-21T02:00:00+00:00</published><updated>2026-06-21T02:00:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/qal2-calibration-variability-test-cems</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/qal2-calibration-variability-test-cems/"><![CDATA[<p><em>Operating a compliant CEMS — Part 2 of 5. A practical series for industry, drawn from the DOE CEMS Guidelines (Version 8, 2025), which we helped develop.</em></p>

<p>In <a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">Part 1</a> we mapped the four-stage quality-assurance chain. <a href="/insights/qal1-certification-mcert-tuv-doe-registered-cems/">QAL1</a> proved the instrument <em>design</em> is sound before it ever reached your stack. But a certified analyser bolted onto <em>your</em> chimney, breathing <em>your</em> flue gas, still has to prove it reads true. That proof is <strong>QAL2</strong> — and until it passes, your data officially counts for nothing.</p>

<h2 id="what-qal2-actually-certifies">What QAL2 actually certifies</h2>

<p>The <strong>QAL2 Calibration and Variability Test (QAL2-CVT)</strong> is the test that <strong>accepts and certifies your CEMS installation and operation</strong> at the plant. It does two jobs at once: it <em>calibrates</em> your analyser against a trusted reference, and it <em>checks</em> that the calibrated system is precise enough to be relied on.</p>

<p>Here’s the part operators most often underestimate: QAL2 <strong>must be completed before your CEMS data is connected to the DOE System for CEMS</strong> (the iRemote platform). Any data transmitted before that is, in the words of the guidelines, <strong>“unverified and invalid.”</strong> QAL2 is the gate between <em>installed</em> and <em>officially reporting</em>.</p>

<figure class="fig flow">
<p class="fig-title">The QAL2-CVT sequence · from functional check to valid data</p>
<div class="flow-row">
<div class="flow-step"><span class="fs-name">Functional test</span><span class="fs-q">System ready?</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">Parallel test</span><span class="fs-q">CEMS vs SRM, 15 runs / 3 days</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">Calibration function</span><span class="fs-q">Signal → true value</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">Variability test</span><span class="fs-q">Precise enough? (decider)</span></div>
</div>
<p class="fig-note">● Pass → CVT report verified by DOE → CEMS data connects as valid</p>
<figcaption>Each step gates the next. Fail the functional test and the parallel test can't start; fail variability and the calibration doesn't stand.</figcaption>
</figure>

<h2 id="first-the-functional-test">First, the functional test</h2>

<p>Before any of the real measurement happens, the system has to clear a <strong>functional test</strong> — a series of checks (alignment, zero and span, leak, interferences, drift) confirming the CEMS is fit to be tested. It must be carried out <strong>no more than one month</strong> before the parallel measurements begin, and <strong>validated before the test proceeds</strong>. If it fails and no corrective action is taken, the QAL2 simply <strong>cannot go ahead</strong>. It’s the gate we flagged in Part 1 — the thing that stops you wasting a test campaign on a system that isn’t ready.</p>

<h2 id="the-parallel-measurement-cems-against-the-srm">The parallel measurement: CEMS against the SRM</h2>

<p>This is the heart of QAL2. A <strong>DOE-registered, independent CEMS tester</strong> runs the <strong>Standard Reference Method (SRM)</strong> — the trusted manual measurement method (<a href="/insights/why-cems-needs-manual-stack-tests-srm/">what the SRM actually is, and why your CEMS depends on it</a>) — <em>alongside</em> your CEMS, sampling the same flue gas at the same time. Pair after pair, the SRM gives the “true” value to compare your analyser against.</p>

<p>The guidelines are specific about how this is done:</p>

<ul>
  <li><strong>At least 15 valid parallel measurements</strong>, spread uniformly over <strong>three days</strong> (not necessarily consecutive, but within four weeks), with the plant operating normally.</li>
  <li><strong>Each sample at least 30 minutes</strong>, and the start of each at least <strong>one hour apart</strong>.</li>
  <li><strong>At least one measurement at or near zero</strong> (defined as ≤ 5% of the ELV).</li>
  <li>Testers are advised to collect <strong>18–19 sets</strong> so enough valid pairs remain after any outliers are removed.</li>
</ul>

<p>One rule matters more than it looks: <strong>reference gases alone are not permitted</strong> to build the calibration. The test has to use the real stack-gas matrix — only the SRM, on your actual emissions, captures the moisture, temperature and interferences your analyser really sees. The tester also picks times when emissions are likely to be <strong>highest and most varied</strong> (without artificially forcing them), so the calibration covers your genuine operating range.</p>

<h2 id="the-calibration-function">The calibration function</h2>

<p>From those paired readings, the tester derives the <strong>calibration function</strong> — the equation that converts your analyser’s raw signal into a <strong>true, traceable concentration</strong>. From this point on, your CEMS no longer reports raw counts; it reports calibrated, defensible values.</p>

<figure class="fig">
<svg viewBox="0 0 680 380" xmlns="http://www.w3.org/2000/svg" role="img" aria-labelledby="cf-t cf-d" font-family="'Helvetica Neue',Helvetica,Arial,sans-serif">
<title id="cf-t">The calibration function</title>
<desc id="cf-d">A scatter plot of paired CEMS-versus-SRM measurements rising from near zero to high concentration, with a straight calibration line fitted through them. The daily ELV and the top of the valid calibration range are marked as horizontal reference lines.</desc>
<rect x="80" y="92" width="560" height="208" fill="var(--green-tint)" />
<line x1="80" y1="92" x2="640" y2="92" stroke="var(--grey)" stroke-width="1.5" stroke-dasharray="6 4" />
<line x1="80" y1="120" x2="640" y2="120" stroke="var(--green-d)" stroke-width="1.5" stroke-dasharray="6 4" />
<line x1="80" y1="60" x2="80" y2="300" stroke="var(--grey)" stroke-width="1" />
<line x1="80" y1="300" x2="640" y2="300" stroke="var(--grey)" stroke-width="1" />
<text x="74" y="304" text-anchor="end" font-size="10.5" fill="var(--muted)">0</text>
<text x="74" y="124" text-anchor="end" font-size="10.5" fill="var(--muted)">150</text>
<text x="74" y="64" text-anchor="end" font-size="10.5" fill="var(--muted)">200</text>
<text x="636" y="88" text-anchor="end" font-size="10.5" fill="var(--grey)">Top of valid calibration range (VCR)</text>
<text x="636" y="115" text-anchor="end" font-size="10.5" fill="var(--green-d)">Daily ELV = 150</text>
<text x="360" y="334" text-anchor="middle" font-size="11" fill="var(--muted)">CEMS analyser signal (raw)</text>
<text x="26" y="180" text-anchor="middle" font-size="11" fill="var(--muted)" transform="rotate(-90 26 180)">SRM reference (mg/m³)</text>
<line x1="80" y1="290" x2="640" y2="90" stroke="var(--green-d)" stroke-width="2.5" />
<g fill="var(--green)" stroke="#fff" stroke-width="1">
<circle cx="95" cy="286" r="4" /><circle cx="120" cy="279" r="4" /><circle cx="160" cy="256" r="4" /><circle cx="200" cy="250" r="4" /><circle cx="240" cy="236" r="4" /><circle cx="280" cy="213" r="4" /><circle cx="320" cy="209" r="4" /><circle cx="360" cy="186" r="4" /><circle cx="400" cy="179" r="4" /><circle cx="440" cy="158" r="4" /><circle cx="480" cy="150" r="4" /><circle cx="520" cy="136" r="4" /><circle cx="560" cy="114" r="4" /><circle cx="600" cy="108" r="4" /><circle cx="640" cy="93" r="4" />
</g>
<text x="150" y="320" text-anchor="start" font-size="10.5" fill="var(--green-d)">↑ a near-zero pair is required</text>
<rect x="404" y="214" width="150" height="46" rx="4" fill="#fff" stroke="var(--grey)" stroke-width="1" />
<text x="414" y="232" text-anchor="start" font-size="11" font-weight="600" fill="var(--ink)">R² ≥ 0.9</text>
<text x="414" y="250" text-anchor="start" font-size="10" fill="var(--muted)">good fit (guidance)</text>
<text x="340" y="28" text-anchor="middle" font-size="16" font-weight="700" fill="var(--ink)">Each point = one parallel CEMS–SRM measurement</text>
</svg>
<figcaption>The line is the calibration function: it translates analyser signal into true concentration. A correlation of R² ≥ 0.9 indicates a good fit — but at low, clustered emissions a lower R² isn't automatically a failure.</figcaption>
</figure>

<p>A correlation of <strong>R² ≥ 0.9</strong> is the guideline’s indicator of a good fit. But where emissions are low or tightly clustered, a lower R² can be perfectly legitimate — which is exactly why R² is <em>guidance</em>, and the <strong>variability test has the final word</strong>.</p>

<h2 id="the-valid-calibration-range">The valid calibration range</h2>

<p>A calibration is only trustworthy across the span of concentrations it was actually built on — the <strong>valid calibration range (VCR)</strong>. The guidelines set its top at the <strong>highest calibrated parallel reading plus a margin</strong> (10% for gas, or 100% for particulate, of the ELV — or 20% of the ELV, whichever is greater).</p>

<p>Operate inside the VCR and your data stands on solid ground. The operator must <strong>check weekly</strong> that readings stay within it; readings that persistently sit <em>outside</em> the VCR (for example, more than 5% of values over five consecutive weeks) can trigger a <strong>fresh QAL2</strong> — though if an exceedance was caused by a plant failure, fixing the plant is enough and a full recalibration isn’t needed.</p>

<h2 id="the-variability-test--the-decider">The variability test — the decider</h2>

<p>Calibration tells you the CEMS reads the right <em>value</em>. The <strong>variability test</strong> asks whether it reads <em>consistently enough</em>. It compares the scatter of CEMS-versus-SRM differences against an allowed uncertainty (the 95% confidence interval in the regulation), using <strong>stack measurements only</strong> — never reference materials.</p>

<p>This is the <strong>definitive test</strong>. A CEMS can have a tidy-looking calibration line and still fail variability; the test, not the eye, decides. Worth knowing too: sloppy SRM work can make a perfectly good CEMS <em>fail</em> — another reason the competence of your independent tester is not a place to economise.</p>

<h2 id="passing--and-going-live">Passing — and going live</h2>

<p>Once the system passes, the tester compiles the <strong>Calibration and Variability Test report</strong> (to the Appendix 2 format) and submits it to <strong>DOE for verification</strong>. Only after that verification can your CEMS data connect to the DOE System for CEMS as <strong>valid, compliant data</strong>.</p>

<p>And then the job shifts from <em>proving it once</em> to <em>keeping it true every day</em> — which is <strong>QAL3</strong>, the subject of the next part.</p>

<p><strong>Facing a QAL2 and want it to pass first time?</strong> <a href="/#contact">Talk to us</a> — we prepare and run CEMS for facilities across Malaysia against the same DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/qal1-certification-mcert-tuv-doe-registered-cems/">QAL1 and certification: what "DOE-registered" and MCERT/TÜV mean</a></li>
    <li><a href="/insights/cems-compliance-daily-half-hourly-rule-reg-17-3/">What "compliant" actually means: the daily-average and 2× half-hourly rule</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility, refer to the current Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 2 of our Operating a Compliant CEMS series: how the QAL2 Calibration & Variability Test certifies your CEMS against the Standard Reference Method — the parallel measurements, the calibration function, the valid calibration range, and the variability test that has the final say.]]></summary></entry><entry><title type="html">QAL1 and certification: what ‘DOE-registered CEMS’ and MCERT/TÜV actually mean</title><link href="https://www.alamsekitar.com.my/insights/qal1-certification-mcert-tuv-doe-registered-cems/" rel="alternate" type="text/html" title="QAL1 and certification: what ‘DOE-registered CEMS’ and MCERT/TÜV actually mean" /><published>2026-06-19T02:20:00+00:00</published><updated>2026-06-19T02:20:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/qal1-certification-mcert-tuv-doe-registered-cems</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/qal1-certification-mcert-tuv-doe-registered-cems/"><![CDATA[<p><em>Buying a CEMS — Part 2 of 5. A practical series for industry, drawn from the DOE CEMS Guidelines (Version 8, 2025), which we helped develop.</em></p>

<p>In <a href="/insights/need-a-cems-clean-air-regulations-2014/">Part 1</a> we covered whether your facility needs a CEMS and the steps to take before installing one. Now to the single most important quality marker when you actually choose equipment: <strong>certification</strong>. Get this wrong and everything downstream — your QAL2 test, your compliance data, your inspection record — is built on sand.</p>

<h2 id="what-qal1-is-and-isnt">What QAL1 is (and isn’t)</h2>

<p>Malaysia’s CEMS quality framework follows the international <strong>EN 14181</strong> standard, which defines a chain of “Quality Assurance Levels”: <strong>QAL1, QAL2, QAL3</strong>, plus the <strong>Annual Surveillance Test (AST)</strong>. They sound similar but do very different jobs.</p>

<p><strong>QAL1 is the one that happens before the system ever reaches your stack.</strong> It certifies that the <em>instrument design</em> — the make and model — has been independently type-tested in the laboratory and the field, and meets the required performance standards. Think of it as the analyser’s “type approval”: proof the technology itself is fit for purpose.</p>

<p>It does <strong>not</strong> prove the system works on <em>your</em> stack — that’s QAL2, which we cover in the <a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">Operating series</a>. QAL1 is about the equipment; QAL2 is about your installation.</p>

<h2 id="mcert-and-tüv--the-certification-schemes">MCERT and TÜV — the certification schemes</h2>

<p>QAL1 certificates are issued under recognised international schemes — most commonly the UK’s <strong>MCERTS</strong> or Germany’s <strong>TÜV</strong>. DOE requires that any CEMS installed in Malaysia is <strong>MCERT- or TÜV QAL1-certified before installation.</strong></p>

<p>So your first question to any supplier is simple: <em>show me the QAL1 certificate.</em> If a product can’t produce a current MCERTS or TÜV QAL1 certificate for the exact model being offered, it should not be going on your stack.</p>

<h2 id="the-certified-range-must-match-your-elv">The certified range must match your ELV</h2>

<p>Here’s a subtlety that trips up buyers. A QAL1 certificate doesn’t just say “this analyser is good” — it certifies the instrument over a <strong>specific measuring range</strong>, and that <strong>certification range is always related to the daily ELV.</strong></p>

<p>In practice: if your activity’s daily Emission Limit Value for a pollutant is, say, 150 mg/m³, the instrument’s certified range has to be appropriate for measuring around that limit. A system certified for a very different range — even a genuine, MCERT-certified one — may be the wrong tool for your facility. Match the certified range to <em>your</em> ELV, not just to a brand name.</p>

<h2 id="certified-and-registered-are-two-different-things">“Certified” and “registered” are two different things</h2>

<p>This is where people conflate two requirements:</p>

<ul>
  <li><strong>Certified</strong> means the model holds a valid MCERTS/TÜV QAL1 certificate (a manufacturer responsibility).</li>
  <li><strong>DOE-registered</strong> means the specific equipment is registered through the <strong>DOE System for CEMS</strong>, and is supplied and installed by a <strong>DOE-registered CEMS consultant</strong>.</li>
</ul>

<p>You need <strong>both</strong>. A certified system that isn’t registered through DOE, or that’s supplied by an unregistered party, doesn’t satisfy the requirement. Conversely, registration is only granted to genuinely certified equipment from registered consultants — the two reinforce each other.</p>

<h2 id="certified-is-necessary-not-sufficient">Certified is necessary, not sufficient</h2>

<p>Even the right certificate isn’t the whole story. The DOE-registered consultant is responsible for ensuring the <strong>supplied design matches your plant process, flue-gas characteristics, the pollutants you must monitor and your ELV</strong> — exactly as per the QAL1 certificate. “MCERT-certified” tells you the model is sound; it doesn’t tell you it’s the <em>right</em> model for your stack, gas composition and operating conditions. That matching judgement is precisely what a competent consultant is for.</p>

<h2 id="a-buyers-certification-checklist">A buyer’s certification checklist</h2>

<p>Before you sign, you should be able to tick all of these:</p>

<ul>
  <li>✅ A current <strong>MCERTS or TÜV QAL1 certificate</strong> for the exact model offered.</li>
  <li>✅ The <strong>certified range suits your daily ELV</strong> and pollutants.</li>
  <li>✅ The equipment is <strong>registered through the DOE System for CEMS</strong>.</li>
  <li>✅ It’s supplied/installed by a <strong>DOE-registered CEMS consultant</strong>.</li>
  <li>✅ The consultant has confirmed the design <strong>fits your process and flue-gas conditions</strong>.</li>
</ul>

<p>Miss any one of these and you risk a system that can’t be registered, can’t pass QAL2, or simply isn’t suited to your stack — an expensive lesson to learn after commissioning.</p>

<p><strong>Want a second pair of eyes on a quotation or certificate?</strong> <a href="/#contact">Talk to us</a> — we check exactly these points every day, using the same DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST</a></li>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility, refer to the current Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 2 of our Buying a CEMS series: how QAL1 type-certification (MCERT/TÜV) works, why the certified range must match your daily ELV, and the difference between a certified system and a DOE-registered one.]]></summary></entry><entry><title type="html">The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST, and why each exists</title><link href="https://www.alamsekitar.com.my/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/" rel="alternate" type="text/html" title="The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST, and why each exists" /><published>2026-06-19T02:10:00+00:00</published><updated>2026-06-19T02:10:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/"><![CDATA[<p><em>Operating a compliant CEMS — Part 1 of 5. A practical series for industry, drawn from the DOE CEMS Guidelines (Version 8, 2025), which we helped develop.</em></p>

<p>Buying a certified CEMS is the easy part. Keeping it producing data the regulator will accept — every hour, all year — is a continuous <strong>quality-assurance programme</strong>. Under the international <strong>EN 14181</strong> standard that Malaysia’s guidelines follow, that programme has four stages. Each answers a different question, and each has a clearly assigned owner. Skip one and the whole chain of trust in your data breaks.</p>

<p>Here’s the chain, in plain terms.</p>

<figure class="fig flow">
<p class="fig-title">The CEMS quality-assurance chain · EN 14181</p>
<div class="flow-row">
<div class="flow-step"><span class="fs-name">QAL1</span><span class="fs-q">Right design?</span><span class="fs-own">Owner: Manufacturer</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">QAL2</span><span class="fs-q">Right on your stack?</span><span class="fs-own">Owner: Independent tester</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step"><span class="fs-name">QAL3</span><span class="fs-q">Staying right daily?</span><span class="fs-own">Owner: Plant operator</span></div>
<div class="flow-arrow" aria-hidden="true">→</div>
<div class="flow-step muted"><span class="fs-name">AST</span><span class="fs-q">Valid this year?</span><span class="fs-own">Owner: Independent tester</span></div>
</div>
<p class="fig-note">● Functional test must pass before QAL2 and AST</p>
<figcaption>Each stage assumes the one before it held — skip one and the chain of trust in your data breaks.</figcaption>
</figure>

<h2 id="qal1--does-the-instrument-design-work">QAL1 — <em>Does the instrument design work?</em></h2>

<p>This is the type-certification you sorted out at purchase: the make and model is independently tested and holds an <strong>MCERTS or TÜV QAL1 certificate</strong>. It proves the technology is fit for purpose before it ever reaches your stack.</p>

<p><strong>Owner:</strong> the CEMS manufacturer (who achieves and maintains the certification). <em>(We covered QAL1 in detail in the <a href="/insights/qal1-certification-mcert-tuv-doe-registered-cems/">Buying a CEMS series</a>.)</em></p>

<h2 id="qal2--is-it-right-on-your-stack">QAL2 — <em>Is it right on YOUR stack?</em></h2>

<p>A certified instrument still has to be proven on <em>your</em> chimney, with <em>your</em> flue gas. That’s the <strong>Calibration and Variability Test (CVT)</strong>, done after installation. A <strong>DOE-registered CEMS tester</strong> runs <strong>Standard Reference Method (SRM)</strong> measurements (<a href="/insights/why-cems-needs-manual-stack-tests-srm/">the manual stack test behind the calibration</a>) in parallel with your CEMS, establishes the <strong>calibration function</strong> that relates your analyser’s signal to true concentration, and confirms the system’s <strong>variability</strong> is within allowed limits.</p>

<p>Two things matter here: a <strong>functional test</strong> must pass first (more below), and the tester must be <strong>independent</strong> — they cannot test a system their own company installed. That independence is what makes your calibration credible.</p>

<p><strong>Owner:</strong> an independent DOE-registered CEMS tester.</p>

<h2 id="qal3--is-it-staying-right-day-to-day">QAL3 — <em>Is it staying right, day to day?</em></h2>

<p>QAL2 proves the system on the day. QAL3 — <strong>On-Going Performance Monitoring (OGPM)</strong> — keeps it honest <em>between</em> formal tests. It’s the routine discipline of <strong>zero and span drift checks</strong> plotted on <strong>control charts</strong>, so you catch drift early and act before it becomes an exceedance or a failed audit. These checks are done at the maintenance intervals set in the <strong>MCERTS/TÜV certificate</strong> (and never longer than that interval).</p>

<p><strong>Owner:</strong> the plant operator — who may use competent personnel (your maintenance team, the consultant, or a tester) to perform the drift checks, plotting and corrective action.</p>

<h2 id="ast--is-the-qal2-calibration-still-valid-this-year">AST — <em>Is the QAL2 calibration still valid this year?</em></h2>

<p>Calibrations don’t last forever. The <strong>Annual Surveillance Test</strong> checks, once a year, whether the calibration function established at QAL2 is still valid. It uses the <strong>same functional checks as QAL2</strong> and is, again, run by an independent registered tester.</p>

<p><strong>Owner:</strong> an independent DOE-registered CEMS tester (appointed by the operator).</p>

<h2 id="the-functional-test--the-gate-before-every-formal-test">The functional test — the gate before every formal test</h2>

<p>Before <em>every</em> QAL2 and AST, a <strong>functional test</strong> — a series of checks on the CEMS — must be carried out. If it fails and no corrective action is taken, the QAL2 or AST <strong>cannot proceed</strong>. It’s the gate that stops you wasting a test day on a system that isn’t ready.</p>

<h2 id="why-the-chain-matters">Why the chain matters</h2>

<p>Put together, the logic is clean:</p>

<blockquote>
  <p><strong>QAL1</strong> (right design) → <strong>QAL2</strong> (right on your stack) → <strong>QAL3</strong> (stays right daily) → <strong>AST</strong> (re-confirmed yearly).</p>
</blockquote>

<p>Each stage assumes the one before it held. A facility that nails QAL2 but neglects QAL3 drift checks can drift out of compliance unnoticed; one that skips the AST can be running on a calibration that’s no longer valid. The regulator trusts your data because — and only because — the whole chain is intact.</p>

<p>One more thing to plan for: certain <strong>modifications, upgrades or repairs</strong> reset the clock and require a fresh QAL2. We’ll cover exactly which ones later in this series.</p>

<p><strong>Not sure your QA programme covers all four stages?</strong> <a href="/#contact">Talk to us</a> — we run this chain for facilities across Malaysia, using the DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/qal1-certification-mcert-tuv-doe-registered-cems/">QAL1 and certification: what "DOE-registered CEMS" and MCERT/TÜV mean</a></li>
    <li><a href="/insights/need-a-cems-clean-air-regulations-2014/">Do you even need a CEMS? What the law requires before you buy</a></li>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility, refer to the current Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 1 of our Operating a Compliant CEMS series: the four-stage EN 14181 quality-assurance programme explained — what each stage proves, and who is responsible for it.]]></summary></entry><entry><title type="html">What ‘compliant’ actually means: the daily-average and 2× half-hourly rule</title><link href="https://www.alamsekitar.com.my/insights/cems-compliance-daily-half-hourly-rule-reg-17-3/" rel="alternate" type="text/html" title="What ‘compliant’ actually means: the daily-average and 2× half-hourly rule" /><published>2026-06-19T02:00:00+00:00</published><updated>2026-06-19T02:00:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/cems-compliance-daily-half-hourly-rule-reg-17-3</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/cems-compliance-daily-half-hourly-rule-reg-17-3/"><![CDATA[<p><em>Enforcing the Clean Air Regulations 2014 — Part 1 of 5. A series for regulators and compliance staff, drawn from the DOE CEMS Guidelines (Version 8, 2025), which we helped develop.</em></p>

<p>“Is this facility compliant?” sounds like a yes/no question, but the answer rests on a precise test that’s easy to half-remember and get wrong. Under the <strong>Environmental Quality (Clean Air) Regulations 2014 (CAR 2014)</strong>, continuous-monitoring compliance is a <strong>two-part</strong> rule — and <em>both</em> parts must hold.</p>

<h2 id="the-rule-regulation-173">The rule: Regulation 17(3)</h2>

<p>For continuous emission monitoring, the Emission Limit Values (ELVs) are complied with if, over the operating period <strong>within any one calendar year</strong>:</p>

<ol>
  <li><strong>no daily average exceeds the ELV</strong>, <em>and</em></li>
  <li><strong>no half-hourly average exceeds two (2) times the ELV.</strong></li>
</ol>

<p>Two thresholds, two averaging periods, one verdict. Pass both and the facility is compliant for that period; breach either — even once — and it is not.</p>

<h2 id="a-worked-example">A worked example</h2>

<p>Say a facility’s <strong>daily ELV for total particulate matter is 150 mg/m³.</strong> Then:</p>

<ul>
  <li>The <strong>daily limit</strong> is <strong>150 mg/m³</strong> — every daily average must stay at or below it.</li>
  <li>The <strong>half-hourly limit</strong> is <strong>2 × 150 = 300 mg/m³</strong> — no half-hour average may exceed it.</li>
</ul>

<p>So:</p>

<ul>
  <li>A half-hour averaging <strong>280 mg/m³</strong> is <em>within</em> the half-hourly limit (≤ 300). On its own, not an exceedance.</li>
  <li>A day averaging <strong>160 mg/m³</strong> is an <strong>exceedance</strong> of the daily ELV — non-compliant, even though no single half-hour may have looked dramatic.</li>
  <li>A half-hour spiking to <strong>320 mg/m³</strong> breaches the 2× half-hourly limit — an exceedance, regardless of where the daily average lands.</li>
</ul>

<figure class="fig">
<svg viewBox="0 0 680 360" xmlns="http://www.w3.org/2000/svg" role="img" aria-labelledby="r17-t r17-d" font-family="'Helvetica Neue',Helvetica,Arial,sans-serif">
<title id="r17-t">Regulation 17(3): the two-part compliance test</title>
<desc id="r17-d">A chart of half-hourly averages across one day. The daily ELV of 150 and the half-hourly ceiling of twice the ELV (300) are shown as limit lines. A normal half-hour at 280 stays below the ceiling, while a spike to 320 breaches it.</desc>
<rect x="72" y="196" width="576" height="104" fill="var(--green-tint)" />
<rect x="72" y="58" width="576" height="35" fill="#FBE9E7" />
<line x1="72" y1="93" x2="648" y2="93" stroke="var(--grey)" stroke-width="1.5" stroke-dasharray="6 4" />
<line x1="72" y1="196" x2="648" y2="196" stroke="var(--green-d)" stroke-width="1.5" stroke-dasharray="6 4" />
<line x1="72" y1="58" x2="72" y2="300" stroke="var(--grey)" stroke-width="1" />
<line x1="72" y1="300" x2="648" y2="300" stroke="var(--grey)" stroke-width="1" />
<text x="66" y="97" text-anchor="end" font-size="10.5" fill="var(--muted)">300</text>
<text x="66" y="200" text-anchor="end" font-size="10.5" fill="var(--muted)">150</text>
<text x="66" y="304" text-anchor="end" font-size="10.5" fill="var(--muted)">0</text>
<text x="360" y="332" text-anchor="middle" font-size="11" fill="var(--muted)">Half-hourly averages across one operating day</text>
<text x="28" y="182" text-anchor="middle" font-size="11" fill="var(--muted)" transform="rotate(-90 28 182)">mg/m³</text>
<text x="644" y="88" text-anchor="end" font-size="10.5" fill="var(--grey)">Half-hourly ceiling = 300 (2× ELV)</text>
<text x="644" y="191" text-anchor="end" font-size="10.5" fill="var(--green-d)">Daily ELV = 150</text>
<text x="80" y="78" text-anchor="start" font-size="10.5" fill="#C0392B">Above 2× ELV — exceedance</text>
<text x="80" y="290" text-anchor="start" font-size="10.5" fill="var(--green-d)">At/below ELV — daily-average compliant zone</text>
<polyline points="100,155 147,134 194,144 241,120 288,106 335,127 382,138 429,117 476,124 523,79 570,134 617,141" fill="none" stroke="var(--green-d)" stroke-width="2.5" stroke-linejoin="round" />
<circle cx="100" cy="155" r="2.4" fill="var(--green-d)" /><circle cx="147" cy="134" r="2.4" fill="var(--green-d)" /><circle cx="194" cy="144" r="2.4" fill="var(--green-d)" /><circle cx="241" cy="120" r="2.4" fill="var(--green-d)" /><circle cx="335" cy="127" r="2.4" fill="var(--green-d)" /><circle cx="382" cy="138" r="2.4" fill="var(--green-d)" /><circle cx="429" cy="117" r="2.4" fill="var(--green-d)" /><circle cx="476" cy="124" r="2.4" fill="var(--green-d)" /><circle cx="570" cy="134" r="2.4" fill="var(--green-d)" /><circle cx="617" cy="141" r="2.4" fill="var(--green-d)" />
<circle cx="288" cy="106" r="4.5" fill="var(--green)" stroke="#fff" stroke-width="1.5" />
<text x="288" y="124" text-anchor="middle" font-size="11" font-weight="600" fill="var(--green-d)">280 ✓</text>
<circle cx="523" cy="79" r="4.5" fill="#C0392B" stroke="#fff" stroke-width="1.5" />
<text x="523" y="70" text-anchor="middle" font-size="11" font-weight="600" fill="#C0392B">320 ✗ breach</text>
<text x="340" y="28" text-anchor="middle" font-size="16" font-weight="700" fill="var(--ink)">Regulation 17(3): two thresholds, one verdict</text>
</svg>
<figcaption>Half-hourly averages may sit between the ELV and the 2× ceiling — but a day averaging 160 mg/m³ still fails the 150 daily ELV. Both parts must hold.</figcaption>
</figure>

<h2 id="why-two-thresholds">Why two thresholds?</h2>

<p>The structure is deliberate. The <strong>daily average</strong> governs <em>sustained</em> performance — it stops a facility running persistently high. The <strong>2× half-hourly</strong> ceiling caps <em>short-term</em> behaviour — it tolerates brief, normal process variation but draws a hard line on spikes. Together they prevent both “always a bit over” and “occasionally way over.”</p>

<h2 id="how-the-daily-average-is-built--reg-174">How the daily average is built — Reg 17(4)</h2>

<p>The daily figure isn’t measured directly; it’s <strong>derived</strong>. Under Reg 17(4), for each calendar day the owner or occupier calculates the <strong>daily mean value (relating to the daily operating time) from the half-hourly mean values.</strong> In other words, half-hourly averages are the building blocks, and the daily average is computed from them.</p>

<p>That’s why data quality at the half-hourly level matters so much for enforcement — if the underlying half-hours aren’t <em>valid</em>, the daily figure built on them can’t be relied on. (We cover exactly when a reading counts as valid in <a href="/insights/cems-valid-averages-75-percent-rule/">Part 2</a> of this series.)</p>

<h2 id="what-counts-as-an-excess-emission">What counts as an “excess emission”</h2>

<p>An <strong>excess emission</strong> is an <strong>exceedance of the applicable ELV as shown by a valid measurement</strong>, reported in the correct units and averaging period. The emphasis on <em>valid</em> is the point: enforcement stands on data that has passed the validity rules — not on raw, unqualified numbers. An exceedance also triggers specific notification duties (the 24-hour rule), which we’ll cover in Part 3.</p>

<h2 id="the-yardstick-for-regulators">The yardstick, for regulators</h2>

<p>Assessing a year’s data comes down to two passes:</p>

<ul>
  <li>Check <strong>every daily average</strong> against the <strong>ELV</strong>; and</li>
  <li>Check <strong>every half-hourly average</strong> against <strong>2× the ELV</strong>.</li>
</ul>

<p>A single valid exceedance of either threshold is non-compliance for that period — and the basis for the reporting and enforcement steps that follow.</p>

<p><strong>Operate a regulated facility and want to understand how your data will be assessed?</strong> <a href="/#contact">Talk to us</a> — we help operators read their numbers the way the regulator does, using the DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: why your data is valid in the first place</a></li>
    <li><a href="/insights/need-a-cems-clean-air-regulations-2014/">Do you even need a CEMS? What the law requires before you buy</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For the precise legal position, refer to the Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 1 of our Enforcing the Clean Air Regulations 2014 series: the precise two-part compliance test in Reg 17(3) — no daily average above the ELV, and no half-hourly average above twice the ELV — with a worked example.]]></summary></entry><entry><title type="html">Do you even need a CEMS? What the Clean Air Regulations 2014 require before you buy</title><link href="https://www.alamsekitar.com.my/insights/need-a-cems-clean-air-regulations-2014/" rel="alternate" type="text/html" title="Do you even need a CEMS? What the Clean Air Regulations 2014 require before you buy" /><published>2026-06-19T00:00:00+00:00</published><updated>2026-06-19T00:00:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/need-a-cems-clean-air-regulations-2014</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/need-a-cems-clean-air-regulations-2014/"><![CDATA[<p><em>Buying a CEMS — Part 1 of 5. A practical series for industry, drawn from the DOE CEMS Guidelines (Version 8, 2025), which we helped develop.</em></p>

<p>A Continuous Emission Monitoring System is a significant investment, and the worst time to discover you’ve bought the wrong one — or skipped a required step — is <em>after</em> it’s bolted to your stack. Before you compare quotes, it’s worth being clear on two things: <strong>whether the law actually requires a CEMS at your facility</strong>, and <strong>what the Department of Environment (DOE) expects you to do before installation</strong>.</p>

<h2 id="are-you-required-to-have-one">Are you required to have one?</h2>

<p>Under the <strong>Environmental Quality (Clean Air) Regulations 2014 (CAR 2014)</strong> — made under the <strong>Environmental Quality Act 1974 (EQA 1974)</strong> — certain stationary emission sources must continuously monitor their emissions. A CEMS isn’t optional decoration; it’s the mechanism that produces a continuous, defensible record proving your stack stays within its limits.</p>

<p>You may be required to install a CEMS if any of these apply:</p>

<ul>
  <li>Your activity or facility falls under <strong>CAR 2014</strong> as a regulated stationary source;</li>
  <li>It’s a <strong>condition of your EIA report approval</strong>;</li>
  <li>You operate a <strong>licensed prescribed premises</strong>;</li>
  <li>You’ve been identified as a <strong>problematic facility</strong>; or</li>
  <li>You’ve received a <strong>written directive from DOE</strong> under its EQA 1974 jurisdiction.</li>
</ul>

<p>If you’re unsure which bucket you fall into, that uncertainty is itself a reason to get advice early — the answer shapes everything that follows.</p>

<h2 id="your-activity-sets-your-limits">Your activity sets your limits</h2>

<p>A common misconception is that there’s a single emission standard for everyone. There isn’t. The <strong>2nd and 3rd Schedules of CAR 2014</strong> specify, by activity type, <em>which</em> pollutants you must monitor (for example total particulate matter, SO₂, NOₓ, CO), the applicable <strong>Emission Limit Values (ELVs)</strong>, and the <strong>diluent reference gas</strong> (O₂ or CO₂) your readings are corrected to.</p>

<p>This matters before you buy because your activity’s pollutant list and ELV directly determine what analysers and what measuring range your CEMS needs. A system that’s perfect for one industry can be the wrong specification for another. Pin down your pollutants, ELVs and reference gas <em>first</em> — they are the design brief for everything else.</p>

<h2 id="the-order-of-operations-the-law-expects">The order of operations the law expects</h2>

<p>Here’s the sequence DOE’s guidelines set out — and the steps people most often get wrong by doing them out of order:</p>

<ol>
  <li><strong>Register as a CEMS Industry</strong> with DOE, and <strong>apply for CEMS installation through the DOE System for CEMS — before any site installation.</strong> Installing first and asking later is the wrong way round.</li>
  <li><strong>Buy a registered, certified system.</strong> The CEMS must be <strong>MCERT or TÜV QAL1-certified</strong> (more on what QAL1 means in <a href="/insights/qal1-certification-mcert-tuv-doe-registered-cems/">Part 2</a>), and it must be <strong>supplied and installed by a DOE-registered CEMS consultant</strong> — one listed on the DOE website and DOE System for CEMS.</li>
  <li><strong>Match the system to your stack.</strong> The consultant is responsible for ensuring the supplied design matches your plant process, flue-gas characteristics, the pollutants you must monitor and your ELV — not just selling a box.</li>
  <li><strong>Have it verified by an independent tester.</strong> After installation, a <strong>DOE-registered CEMS tester</strong> conducts the performance audit. Crucially, the tester must be <em>independent of whoever installed it</em> — they cannot test their own company’s installation.</li>
</ol>

<h2 id="whos-who-in-a-cems-project">Who’s who in a CEMS project</h2>

<p>It helps to know the four parties you’ll deal with, because their roles are defined and separate:</p>

<ul>
  <li><strong>CEMS manufacturer</strong> — makes the equipment and holds its QAL1 certification.</li>
  <li><strong>CEMS consultant</strong> — the DOE-registered company that supplies, installs, commissions and maintains the system, and advises you on compliance. (This is our role.)</li>
  <li><strong>CEMS tester</strong> — a <em>separate</em>, DOE-registered party that independently verifies and certifies performance.</li>
  <li><strong>Plant operator</strong> — you: responsible for applying to DOE, running the quality-assurance programme, monitoring compliance and reporting.</li>
</ul>

<p>That separation between installer and tester is deliberate: it’s what makes your compliance data credible to the regulator.</p>

<h2 id="the-takeaway">The takeaway</h2>

<p>Before you shortlist a single product, you should be able to answer: <em>Am I required to monitor? Which pollutants and ELVs apply to my activity? Have I registered and applied to DOE? Am I buying a QAL1-certified system through a registered consultant?</em> Getting those four right at the start is what keeps a CEMS purchase from becoming a costly do-over.</p>

<p><strong>Not sure where your facility stands?</strong> <a href="/#contact">Talk to us</a> — we’ll help you map your obligations before you commit, drawing on the DOE CEMS Guidelines we helped write.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST</a></li>
    <li><a href="/insights/clean-air-regulations-2014-cems/">What the Clean Air Regulations 2014 mean for your CEMS</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility, refer to the current Environmental Quality (Clean Air) Regulations 2014, the EQA 1974, and the DOE CEMS Guidelines, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[Part 1 of our Buying a CEMS series: who is actually required to install a Continuous Emission Monitoring System under Malaysia's Clean Air Regulations 2014, and the steps the law expects before you spend a ringgit.]]></summary></entry><entry><title type="html">What the Clean Air Regulations 2014 mean for your CEMS</title><link href="https://www.alamsekitar.com.my/insights/clean-air-regulations-2014-cems/" rel="alternate" type="text/html" title="What the Clean Air Regulations 2014 mean for your CEMS" /><published>2026-06-18T00:00:00+00:00</published><updated>2026-06-18T00:00:00+00:00</updated><id>https://www.alamsekitar.com.my/insights/clean-air-regulations-2014-cems</id><content type="html" xml:base="https://www.alamsekitar.com.my/insights/clean-air-regulations-2014-cems/"><![CDATA[<p>If your facility operates a regulated stationary emission source in Malaysia, the <strong>Environmental Quality (Clean Air) Regulations 2014</strong> — made under the Environmental Quality Act 1974 — are the rules that ultimately decide whether your operation stays running. For many industrial operators, the practical expression of those rules is a <strong>Continuous Emission Monitoring System (CEMS)</strong>.</p>

<p>Here’s what that means in practice, without the jargon.</p>

<h2 id="why-cems-exists">Why CEMS exists</h2>

<p>The regulations set emission limits for pollutants from stationary sources — think boilers at palm oil mills, kilns at cement plants, and combustion units at power and manufacturing facilities. For higher-impact sources, periodic manual stack testing isn’t enough; the Department of Environment (DOE) expects <strong>continuous</strong> measurement, so that emissions are demonstrably within limits every hour of operation, not just on test day.</p>

<p>A CEMS continuously measures parameters such as <strong>particulate matter (dust)</strong> and <strong>opacity</strong>, records the data, and makes it available to both the operator and the regulator.</p>

<h2 id="the-three-things-the-doe-looks-for">The three things the DOE looks for</h2>

<p>In our experience sitting on both sides of the table — as a consultant and as a contributor to the DOE CEMS Guidelines — compliance comes down to three questions:</p>

<ol>
  <li><strong>Is the system measuring the right things, accurately?</strong> The analysers must be appropriate for your source and kept within accepted tolerances through scheduled calibration.</li>
  <li><strong>Can you prove it?</strong> This is where <a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/"><strong>QAL2 and QAL3</strong> testing</a> (to the EN 14181 standard) comes in — formal quality-assurance procedures that demonstrate, and keep demonstrating, that your CEMS data is reliable.</li>
  <li><strong>Is the data reaching the regulator?</strong> CEMS data must be transmitted to the DOE’s <strong>iRemote / CEMS 3.0</strong> national platform. A system that measures perfectly but doesn’t report continuously is not a compliant system.</li>
</ol>

<h2 id="where-operators-get-caught-out">Where operators get caught out</h2>

<p>The most common compliance gaps we see aren’t dramatic failures — they’re quiet ones:</p>

<ul>
  <li><strong>Calibration drift</strong> that goes unnoticed until an audit.</li>
  <li><strong>A lapsed QAL certification</strong>, because QAL3 is an ongoing obligation, not a one-time event.</li>
  <li><strong>A broken iRemote connection</strong> that stops transmitting without anyone noticing for days.</li>
</ul>

<p>Any of these can turn a well-run facility into a non-compliant one on paper — and that’s what triggers notices, fines, or in the worst case, a shutdown order.</p>

<h2 id="staying-inspection-ready">Staying inspection-ready</h2>

<p>The goal isn’t to pass one inspection; it’s to be ready for any inspection, any day. That means treating CEMS as a lifecycle, not a purchase:</p>

<blockquote>
  <p>Design and install it correctly, certify it to standard, maintain it on schedule, transmit continuously — and keep the paperwork in order behind all of it.</p>
</blockquote>

<p>That full-lifecycle ownership is exactly what we do for the operators we work with across Malaysia’s palm oil, energy, cement and manufacturing sectors.</p>

<p><strong>Not sure where your facility stands?</strong> <a href="/#contact">Get in touch</a> and we’ll help you find out — from the team that helped write the DOE CEMS Guidelines.</p>

<div class="related">
  <p class="label">Related insights</p>
  <ul>
    <li><a href="/insights/need-a-cems-clean-air-regulations-2014/">Do you even need a CEMS? What the law requires before you buy</a></li>
    <li><a href="/insights/cems-quality-assurance-chain-qal1-qal2-qal3-ast/">The CEMS quality-assurance chain: QAL1 → QAL2 → QAL3 → AST</a></li>
    <li><a href="/insights/cems-compliance-daily-half-hourly-rule-reg-17-3/">What "compliant" actually means: the daily-average and 2× half-hourly rule</a></li>
  </ul>
</div>

<hr />

<p><em>This article is general guidance, not legal advice. For obligations specific to your facility and source, refer to the current Environmental Quality (Clean Air) Regulations 2014 and the DOE CEMS Guidelines, or speak with us directly.</em></p>]]></content><author><name></name></author><summary type="html"><![CDATA[A plain-English guide to how Malaysia's Environmental Quality (Clean Air) Regulations 2014 shape Continuous Emission Monitoring System obligations — and how to stay inspection-ready.]]></summary></entry></feed>