How to Read an ATEX Marking

Decode the equipment group, category, protection type, and temperature class in any ATEX marking — and keep those attributes clean across every supplier feed.

published enrichmentdistributors

When a distributor ingests fifty supplier feeds for hazardous-area equipment, the same flameproof junction box can arrive as II 2G Ex d IIC T6 from one vendor, Ex d IIC T6 Gb from a second, and a plain-text blob like ATEX Zone 1, flameproof, T6 from a third. To a naive catalog system these look like three different products. To a buyer specifying equipment for a Zone 1 gas area, all three must resolve to the same canonical record — with a single, validated ATEX string. That gap between raw supplier text and a trusted, searchable attribute is exactly the problem Claro solves: it parses the marking into structured fields, validates each field for internal consistency, matches the result to your existing golden records, and writes clean attributes back into your PIM or ERP.

Anatomy of an ATEX marking

An ATEX marking is the standardized string stamped on equipment intended for explosive atmospheres. It follows a fixed left-to-right order defined by the ATEX directive and the IEC/EN 60079 series.

First block — equipment group and category

The first element is the equipment group:

  • Group I — mining (firedamp and coal dust)
  • Group II — surface industries (all other explosive atmospheres)
  • Group III — dust-specific surface applications (in some newer markings)

Immediately after the group comes the category (1, 2, or 3). Category 1 is the highest level of protection; it is required for Zone 0 (gas) or Zone 20 (dust) locations where an explosive atmosphere is present continuously or for long periods. Category 2 covers Zone 1 / Zone 21; category 3 covers Zone 2 / Zone 22.

A capital G (gas) or D (dust) follows the category. So II 2 G is a surface-industry, category 2, gas product.

Second block — protection method and gas/dust group

After the Ex hexagon comes the protection-type code, which specifies how the equipment achieves safety:

Code Protection type Typical application
d Flameproof enclosure Switchgear, motors, junction boxes in Zone 1
e Increased safety Terminal boxes, luminaires in Zone 1
ia / ib / ic Intrinsic safety Sensors, transmitters, field instruments
m Encapsulation Electronic components, solenoid coils
p Pressurised enclosure Control panels, analysers
n Non-sparking (restricted breathing) Zone 2 only equipment
o Oil immersion Transformers, switchgear

The protection type is followed by the gas group (IIA, IIB, or IIC) for gas apparatus, or the dust group (IIIA, IIIB, IIIC) for dust apparatus. IIC is the most stringent gas group, covering hydrogen and acetylene atmospheres; IIA covers propane and similar gases.

Third block — temperature class

The temperature class (T1 through T6) is the maximum surface temperature the equipment may reach. It must remain below the auto-ignition temperature of the surrounding gas or vapour:

Class Max surface temperature Typical use case
T1 450 C Low-risk solvents
T2 300 C General hydrocarbons
T3 200 C Petroleum products
T4 135 C Acetaldehyde atmospheres
T5 100 C Carbon disulfide
T6 85 C Diethyl ether — most conservative

Optional suffix — Equipment Protection Level (EPL)

More recent markings include an EPL suffix such as Ga, Gb, Gc (gas) or Da, Db, Dc (dust). This maps closely to the category but is defined at the equipment level rather than for the installation zone. Gb is roughly equivalent to category 2 in a gas atmosphere.

A fully qualified modern marking therefore reads: Ex d IIC T4 Gb — flameproof, hydrogen-rated, 135 C maximum surface temperature, zone 1 gas protection level.

Why ATEX data almost never arrives clean

For distributors and marketplaces, ATEX attributes are among the highest-stakes fields in the catalog. A mismatch is not a formatting error; it is a safety and liability one. The problem is that clean data is the exception:

  • Spacing and ordering differ between suppliers (some write II2G, others write II 2 G)
  • The EPL suffix (Gb, Db) is present in some feeds and absent in others for the same product
  • Older certificates use category notation; newer ones use EPL notation
  • Some suppliers send a free-text description in place of a structured code
  • Identical products carry different temperature class representations (T4 vs 135°C max)

Until the string is parsed into discrete, normalized fields — group, category, protection type, gas group, temperature class, EPL — catalog logic treats formatting variants as separate products. Deduplication fails. Faceted search returns incomplete results. AI assistants cannot match a buyer’s zone specification to the right SKU.

BEFORE / AFTER: raw supplier feed vs. trusted catalog record

