EU Industrial Permit Records — EEA IED

Keyless. Pay per record. Which competent authority permits each of Europe's IED industrial installations.

This actor turns the European Environment Agency (EEA) Industrial Emissions Directive (IED) registry into clean, per-record data — the link between each of Europe's IED production installations and the competent AUTHORITY responsible for permitting it. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per permit linkage row, structured for regulatory mapping and permitting intelligence, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

Under the Industrial Emissions Directive, each production installation is permitted by a designated competent authority, and the registry records that relationship. This actor reads that competent-authority permit table and delivers one record per authority-to-installation permit link: the competent authority's ORGANISATION name, an address-confidentiality flag, the control-file id, and the installation it is linked to — enriched with the installation's facility name (suppressed where flagged confidential), country, main IED Annex I activity, and status. It is the permitting map of Europe's industrial installations.

Who buys this and for what job

• Regulatory-intelligence teams mapping which authority permits which industrial installation across Europe
• Environmental consultancies building authority-by-installation reference tables for permitting work
• Market and site-intelligence products attaching a permitting regulator to each IED installation
• Data engineers who want the IED permit-authority linkage table 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. These are reported values as filed — not a compliance verdict.

Authority/installation grain — structural exclusion of the contact block, no person data

The unit of every record is a permitting-authority-to-installation link — an organisation linked to an installation, never a person. The source table carries an authority contact block: individualName, electronicMailAddress, telephoneNo, faxNo, and a street address. None of those columns is ever selected — the query reads only the authority organisationName, the addressConfidentiality flag, and the installation/control identifiers. The individual contact name, email, phone, fax, and street address are structurally excluded, so no natural-person name or contact detail can appear (the SIGNAL-18 inspection-authority pattern). Only the authority organisation name is carried, and 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": "1:1",
  "permitting_authority_name": "The Environmental Board",
  "address_confidentiality": null,
  "installation_id": "1",
  "installation_name": "Molycorp Silmet AS, Sillamäe haruldaste muldmetallide tehas",
  "country_code": "EE",
  "ied_annex_i_main_activity": "2.5(a)",
  "installation_status": "functional",
  "reporting_year": "2017",
  "control_file_id": "15",
  "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-permitting-authority permit 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-permitting-authority linkage records at authority/installation grain from the EEA IED registry: each record links an IED production installation to the competent AUTHORITY organisation responsible for PERMITTING it, with the installation's identity (facility name, suppressed where flagged confidential; country; main IED activity) and the control-file id. The authority contact block in the source — the individual contact name, email address, telephone, fax, and street address — is STRUCTURALLY EXCLUDED: those columns are never selected, so no natural-person name or contact detail can appear. Only the authority ORGANISATION name (an organisation, never a person) is carried. A person-key guard runs on every record as a backstop. A registry permit linkage, not a compliance verdict.",
  "observed_at": "2026-09-25T17:21:22Z"
}

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
industrial_permit_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 of the installation (e.g. DE, FR).
year	integer	—	Optional reporting year to filter.
maxRecords	integer	500	Ceiling on records delivered and billed.

Output

One JSON object per permit linkage row. Real example (values as reported):

{
  "record_id": "17706:5",
  "permitting_authority_name": "Example Environmental Agency",
  "address_confidentiality": null,
  "installation_id": "17706",
  "installation_name": "Alytus district boiler",
  "country_code": "LT",
  "ied_annex_i_main_activity": "1.1",
  "installation_status": "functional",
  "reporting_year": "2018",
  "control_file_id": "9",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "observed_at": "2026-08-22T00:00:00Z"
}

An unbilled RUN_RECEIPT records the robots check, the filters, rows seen and delivered, and whether charged equals delivered.

Field reference

Each record is one permit link. Authority: permitting_authority_name (the competent authority organisation) and address_confidentiality (the source's flag). Installation: installation_id, installation_name (facility/org name, suppressed where confidential), country_code, ied_annex_i_main_activity, installation_status, and reporting_year. Key: record_id and control_file_id. Provenance travels on every record: 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 IED permit-authority linkage table, and flattens each row to one record — carrying every value verbatim, 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 table holds on the order of 484,305 rows. Because each record carries the installation identity and the permitting authority organisation, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

Working with the data

The linkage is a permitting map, and the fields make it queryable. Because every record pairs a permitting_authority_name with an installation_id and country_code, an analyst can group installations by their permitting authority, or list every installation a given authority permits, in a single group-by. The enriched installation_name, ied_annex_i_main_activity, and installation_status give each linked installation a human-readable anchor and a sector code.

Permitting vs inspecting authority

The IED registry records two distinct competent-authority relationships for an installation — the authority that PERMITS it and the authority that INSPECTS it — and they are not always the same organisation. This cell resolves the permitting side; pairing it with the inspection-authority cell on the shared installation_id gives a buyer the full competent-authority picture for each installation.

Identifiers and joins

Every record carries an installation_id, the stable key back to the fleet's other IED cells — emissions, permit conditions, BAT conclusions, derogations, and the competent authority that INSPECTS the installation — so a buyer can attach a permitting authority to an installation's full regulatory picture on an identifier rather than a fuzzy name match.

Cost guidance

One industrial_permit_record per delivered row: cost = rows delivered × your plan's per-record price. Scope with countryCode and year to keep runs bounded. 1,000 rows is $50 (Free) / $33.50 (Gold).

Honest limitations

• As reported. Values, flags, and status labels are as filed; this actor reformats, it does not audit or recompute.
• A label, not a verdict. These are reported classifications/schedules/linkages, not an independent compliance assessment.
• Acknowledge the EEA. The acknowledgement travels on every record.
• No person data of any kind.

Differentiation

This is a net-new category for the NexGenData fleet. It is distinct from eu-industrial-inspection-records (which links installations to their INSPECTING authority) — this cell links them to their PERMITTING authority; a different competent-authority relationship. It is also distinct from eu-stricter-permit-condition-records (the stricter-than-BAT permit CONDITIONS on an installation), which carries the permit-condition text, not the authority linkage. Its specific job is the IED installation-to-permitting-authority linkage, with the source's individual contact block structurally excluded.

The NexGen Signal family

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

• EU Industrial Inspection Authority Records — EEA IED
• EU Stricter Permit Condition Records — EEA IED
• EU Industrial BAT Conclusion Records — EEA IED
• EU BAT Derogation Records — EEA IED
• EU Industrial Emissions Records — EEA IED Facilities

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. Authority/installation grain; the authority contact block — individual name, email, telephone, fax, street address — is structurally excluded (never selected); only the authority organisation name is carried. No natural-person data of any kind. Values as filed, not a compliance verdict.