Thermal Power Plant (with and without CCS)

Contents

Overview | Asset Structure | Flow Equations | Input File (Standard Format) | Types - Asset Structure | Constructors | Examples | Best Practices | Input File (Advanced Format)

Overview

Thermal power plant assets in Macro represent electricity generation technologies that convert fuel into electricity through combustion or other thermal processes. These assets can include conventional thermal plants (coal, natural gas) and those with carbon capture and storage (CCS) capabilities. They are defined using either JSON or CSV input files placed in the assets directory, typically named with descriptive identifiers like natgas_power.json, nuclear_power.json, or coal_power.json.

Asset Structure

A thermal power plant asset consists of five main components:

1. Transformation Component: Balances the fuel and electricity flows
2. Fuel Edge: Represents the fuel supply to the plant
3. Electricity Edge: Represents the electricity production (can have unit commitment operations)
4. CO₂ Edge: Represents the CO₂ emissions
5. CO₂ Captured Edge: Represents the CO₂ captured (only if CCS is present)

Here is a graphical representation of the thermal power plant asset:

Flow Equations

The thermal power plant asset follows these stoichiometric relationships:

\[\begin{aligned} \phi_{fuel} &= \phi_{elec} \cdot \epsilon_{fuel\_consumption} \\ \phi_{co2} &= \phi_{fuel} \cdot \epsilon_{emission\_rate} \\ \phi_{co2\_captured} &= \phi_{fuel} \cdot \epsilon_{co2\_capture\_rate} \quad \text{(if CCS)} \\ \end{aligned}\]

Where:

• $\phi$ represents the flow of each commodity
• $\epsilon$ represents the stoichiometric coefficients defined in the Conversion Process Parameters section.

Input File (Standard Format)

The easiest way to include a thermal power plant asset in a model is to create a new file (either JSON or CSV) and place it in the assets directory together with the other assets.

your_case/
├── assets/
│   ├── thermal_power.json    # or thermal_power.csv
│   ├── other_assets.json
│   └── ...
├── system/
├── settings/
└── ...

This file can either be created manually, or using the template_asset function, as shown in the Adding an Asset to a System section of the User Guide. The file will be automatically loaded when you run your Macro model.

The following is an example of a thermal power plant asset input file with unit commitment enabled and burning natural gas:

{
    "NaturalGasPowerCCS": [
        {
            "type": "ThermalPowerCCS",
            "instance_data": [
                {
                    "id": "SE_naturalgas_ccccsavgcf_conservative_0",
                    "location": "SE",
                    "fuel_commodity": "NaturalGas",
                    "uc": true,
                    "co2_sink": "co2_sink",
                    "elec_constraints": {
                        "MinFlowConstraint": true,
                        "MinUpTimeConstraint": true,
                        "MinDownTimeConstraint": true
                    },
                    "capacity_size": 377,
                    "fuel_consumption": 2.09809579,
                    "emission_rate": 0.018104824,
                    "capture_rate": 0.162943412,
                    "investment_cost": 105122.0711,
                    "fixed_om_cost": 47800,
                    "variable_om_cost": 3.76,
                    "startup_cost": 97,
                    "startup_fuel_consumption": 0.058614214,
                    "min_up_time": 4,
                    "min_down_time": 4,
                    "ramp_up_fraction": 1,
                    "ramp_down_fraction": 1,
                    "min_flow_fraction": 0.5
                }
            ]
        }
    ]
}

The following tables outline the attributes that can be set for a thermal power plant asset.

Essential Attributes

Conversion Process Parameters

The following set of parameters control the conversion process and stoichiometry of the thermal power plant asset (see Flow Equations for more details).

Constraints Configuration

Thermal power plant assets can have different constraints applied to them, and the user can configure them using the following fields:

For example, if the user wants to apply the BalanceConstraint to the transformation component and the CapacityConstraint to the electricity edge, the constraints fields should be set as follows:

{
    "transform_constraints": {
        "BalanceConstraint": true
    },
    "elec_constraints": {
        "CapacityConstraint": true
    }
}

Users can refer to the Adding Asset Constraints to a System section of the User Guide for a list of all the constraints that can be applied to the different components of a thermal power plant asset.

Default constraints

To simplify the input file and the asset configuration, the following constraints are applied to the thermal power plant asset by default:

• Balance constraint (applied to the transformation component)
• Capacity constraint (applied to the electricity edge)
• Ramping limits constraint (applied to the electricity edge)

Unit commitment constraints (when uc is set to true):

• Minimum up and down time constraint (applied to the electricity edge)

Investment Parameters

Additional Investment Parameters

Maximum and minimum capacity constraints

If MaxCapacityConstraint or MinCapacityConstraint are added to the constraints dictionary for the electricity edge, the following parameters are used by Macro:

Economic Parameters

Operational Parameters

Additional Operational Parameters

Unit commitment parameters (when uc is set to true)

Minimum flow constraint

If MinFlowConstraint is added to the constraints dictionary for the electricity edge, the following parameter is used:

Ramping limit constraint

If RampingLimitConstraint is added to the constraints dictionary for the electricity edge, the following parameters are used:

Minimum up and down time constraints

If MinUpTimeConstraint or MinDownTimeConstraint are added to the constraints dictionary for the electricity edge, the following parameters are used:

Types - Asset Structure

The ThermalPower and ThermalPowerCCS assets are defined as follows:

struct ThermalPower{T} <: AbstractAsset
    id::AssetId
    thermal_transform::Transformation
    elec_edge::Union{Edge{<:Electricity},EdgeWithUC{<:Electricity}}
    fuel_edge::Edge{<:T}
    co2_edge::Edge{<:CO2}
end

struct ThermalPowerCCS{T} <: AbstractAsset
    id::AssetId
    thermalpowerccs_transform::Transformation
    elec_edge::Union{Edge{<:Electricity},EdgeWithUC{<:Electricity}}
    fuel_edge::Edge{<:T}
    co2_edge::Edge{<:CO2}
    co2_captured_edge::Edge{<:CO2Captured}
end

Constructors

Default constructor

ThermalPower(id::AssetId, thermal_transform::Transformation, elec_edge::Union{Edge{<:Electricity},EdgeWithUC{<:Electricity}}, fuel_edge::Edge{<:Fuel}, co2_edge::Edge{<:CO2})

ThermalPowerCCS(id::AssetId, thermalpowerccs_transform::Transformation, elec_edge::Union{Edge{<:Electricity},EdgeWithUC{<:Electricity}}, fuel_edge::Edge{<:Fuel}, co2_edge::Edge{<:CO2}, co2_captured_edge::Edge{<:CO2Captured})

Factory constructor

make(asset_type::Type{ThermalPower}, data::AbstractDict{Symbol,Any}, system::System)
make(asset_type::Type{ThermalPowerCCS}, data::AbstractDict{Symbol,Any}, system::System)

Examples

This section contains examples of how to use the thermal power plant asset in a Macro model.

Nuclear Power Plant

This example shows a nuclear power plant with unit commitment enabled and using uranium as fuel. The asset has an existing capacity that is only allowed to be retired. A MinFlowConstraint constraint is applied to the electricity edge with a minimum flow fraction of 0.5. A MinUpTimeConstraint and MinDownTimeConstraint constraint is applied to the electricity edge with a minimum up and down time of 36 hours. A RampingLimitConstraint constraint is applied to the electricity edge with a ramping limit of 0.25. The asset has an availability time series loaded from a CSV file.

JSON Format:

Note that the global_data field is used to set the fields and constraints that are common to all instances of the same asset type.

{
    "NuclearPower": [
        {
            "type": "ThermalPower",
            "instance_data": [
                {
                    "id": "SE_nuclear_1",
                    "location": "SE",
                    "timedata": "Uranium",
                    "fuel_commodity": "Uranium",
                    "fuel_start_vertex": "uranium_source",
                    "co2_sink": "co2_sink",
                    "uc": true,
                    "can_retire": true,
                    "can_expand": false,
                    "existing_capacity": 33632.288,
                    "capacity_size": 1051.009,
                    "elec_constraints": {
                        "MinFlowConstraint": true,
                        "MinUpTimeConstraint": true,
                        "MinDownTimeConstraint": true
                    },
                    "fuel_consumption": 3.064351108,
                    "fixed_om_cost": 199087.824,
                    "variable_om_cost": 2.34,
                    "min_flow_fraction": 0.5,
                    "startup_cost": 1000,
                    "min_up_time": 36,
                    "min_down_time": 36,
                    "ramp_up_fraction": 0.25,
                    "ramp_down_fraction": 0.25,
                    "startup_fuel_consumption": 0.0
                }
            ]
        }
    ]
}

CSV Format:

Multiple Natural Gas Fired Combined Cycle Plants in Different Zones with CCS

This example shows three natural gas fired combined cycle plants with unit commitment enabled and using natural gas as fuel. Each asset has an existing capacity that is only allowed to be retired. A MinFlowConstraint constraint is applied to the electricity edge with a minimum flow fraction of 0.444, 0.526, and 0.41. A MinUpTimeConstraint and MinDownTimeConstraint constraint is applied to the electricity edge with a minimum up and down time of 6 hours. A RampingLimitConstraint constraint is applied to the electricity edge with a ramping limit of 0.64. The asset has an availability time series loaded from a CSV file.

