# EU Combustion Installation Part Records — EEA IED (`nexgensignal/eu-combustion-installation-part-records`) Actor

Keyless pay-per-record EEA IED combustion installation-part reports — category, operating hours, district-heating share, refinery status. No persons. EEA acknowledge. $0.05 per record on the Free plan, $0.0335 on Gold.

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

## Pricing

from $33.50 / 1,000 combustion part 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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EU Combustion Installation Part Records — EEA IED

**Keyless. Pay per record. Every European combustion installation-part's category, operating hours, and heat-to-district-heating share.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) registry** into clean, per-installation-part records — the annual combustion reports for each part of Europe's industrial combustion installations. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per installation-part report: the combustion plant category, the annual number of operating hours, the share of useful heat production going to district heating, and whether the part sits within a refinery. Installation-part 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, operators report annual detail about the combustion parts of their installations. This actor reads that report table and flattens each installation-part into a single analysis-ready record: the combustion plant category (boiler, engine, gas turbine, and so on), the number of operating hours in the year, the proportion of useful heat production supplied to district heating, the within-refinery flag, the reporting country and year, any confidentiality reason, and the local and namespace identifiers that key the part back to its installation. Values are carried **verbatim** as reported. It is the combustion-operations layer of the IED register. You are billed only for records actually delivered.

### Who buys this and for what job

- **Energy, decarbonisation, and industrial-analytics teams** profiling combustion assets by category, utilisation, and district-heating role.
- **Compliance and consultancy teams** tracking operating hours and refinery status across installations.
- **ESG and heat-network products** mapping which combustion parts feed district heating and how heavily they run.
- **Data engineers** who want the IED combustion-part 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.

### Installation-part grain — no person data

The unit of every record is an installation-part annual report — an organisation-level report, never a person. There is **no operator, contact, or responsible-person field** in the source, and none is emitted; the free-text remarks and further-details fields are excluded at field selection. A person-key guard runs on every record as a backstop. Local and namespace identifiers are the part's own codes, not anyone's.

### Sample output

![Sample output — EU Combustion Installation Part Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-combustion-installation-part-records.png)

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

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

```json
{
  "record_id": "10011.A.INSTALLATIONPART",
  "combustion_plant_category": "Boiler",
  "number_of_operating_hours": 8616,
  "district_heating_useful_heat_share": null,
  "within_refinery": "False",
  "confidentiality_reason": null,
  "local_id": "10011.A.INSTALLATIONPART",
  "namespace": "FR.CAED",
  "report_data_id": "2",
  "control_file_id": "2",
  "country_code": "FR",
  "reporting_year": 2018,
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — combustion installation-part reports. 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": "Combustion installation-part annual reports at installation-part grain from the EEA IED registry: combustion plant category, annual operating hours, the share of useful heat production going to district heating, and refinery status. Installation/organisation grain — no natural-person data; there is no operator, contact, or responsible-person field in the source, and none is emitted (free-text remarks are excluded at field selection). Values carried VERBATIM as reported; a report record, not a compliance verdict.",
  "observed_at": "2026-09-25T17:31:29Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `combustion_part_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 (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 installation-part report. Real example (values as published):

```json
{
  "record_id": "10011.A.INSTALLATIONPART",
  "combustion_plant_category": "Boiler",
  "number_of_operating_hours": 8616.0,
  "district_heating_useful_heat_share": 12.5,
  "within_refinery": "No",
  "confidentiality_reason": null,
  "local_id": "10011.A.INSTALLATIONPART",
  "namespace": "AT",
  "report_data_id": "9",
  "country_code": "AT",
  "reporting_year": 2018,
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Combustion installation-part annual reports ... no operator, contact, or responsible-person field ...",
  "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 installation-part report. Identity: `record_id`, `local_id`, `namespace`, and `report_data_id`. Combustion: `combustion_plant_category`, `number_of_operating_hours`, `district_heating_useful_heat_share`, and `within_refinery`. Scope: `country_code` and `reporting_year`, plus `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 installation-part report table, applies your optional `countryCode` and `year` filters, and flattens each report to one record — carrying the values **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 installation-part report table holds on the order of **30,000+ rows**. Because each record carries the `country_code`, `combustion_plant_category`, and `reporting_year`, segmenting by country, category, or year is straightforward. Pull one country, or the whole table to seed a combustion-asset warehouse.

### Working with the reports

The reports profile how combustion assets actually run, and the fields make that comparable. Because every record carries the `number_of_operating_hours` alongside the `combustion_plant_category`, an analyst can rank asset categories by utilisation, and the `district_heating_useful_heat_share` surfaces which parts are cogenerating heat for district networks — a decarbonisation signal in a single column. The `within_refinery` flag isolates refinery combustion from the rest, and the `country_code` and `reporting_year` frame each report in time and place, so two years can be diffed to see how utilisation shifted. The local and namespace identifiers key each part back to its installation for a join to the fleet's other IED cells.

### Confidentiality and identifiers

Where the source marks a report with a confidentiality reason, that reason is carried on the record so a downstream consumer can see which values the operator flagged rather than treating a gap as missing data. The local and namespace identifiers are the installation-part's own codes in the reporting system — an organisation-level key, never a person — and they let a buyer join each combustion-part report back to its installation and to the fleet's other IED cells (facility reports, LCP plants, fuel inputs, emissions) without any fuzzy matching. Because the free-text remarks and further-details fields are excluded at field selection, the record stays a clean, structured row: category, hours, heat share, and refinery status, with nothing person-shaped and nothing narrative to sanitise downstream.

### Cost guidance

One `combustion_part_record` per delivered report: cost = reports delivered × your plan's per-record price. Scope with `countryCode` or `year`. The table is ~30,000 rows; 1,000 rows is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As filed.** Values are as reported for the year; this actor reformats, it does not audit.
- **Part grain.** These are installation-*part* reports; the plant-level LCP view is a separate fleet cell.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

Its specific job is the **IED combustion installation-*part* annual report** — category, operating hours, and district-heating share, part by part.

### The NexGen Signal family

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

- [EU Combustion Plant Records — EEA IED LCP](https://apify.com/nexgensignal/eu-combustion-plant-operating-hour-records)
- [EU Combustion Plant Fuel Input Records — EEA IED](https://apify.com/nexgensignal/eu-combustion-plant-fuel-input-records)
- [EU Industrial Facility Report Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-facility-report-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Industrial BAT Conclusion Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-bat-conclusion-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. Installation-part grain; 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`):

Optional 2-letter country code (e.g. DE, FR).

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

Optional year to filter.

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

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 10
}
```

# 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 = {
    "maxRecords": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-combustion-installation-part-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 = { "maxRecords": 10 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-combustion-installation-part-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 '{
  "maxRecords": 10
}' |
apify call nexgensignal/eu-combustion-installation-part-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-combustion-installation-part-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/CZp2ZU7UqSQnU41Tu/builds/3KegTHfxUvXY4o4T3/openapi.json