Without structured ATEX attributes With Claro normalization
Same product appears in 3-5 records with different marking formats One resolved entity per product with a single canonical ATEX string
Free-text blobs like 'ATEX Zone 1 flameproof T6' in description field Discrete fields: group=II, category=2, protection=d, gas group=IIC, T-class=T6, EPL=Gb
Faceted filter for 'Zone 1 / IIC / T6' returns incomplete results Filter matches every variant of that specification correctly
Duplicate SKUs accumulate as new supplier feeds are onboarded New records match against existing golden products at ingest
Internal consistency errors (wrong EPL for the stated category) reach customers Validation rules flag contradictions before publish
AI assistant cannot confidently match a buyer query to a product Single authoritative record with structured attributes AI can cite

Claro ingests the raw string from each supplier feed, parses it into the six structural fields above, runs a consistency check against the ATEX rules, and then matches the result against your existing catalog. Records that differ only in marking format are resolved to the same golden product. The normalized attribute values are written back to the correct fields in your PIM or ERP — no manual re-keying, no accumulation of variants, and no silent contradictions passed downstream.

How the blocks fit together: a worked example

Take the marking Ex d IIC T4 Gb:

  1. Ex — the universal symbol for equipment built to IEC/EN 60079. Confirms the product carries formal explosion-protection certification.
  2. d — flameproof enclosure. The housing can contain an internal ignition and prevent it from reaching the surrounding atmosphere.
  3. IIC — the most stringent gas group. Suitable for hydrogen and acetylene environments, and therefore also valid for IIB and IIA atmospheres.
  4. T4 — maximum surface temperature of 135 C. Safe for acetaldehyde and most common hydrocarbon atmospheres.
  5. Gb — Equipment Protection Level b for gas. Equivalent to category 2; suitable for Zone 1 installations where an explosive atmosphere is likely to occur in normal operation.

Reading end to end: this is a flameproof device, rated for the most demanding gas groups, with a 135 C surface-temperature limit, suitable for Zone 1 gas installations. A specifier can match this directly against their site zone classification without reading a data sheet.

FAQ

What does II 2 G mean in an ATEX marking?

It breaks into three parts. The roman numeral II is the equipment group for surface industries (group I covers mines). The digit 2 is the category, indicating a high level of protection suitable for Zone 1 (gas) or Zone 21 (dust). The letter G means the equipment is intended for a gas atmosphere; a D in that position would mean dust. So II 2 G is a surface-industry, category 2, gas product.

What is the difference between ATEX category and zone?

The category is a property of the equipment and describes its level of protection (1 being the highest, suitable for the most frequently hazardous areas). The zone is a property of the location and describes how often an explosive atmosphere is present. They are matched together: a Zone 0 location requires category 1 gas equipment, Zone 1 accepts category 2, and Zone 2 accepts category 3. Reading the marking tells you the category; the site survey tells you the zone.

What do the temperature classes T1 to T6 mean?

The temperature class is the maximum surface temperature the equipment can reach, and it must stay below the auto-ignition temperature of the surrounding gas. T1 allows up to 450 C and T6 allows up to 85 C, so T6 is the most conservative. Lower-numbered classes permit hotter surfaces. A product rated T4 or better is common for many hydrocarbon atmospheres.

What is the difference between Ex d and Ex e protection?

Ex d is a flameproof enclosure: it contains any internal explosion and prevents it from igniting the surrounding atmosphere. Ex e is increased safety: it applies extra measures to prevent arcs, sparks, and hot surfaces from occurring in the first place. They are different protection philosophies and are sometimes combined on the same device, which is why a marking can list more than one protection-type code.

Why do the same ATEX-rated products show up as duplicates in a catalog?

Because suppliers format the marking inconsistently. Spacing, ordering, the presence or absence of the EPL suffix (such as Gb or Db), and free-text descriptions all vary feed to feed. Until the string is parsed into normalized fields, matching logic treats each variant as a distinct product. Reading and structuring the marking at ingest is what collapses those variants onto a single canonical record.

How does Claro handle ATEX attribute normalization across supplier feeds?

Claro parses each incoming ATEX string into discrete fields (equipment group, category, protection type, gas group, temperature class, EPL), validates them for internal consistency, and writes the normalized values back to the corresponding attributes in your PIM or ERP. Records that differ only in marking format are matched to the same golden product, so duplicates do not accumulate as new supplier feeds are onboarded.

Claro

See how Claro handles this in production

This concept is one piece of keeping a catalog trusted. See how Claro resolves identity, enriches missing attributes, and validates every update before it reaches your PIM or ERP.

Learn more