# EU Industrial Facility Report Records — EEA IED (`nexgensignal/eu-industrial-facility-report-records`) Actor

Keyless pay-per-record EEA IED facility reports — employment band (verbatim, never headcount), operating hours, stack height/class. Partition by country. EEA acknowledge. GOLD $0.05 ladder.

- **URL**: https://apify.com/nexgensignal/eu-industrial-facility-report-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 facility report records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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):

```json
{
  "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](https://apify.com/nexgensignal/eu-combustion-installation-part-records)
- [EU Combustion Plant Records — EEA IED LCP](https://apify.com/nexgensignal/eu-combustion-plant-operating-hour-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Stricter Permit Condition Records — EEA IED](https://apify.com/nexgensignal/eu-stricter-permit-condition-records)
- [EU Offsite Pollutant Transfer Records — EEA E-PRTR](https://apify.com/nexgensignal/eu-offsite-pollutant-transfer-records)

*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.*

# Actor input Schema

## `countryCode` (type: `string`):

REQUIRED 2-letter country code (e.g. DE, FR) — the full facility-report table is a MONSTER (587,901 rows) and cannot be pulled unbounded.

## `year` (type: `integer`):

Optional year to filter.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "countryCode": "DE",
  "maxRecords": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "countryCode": "DE",
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-industrial-facility-report-records").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "countryCode": "DE",
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-industrial-facility-report-records").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "countryCode": "DE",
  "maxRecords": 500
}' |
apify call nexgensignal/eu-industrial-facility-report-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-industrial-facility-report-records"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZqA20hc2lqKEyqjrF/builds/iamu0hF60Wb70KHkY/openapi.json