EU Industrial BAT Conclusion Records — EEA IED

Keyless. Pay per record. Which Best Available Techniques conclusion each European industrial installation is held to — installation by installation.

This actor turns the European Environment Agency (EEA) Industrial Emissions Directive (IED) registry into clean, per-linkage records — the resolution of each IED production installation against the Best Available Techniques (BAT) conclusion it operates under. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per installation-to-BAT-conclusion link: the installation id and the BAT conclusion, plus the installation's facility name, country, and main IED activity. Regulatory-linkage grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

Under the IED, every major industrial installation must meet the emission levels associated with the Best Available Techniques for its sector — the "BAT conclusions." The IED registry records which BAT conclusion each installation is resolved against, and this actor extracts exactly that mapping: it reads the installation-to-BAT-conclusion table and joins each row to the installation's identity, delivering the installation id, the BAT conclusion cited verbatim, and the installation's facility name (an organisation, suppressed where the source flags the name confidential), its country, main IED Annex I activity, and status. It is the regulatory-linkage layer that ties an installation to the technique standard it is held to. You are billed only for records actually delivered.

Who buys this and for what job

• Environmental-compliance, permitting, and consultancy teams mapping installations to the BAT conclusions they must meet.
• Industrial-intelligence and ESG products segmenting facilities by the technique standard applied to them.
• Researchers and regulators' data teams studying BAT-conclusion coverage across sectors and countries.
• Data engineers who want the installation↔BAT-conclusion mapping as clean rows from a keyless source.

EEA licence — reuse with acknowledgement

One licence rider travels on every record. EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)." Where third-party content is marked, it keeps its own terms. The BAT conclusions are cited as published — this actor links, it does not interpret them or issue a compliance verdict.

Installation grain — no person data

The unit of every record is an installation and the BAT conclusion it resolves against — an organisation, never a person. The installation name is a facility name, suppressed where the source marks it confidential. There is no operator, contact, or responsible-person field in the linkage, and none is emitted; a person-key guard runs on every record as a backstop.

Sample output

Real rows from a live run of this actor (first 5 rows, selected columns).

One full record from the same run, exactly as delivered:

{
  "record_id": "154:WT",
  "installation_id": "154",
  "bat_conclusion": "WT",
  "installation_name": "Urðunarstaður Fíflholti",
  "country_code": "IS",
  "ied_annex_i_main_activity": "5.4",
  "installation_status": "functional",
  "reporting_year": "2017",
  "control_file_id": "22",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — installation-to-BAT-conclusion linkage. Reuse is permitted, including for commercial purposes, provided the source is acknowledged: 'Source: European Environment Agency (EEA)'. Third-party content, where marked, keeps its own terms.",
  "attribution": "Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Installation-to-BAT-conclusion linkage records at regulatory-linkage grain, from the EEA IED registry. Each record joins an IED production installation to a Best Available Techniques (BAT) conclusion it is resolved against, with the installation's FACILITY name (an organisation, suppressed where the source flags the name confidential), country, and main IED activity. Installation/organisation grain — no natural-person data. BAT conclusions are cited VERBATIM as published, never interpreted; a registry linkage, not a compliance verdict.",
  "observed_at": "2026-09-25T17:32:58Z"
}

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
bat_conclusion_record	$0.05	$0.045	$0.04	$0.0335

Delivered before charged. Blocked runs and empty results cost nothing.

Input

Field	Type	Default	Description
countryCode	string	—	Optional 2-letter country code to filter (e.g. DE, FR, IT).
maxRecords	integer	500	Ceiling on records delivered and billed.

Output

One JSON object per linkage. Real example (values as published):

{
  "record_id": "154:WT",
  "installation_id": "154",
  "bat_conclusion": "WT",
  "installation_name": "Urðunarstaður Fíflholti",
  "country_code": "IS",
  "ied_annex_i_main_activity": "5.4",
  "installation_status": "functional",
  "reporting_year": "2022",
  "control_file_id": "55",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Installation-to-BAT-conclusion linkage records ... cited VERBATIM ... never interpreted ...",
  "observed_at": "2026-08-22T00:00:00Z"
}