JSON Format:

{
    "NaturalGasPower": [
        {
            "type": "ThermalPower",
            "global_data": {
                "timedata": "NaturalGas",
                "fuel_commodity": "NaturalGas",
                "co2_sink": "co2_sink",
                "uc": true,
                "elec_constraints": {
                    "MinFlowConstraint": true,
                    "MinUpTimeConstraint": true,
                    "MinDownTimeConstraint": true
                }
            },
            "instance_data": [
                {
                    "id": "MIDAT_natural_gas_fired_combined_cycle_1",
                    "location": "MIDAT",
                    "emission_rate": 0.181048235160161,
                    "fuel_consumption": 2.249613533,
                    "can_retire": true,
                    "can_expand": false,
                    "existing_capacity": 4026.4,
                    "investment_cost": 0.0,
                    "fixed_om_cost": 16001,
                    "variable_om_cost": 4.415,
                    "capacity_size": 125.825,
                    "startup_cost": 89.34,
                    "startup_fuel_consumption": 0.58614214,
                    "min_up_time": 6,
                    "min_down_time": 6,
                    "ramp_up_fraction": 0.64,
                    "ramp_down_fraction": 0.64,
                    "min_flow_fraction": 0.444
                },
                {
                    "id": "NE_natural_gas_fired_combined_cycle_1",
                    "location": "NE",
                    "emission_rate": 0.181048235160161,
                    "fuel_consumption": 2.511912141,
                    "can_retire": true,
                    "can_expand": false,
                    "existing_capacity": 6119.616,
                    "investment_cost": 0.0,
                    "fixed_om_cost": 16001,
                    "variable_om_cost": 4.415,
                    "capacity_size": 127.492,
                    "startup_cost": 89.34,
                    "startup_fuel_consumption": 0.58614214,
                    "min_up_time": 6,
                    "min_down_time": 6,
                    "ramp_up_fraction": 0.64,
                    "ramp_down_fraction": 0.64,
                    "min_flow_fraction": 0.526
                },
                {
                    "id": "SE_natural_gas_fired_combined_cycle_1",
                    "location": "SE",
                    "emission_rate": 0.181048235160161,
                    "fuel_consumption": 2.132092034,
                    "can_retire": true,
                    "can_expand": false,
                    "existing_capacity": 26218.712,
                    "investment_cost": 0.0,
                    "fixed_om_cost": 9496,
                    "variable_om_cost": 3.504,
                    "capacity_size": 504.206,
                    "startup_cost": 89.34,
                    "startup_fuel_consumption": 0.58614214,
                    "min_up_time": 6,
                    "min_down_time": 6,
                    "ramp_up_fraction": 0.64,
                    "ramp_down_fraction": 0.64,
                    "min_flow_fraction": 0.41
                }
            ]
        }
    ]
}

CSV Format:

Best Practices

1. Use global data for common parameters: Use the global_data field to set the fields and constraints that are common to all instances of the same asset type.
2. Set realistic efficiency parameters: Ensure fuel consumption, emission rates, and capture rates are accurate for the technology being modeled
3. Use meaningful IDs: Choose descriptive identifiers that indicate location and technology type
4. Consider unit commitment carefully: Enable unit commitment only when detailed operational modeling is needed
5. Use constraints selectively: Only enable constraints that are necessary for your modeling needs
6. Validate costs: Ensure investment and O&M costs are in appropriate units and time periods
7. Test configurations: Start with simple configurations and gradually add complexity
8. Separate conventional vs CCS plants: Use different asset types for conventional and CCS thermal plants
9. Set appropriate ramp rates: Consider the actual operational characteristics of the technology

Input File (Advanced Format)

Macro provides an advanced format for defining thermal power plant assets, offering users and modelers detailed control over asset specifications. This format builds upon the standard format and is ideal for those who need more comprehensive customization.

To understand the advanced format, consider the graph representation and the type definition of a thermal power plant asset. The input file mirrors this hierarchical structure.

A thermal power plant asset in Macro is composed of a transformation component, represented by a Transformation object, and multiple edges (fuel, electricity, CO2, and optionally CO2 captured), each represented by an Edge object. The input file for a thermal power plant asset is therefore organized as follows:

{
    "transforms":{
        // ... transformation-specific attributes ...
    },
    "edges":{
        "fuel_edge": {
            // ... fuel_edge-specific attributes ...
        },
        "elec_edge": {
            // ... elec_edge-specific attributes ...
        },
        "co2_edge": {
            // ... co2_edge-specific attributes ...
        },
        "co2_captured_edge": {
            // ... co2_captured_edge-specific attributes, only if CCS is present ...
        }
    }
}

