EU Industrial Facility Report Records — EEA IED

Keyless. Pay per record. Every European industrial facility's annual operating hours, employment band, and stack attributes.

This actor turns the European Environment Agency (EEA) Industrial Emissions Directive (IED) registry into clean, per-facility-report records — the annual reports that Europe's industrial facilities file under the IED. Each run reads the EEA's keyless DiscoData SQL service for the country you choose and delivers one row per facility report: the reported employment band, the annual number of operating hours, and the stack attributes (representative stack height and height class). Facility-report grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

Each year, industrial facilities regulated under the IED report operational detail to their member state, and the EEA compiles it. This actor reads that facility-report table and flattens each report into a single analysis-ready record: the reported employment band (an organisation-size class, carried exactly as published), the annual number of operating hours, the representative stack height in metres and the stack-height class, the reporting country and year, any confidentiality reason, and the local and namespace identifiers that key the report to its facility. Values are carried verbatim. It is the facility-operations layer of the IED register. You are billed only for records actually delivered.

Who buys this and for what job

• Industrial-analytics, ESG, and market-sizing teams profiling facilities by size band, utilisation, and stack characteristics.
• Air-dispersion and environmental-modelling teams who need stack heights and classes for emission-plume work.
• Compliance and consultancy teams tracking facility operating hours across countries and years.
• Data engineers who want the IED facility reports 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 annual report values as filed — not a compliance verdict.

Facility grain — employment BAND only, no person data

The unit of every record is a facility annual report — an organisation, never a person. The employment figure is an organisation-size band as published (for example a size class), carried verbatim; it is never an exact headcount and is never used to infer the number of individuals at a facility. There is no operator, contact, or responsible-person field in the source, and none is emitted; the free-text remarks field is excluded at field selection, and a person-key guard runs on every record as a backstop.

A required partition — this is a large dataset

The facility-report table holds 587,901 rows, so this actor requires a partition: every run must set a countryCode. The country bounds the run; there is no unbounded all-Europe pull. An optional year filter narrows further, and maxRecords is the hard ceiling.

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
facility_report_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	—	Required 2-letter country code (e.g. DE, FR, IT).
year	integer	—	Optional reporting year to filter.
maxRecords	integer	500	Ceiling on records delivered and billed.

Output

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

{
  "record_id": "pf-1.Facility",
  "employment_band": "10-49",
  "number_of_operating_hours": 8760.0,
  "representative_stack_height_m": 45.0,
  "stack_height_class": "H2",
  "confidentiality_reason": null,
  "local_id": "pf-1.Facility",
  "namespace": "CH.CAED",
  "country_code": "CH",
  "reporting_year": 2018,
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Annual industrial-facility reports ... EMPLOYMENT BAND ... NEVER a headcount ...",
  "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 facility report. Identity: record_id, local_id, namespace, and report_data_id. Operations: employment_band (organisation-size band, verbatim) and number_of_operating_hours. Stack: representative_stack_height_m and stack_height_class. Scope: country_code, reporting_year, and confidentiality_reason. 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 facility-report table filtered to your countryCode (and optional year), and flattens each report to one record — carrying the employment band and stack attributes verbatim, never a remarks free-text field 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 facility-report table holds 587,901 rows across reporting countries and years. Because each record carries the country_code, employment_band, and reporting_year, segmenting by country, size band, or year is straightforward. Pull one country, or one year within a country, to seed a facility warehouse.

Working with the reports

The reports profile facilities at an organisational level, and the bands keep that safe. Because the employment_band is a published size class rather than a headcount, an analyst can segment the industrial base by size without ever touching individual-level data, and the number_of_operating_hours adds a utilisation dimension. The representative_stack_height_m and stack_height_class feed air-dispersion models directly, so an environmental team can attach stack geometry to a facility in one join, and the reporting_year supports a year-over-year view. The local and namespace identifiers key each report to its facility for a join to the fleet's other IED cells.

Cost guidance

One facility_report_record per delivered report: cost = reports delivered × your plan's per-record price. Always scope with countryCode and narrow with year. 1,000 reports is $50 (Free) / $33.50 (Gold).

Honest limitations

• Employment band, not headcount. The employment figure is a published band, carried verbatim; it is never an exact count and never used to infer individuals.
• As filed. Values are as reported for the year; this actor reformats, it does not audit.
• Partition required. Every run must set a countryCode.
• 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-industrial-emissions-records (IED facility emissions), from eu-combustion-installation-part-records (combustion-part category and operating hours), and from the IED linkage cells (BAT conclusions, ETS, permit conditions). Its specific job is the IED annual facility report — employment band, operating hours, and stack attributes, facility by facility.

The NexGen Signal family

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

• EU Combustion Installation Part Records — EEA IED
• EU Combustion Plant Records — EEA IED LCP
• EU Industrial Emissions Records — EEA IED Facilities
• EU Stricter Permit Condition Records — EEA IED
• EU Offsite Pollutant Transfer Records — EEA E-PRTR

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. Facility-report grain; the employment figure is an organisation-size band as published, never a headcount and never used to infer individuals; no operator, contact, or responsible-person field, no natural-person data of any kind. Values as filed, not a compliance verdict.