An unbilled RUN_RECEIPT records the robots check, the filter, rows matched and delivered, and whether charged equals delivered.

Field reference

Each record is one linkage. Keys: record_id (installation id + BAT conclusion), installation_id, and bat_conclusion. Installation identity: installation_name (facility/org, confidentiality-suppressed), country_code, ied_annex_i_main_activity, installation_status, and reporting_year. Provenance: control_file_id, source, source_url, licence, attribution, disclaimer, and observed_at.

How a run works

A run first re-reads the source host's robots posture from your runtime — the EEA DiscoData host — and stops at the door if that ever changes. It pages the installation-to-BAT-conclusion table, enriches each row with the installation's identity (suppressing the facility name where confidential), applies your optional countryCode filter, and flattens each linkage to one record — carrying the BAT conclusion verbatim, never interpreting it and never anything person-shaped — delivered before it is charged, so a blocked or empty run costs you nothing. The actor stops at your maxRecords ceiling and records charge_equals_delivered in the receipt.

Coverage and scope

The linkage table holds on the order of 478,000+ installation-to-BAT-conclusion rows. Because each record carries the country_code and ied_annex_i_main_activity, segmenting by country or activity sector is straightforward. Pull one country, or the whole table to seed a BAT-coverage map.

Working with the linkage

The mapping answers a specific regulatory question — which technique standard applies where — and the fields make it queryable. Because every record pairs the installation_id with the bat_conclusion, a compliance team can list every installation held to a given BAT conclusion, or every conclusion a given installation must meet, in one filter, and the ied_annex_i_main_activity groups those by sector. The installation_name and country_code anchor each row for QA, and because the conclusion codes are carried verbatim, the mapping joins cleanly to any external BAT-conclusion reference the buyer maintains. Two pulls can be diffed to see where new conclusions were applied between reporting rounds.

Installation enrichment and confidentiality

Each linkage row in the source carries only an internal installation id; on its own that id is opaque. This actor enriches every record from the IED installation register, adding the installation's facility name, country, main IED Annex I activity, status, and reporting year, so a buyer sees which real facility each row refers to without running a second query. The enrichment is done in bounded, cached batches so a large pull stays efficient. One rule is enforced throughout: where the source flags an installation's name as confidential, the name is suppressed and only the non-name identity (country, activity, status) is carried — the linkage still resolves on the identifiers, but a withheld name is never revealed. This keeps the records both useful and faithful to the source's own confidentiality decisions.

Cost guidance

One bat_conclusion_record per delivered link: cost = links delivered × your plan's per-record price. Scope with countryCode to keep runs bounded. The table is ~478,000 rows; 1,000 rows is $50 (Free) / $33.50 (Gold).

Honest limitations

• A linkage, not a verdict. These are the registry's own installation↔BAT-conclusion joins; conclusions are cited verbatim, never interpreted.
• Name may be withheld. Where the source marks the installation name confidential, it is suppressed; the identifiers still resolve.
• Acknowledge the EEA. The acknowledgement travels on every record.
• No person data of any kind.

Differentiation

It is distinct from the fleet's eu-industrial-emissions-records (IED facility emissions) — this cell carries the installation↔BAT-conclusion regulatory mapping, a different table for a different job. It is the BAT-conclusion member of a five-cell EEA industrial/water family (stricter-permit conditions, ETS linkage, offsite transfers, pesticide monitoring).

The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

• EU Stricter Permit Condition Records — EEA IED
• EU Industrial ETS Linkage Records — EEA IED
• EU Offsite Pollutant Transfer Records — EEA E-PRTR
• EU Industrial Emissions Records — EEA IED Facilities
• EU Air Quality Measure Records — EEA AQ Plans

Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry (discodata.eea.europa.eu). EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)"; marked third-party content keeps its own terms. Regulatory-linkage grain; installation (facility/organisation) identity only, name suppressed where confidential; no natural-person data of any kind. BAT conclusions cited verbatim, not interpreted; a registry linkage, not a compliance verdict.