Each top-level key (e.g., "transforms" or "edges") denotes a component type. The second-level keys either specify the attributes of the component (when there is a single instance) or identify the instances of the component when there are multiple instances.

Below is an example of an input file for a thermal power plant asset that sets up multiple thermal plants across different regions:

{
    "NaturalGasPower": [
        {
            "type": "ThermalPower",
            "global_data": {
                "transforms": {
                    "timedata": "NaturalGas",
                    "constraints": {
                        "BalanceConstraint": true
                    }
                },
                "edges": {
                    "elec_edge": {
                        "commodity": "Electricity",
                        "unidirectional": true,
                        "has_capacity": true,
                        "uc": true,
                        "integer_decisions": false,
                        "constraints": {
                            "CapacityConstraint": true,
                            "RampingLimitConstraint": true,
                            "MinFlowConstraint": true,
                            "MinUpTimeConstraint": true,
                            "MinDownTimeConstraint": true
                        }
                    },
                    "fuel_edge": {
                        "commodity": "NaturalGas",
                        "unidirectional": true,
                        "has_capacity": false
                    },
                    "co2_edge": {
                        "commodity": "CO2",
                        "unidirectional": true,
                        "has_capacity": false,
                        "end_vertex": "co2_sink"
                    }
                }
            },
            "instance_data": [
                {
                    "id": "MIDAT_natural_gas_fired_combined_cycle_1",
                    "transforms": {
                        "emission_rate": 0.181048235160161,
                        "fuel_consumption": 2.249613533
                    },
                    "edges": {
                        "elec_edge": {
                            "end_vertex": "elec_MIDAT",
                            "can_retire": true,
                            "can_expand": false,
                            "existing_capacity": 4026.4,
                            "investment_cost": 0.0,
                            "fixed_om_cost": 16001,
                            "variable_om_cost": 4.415,
                            "capacity_size": 125.825,
                            "startup_cost": 89.34,
                            "startup_fuel_consumption": 0.58614214,
                            "min_up_time": 6,
                            "min_down_time": 6,
                            "ramp_up_fraction": 0.64,
                            "ramp_down_fraction": 0.64,
                            "min_flow_fraction": 0.444
                        },
                        "fuel_edge": {
                            "start_vertex": "natgas_MIDAT"
                        }
                    }
                },
                {
                    "id": "NE_natural_gas_fired_combined_cycle_1",
                    "transforms": {
                        "emission_rate": 0.181048235160161,
                        "fuel_consumption": 2.511912141
                    },
                    "edges": {
                        "elec_edge": {
                            "end_vertex": "elec_NE",
                            "can_retire": true,
                            "can_expand": false,
                            "existing_capacity": 6119.616,
                            "investment_cost": 0.0,
                            "fixed_om_cost": 16001,
                            "variable_om_cost": 4.415,
                            "capacity_size": 127.492,
                            "startup_cost": 89.34,
                            "startup_fuel_consumption": 0.58614214,
                            "min_up_time": 6,
                            "min_down_time": 6,
                            "ramp_up_fraction": 0.64,
                            "ramp_down_fraction": 0.64,
                            "min_flow_fraction": 0.526
                        },
                        "fuel_edge": {
                            "start_vertex": "natgas_NE"
                        }
                    }
                },
                {
                    "id": "SE_natural_gas_fired_combined_cycle_1",
                    "transforms": {
                        "emission_rate": 0.181048235160161,
                        "fuel_consumption": 2.132092034
                    },
                    "edges": {
                        "elec_edge": {
                            "end_vertex": "elec_SE",
                            "can_retire": true,
                            "can_expand": false,
                            "existing_capacity": 26218.712,
                            "investment_cost": 0.0,
                            "fixed_om_cost": 9496,
                            "variable_om_cost": 3.504,
                            "capacity_size": 504.206,
                            "startup_cost": 89.34,
                            "startup_fuel_consumption": 0.58614214,
                            "min_up_time": 6,
                            "min_down_time": 6,
                            "ramp_up_fraction": 0.64,
                            "ramp_down_fraction": 0.64,
                            "min_flow_fraction": 0.41
                        },
                        "fuel_edge": {
                            "start_vertex": "natgas_SE"
                        }
                    }
                }
            ]
        }
    ]
}

Key Points

• The global_data field is utilized to define attributes and constraints that apply universally to all instances of a particular asset type.
• The start_vertex and end_vertex fields indicate the nodes to which the edges are connected. These nodes must be defined in the nodes.json file.
• By default, only the electricity edge is allowed to expand as a modeling decision (see note below)
• The electricity edge can have unit commitment operations enabled by setting the uc attribute to true.
• For a comprehensive list of attributes that can be configured for the transformation and edge components, refer to the transformation and edges pages of the Macro manual.