Execute tasks when the grid is powered by renewable energy
Carbon Aware Computing (2022) All sources
category: Sustainability class: Task Rules
The basic idea behind the time shifting approach is moving the computing load into a point in time when the power grid has a maximum of renewable energy. This will result in a lower emission of CO2 of a computing task.
In addition to energy and hardware efficiency, carbon efficiency is one of the most important principles of green software development, like the Energiewende. Energy is used when it is available from renewables.
Applied to business processes, energy-intensive activities are not executed as soon as they become enabled, but at the point within their allowed window when the carbon intensity of the grid is lowest. Typical candidates are automated activities such as batch jobs, calculations, data processing or machine runs. The pattern therefore needs temporal slack: the service-level agreement or deadline defines how far execution may be shifted.
We shift the energy demand to a point in time when the carbon intensity of the grid is lower. To do this we need forecast data and software libraries to calculate the appropriate execution window. Open tools exist for this, such as the Carbon Aware SDK of the Green Software Foundation. The Camunda Carbon Reductor case study shows how a process engine places such a check in front of an energy-intensive task, and Reducing carbon emissions in a core system describes time shifting for the workloads of a bank’s risk platform.
The pattern complements Delay Execution, which also postpones work but for flexibility reasons, and Use eco-friendly resources, whose time-slot variation applies the same idea to energy as a resource.
■ This pattern ■ Baseline
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: Processes with energy-intensive automated activities and loose timing, e.g. batch processing, reporting, data transfers, model training or machine runs in production. Location: Activities with slack between enablement and deadline, visible as the gap between the preceding event and the SLA due date, and activities scheduled at fixed times regardless of grid conditions. Attributes: Activity duration and energy use, execution timestamps, deadline or SLA per case, and the region of execution, joined with historical grid carbon intensity. Constraints: Don’t shift customer-facing or time-critical activities; treat the SLA as a hard constraint; consider that shifting many cases into the same window can create load peaks.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints