core_eia860__assn_boiler_generator

package: pudl

Association table providing connections between boilers and generators.

Most-recent data:

2024

Processing:

Data has been cleaned and organized into well-modeled tables that serve as building blocks for downstream wide tables and analyses.

Source:

EIA Form 860 -- Annual Electric Generator Report (Schedule 6, Part A)

Primary key:

plant_id_eia, report_date, generator_id, boiler_id

Usage Warnings

  • Contains information from multiple raw inputs.

Additional Details

Augmented with various heuristics within PUDL.

Columns
plant_id_eia

The unique six-digit facility identification number, also called an ORISPL, assigned by the Energy Information Administration.

report_date

Date reported.

generator_id

Generator ID is usually numeric, but sometimes includes letters. Make sure you treat it as a string!

boiler_id

Alphanumeric boiler ID.

unit_id_eia

EIA-assigned unit identification code.

unit_id_pudl

Dynamically assigned PUDL unit id. WARNING: This ID is not guaranteed to be static long term as the input data and algorithm may evolve over time.

boiler_generator_assn_type_code

Indicates whether boiler associations with generator during the year were actual or theoretical. Only available before 2013.

steam_plant_type_code

Code that describes types of steam plants from EIA 860. See steam_plant_types_eia table for more details.

bga_source

The source from where the unit_id_pudl is compiled. The unit_id_pudl comes directly from EIA 860, or string association (which looks at all the boilers and generators that are not associated with a unit and tries to find a matching string in the respective collection of boilers or generator), or from a unit connection (where the unit_id_eia is employed to find additional boiler generator connections).

data_maturity

Maturity of the source data published by EIA that is reflected in this record. EIA releases data incrementally over time, including monthly updates, annual year-to-date updates, provisional early releases of annual data, and final annual release data that is not expected to change further. Records sourced from multiple upstream EIA datasets may have no well defined data maturity. Records whose values have been inferred within PUDL will also have no data maturity.