EU Industrial Inspection Authority Records — EEA IED

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

This actor turns the European Environment Agency (EEA) Industrial Emissions Directive (IED) registry into clean, per-installation records — the link between each of Europe's IED production installations and the competent AUTHORITY organisation responsible for inspecting it. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per authority-to-installation link: the competent authority's organisation name, the installation's identity (facility name, country, main IED activity), and the reporting scope. Authority / installation grain, structured for regulatory mapping, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

Under the IED, each production installation is inspected by a designated competent authority, and the registry records that relationship. This actor reads that competent-authority table and flattens each authority-to-installation link into a single analysis-ready record: the competent authority's organisation name (a regulatory body, never a person), an address-confidentiality flag, and the installation it is linked to — enriched with the installation's facility name (suppressed where the source flags it confidential), country, main IED Annex I activity, and status. The source table also carries an authority contact block — an individual contact name, an email address, a telephone and fax number, and a street address — and none of those columns is ever selected. What remains is a clean regulatory map: which authority organisation is responsible for which installation, and where that installation sits. You are billed only for records actually delivered.

Who buys this and for what job

• Regulatory-intelligence and compliance teams mapping which competent authority oversees which industrial installation across Europe.
• Environmental consultancies building authority-by-installation reference tables for permitting and inspection work.
• Market and site-intelligence products attaching a regulator to each IED installation.
• Data engineers who want the IED competent-authority linkage 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 registry linkages 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 competent-authority-to-installation link — an organisation linked to an installation, never a person. The source table carries a contact block: individualName, electronicMailAddress, telephoneNo, faxNo, and a street address (streetName, buildingNumber, city, postalCode). 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 on a record. Only the authority organisation name is carried, and a person-key guard runs on every record as a backstop. The installation's facility name is itself an organisation name, suppressed where the source flags it confidential.

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",
  "authority_organisation_name": "The Environmental Inspectorate",
  "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 — competent-authority-to-installation inspection assignment. 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": "Competent-authority-to-installation records at authority/installation grain from the EEA IED registry: each record links an IED production installation to the competent AUTHORITY organisation responsible for inspecting it, with the installation's identity (facility name, suppressed where flagged confidential; country; main IED activity). 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. Installation/organisation grain — no natural-person data. A registry linkage, not a compliance verdict, and not an inspection outcome (the source table carries no date, type, or outcome).",
  "observed_at": "2026-09-25T17:21:11Z"
}

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
inspection_authority_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).
maxRecords	integer	500	Ceiling on records delivered and billed.

Output

One JSON object per authority-to-installation link. Real example (values as published):

{
  "record_id": "1:1",
  "authority_organisation_name": "The Environmental Inspectorate",
  "address_confidentiality": null,
  "installation_id": "1",
  "installation_name": "Example Industrial Installation",
  "country_code": "EE",
  "ied_annex_i_main_activity": "1.1",
  "installation_status": "functional",
  "reporting_year": "2018",
  "control_file_id": "15",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "attribution": "Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Competent-authority-to-installation records ... contact block STRUCTURALLY EXCLUDED ...",
  "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 authority-to-installation link. Authority: authority_organisation_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. Keys: record_id and control_file_id. Provenance: 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 competent-authority table ordered by installation, enriches each page's installation identity from the production-installation register, applies your optional countryCode filter, and flattens each link to one record — carrying the authority organisation name only, never the individual contact block — 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 competent-authority table holds on the order of 515,000+ authority-to-installation links. Because each record carries the country_code, the authority organisation name, and the installation identity, segmenting by country or authority is straightforward. Pull one country, or the whole table to seed a regulator-by-installation reference.

Working with the linkage

The linkage is a regulatory map, and the fields make it queryable. Because every record pairs an authority_organisation_name with an installation_id and its country_code, an analyst can group installations by their competent authority, or list every installation a given authority organisation oversees, 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, so the map is not just ids. The address_confidentiality flag preserves the reporting reality where an authority's address was marked confidential at source, without ever carrying the address itself.

Identifiers and joins

Every record carries an installation_id, which is the stable key back to the fleet's other IED cells — emissions, permit conditions, BAT conclusions, derogations, and combustion parts — so a buyer can attach a competent authority to any of those on an identifier rather than a fuzzy name match. The authority organisation name gives a human-readable regulator label for QA. Because the individual contact block is never selected, the record stays a clean organisation-to-organisation linkage: which regulator oversees which installation, and nothing person-shaped.

Cost guidance

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

Honest limitations

• A linkage, not an inspection log. The source table records which competent authority is responsible for each installation; it carries no inspection date, type, or outcome, and this actor invents none.
• Contact block excluded by design. The individual contact name, email, phone, fax, and street address are never selected, so this dataset does not tell you who to contact — only which authority organisation is responsible.
• Enriched identity. The installation name and activity come from the production-installation register, and the facility name is suppressed where flagged confidential.
• 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 the fleet's eu-stricter-permit-condition-records and eu-industrial-bat-conclusion-records (which link installations to permit conditions and BAT conclusions), and from eu-industrial-facility-report-records (facility operating attributes). Its specific job is the IED competent-authority-to-installation linkage — which regulator organisation is responsible for which installation — 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 Stricter Permit Condition Records — EEA IED
• EU Industrial BAT Conclusion Records — EEA IED
• EU BAT Derogation Records — EEA IED
• EU Industrial Facility Report 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, and street address — is structurally excluded (never selected); only the authority organisation name is carried; no natural-person data of any kind. A registry linkage, not a compliance verdict, and not an inspection outcome; the source carries no inspection date, type, or outcome.