How to Screen the Environmental Footprint of a Complex Industrial Project
Author:
Luke Boivin

Two suppliers can both tell you the footprint of making their equipment. That still leaves you with a project question: which configuration will have the lower emissions once the plant is running?
Imagine you’re comparing two ways to drive a compressor. You have preliminary fuel and electricity estimates, but the operating profile is still moving and the site’s power supply hasn’t been confirmed. You could wait for detailed engineering. Or you could build a screening life cycle assessment (LCA) now and find out which of those missing inputs could change the comparison.
The useful result is a shorter list of questions for engineering, procurement, and the site team. Here’s what that looks like on a complex industrial project.
Start with the decision and draw the boundary
Write down what you need to compare and what both options must deliver. Use the same boundary, output, and assessment method across scenarios. If you’re comparing two designs for the same facility, define which equipment, operating stages, and upstream inputs belong in the comparison. A common basis makes it easier to tell whether a result changed because of the design or because the scope moved.
Take an LNG train as an example. If the decision is about compressor drive, compare both designs per tonne of LNG loaded. Record which stages and supporting inputs are included. A model ending at the loading point answers a different question from one that carries the fuel through shipping, regasification, and end use. Name the endpoint alongside the result so that readers can tell which question you answered. NETL’s LNG lifecycle study illustrates how those stages can be modeled separately.
Build a first pass with the data you have
Map the process from inputs to output, then connect the equipment and activities at each stage. Use project-specific data where it’s available. For gaps, choose representative secondary data or engineering estimates and record the source, assumption, and limitation. If you can’t make a defensible estimate for a material input, flag it as unresolved and qualify what the comparison can tell you.
The European Commission’s ILCD Handbook describes screening as a way to find the processes and assumptions that matter before investing in a more detailed study. The GHG Protocol Product Standard applies the same idea to greenhouse gas data collection: use an initial estimate to identify where better data would make the most difference.
A useful first-pass model makes it easy to tell what each input rests on. For example:
Project data. A supplier’s preliminary fuel curve at stated loads. Record the revision and check that the loads represent how you expect the train to run.
Secondary data. A published electricity emissions factor. Record the region, period, and generation mix it represents so you can replace it when the power supply is known.
Engineering assumption. An operating profile from the design team. Record the assumed hours at each load and test a plausible alternative.
Open gap. A material input with no defensible estimate. Record who can supply it and which part of the comparison it could affect.

Results by data source for an illustrative compressor driver package.
That record matters when the project changes. If a supplier revises a performance estimate, you want to update that input and see which scenarios move without having to reconstruct the rest of the assessment.
A worked example from equipment to LNG train
In this example, we start by building one equipment model in CarbonGraph: a gas turbine driver package for a refrigerant compressor. The model shows the estimated contributions from materials, manufacturing, delivery, and end of life, along with the inputs behind those estimates. Equipment configurations can share a model structure while using different inputs.
Then we link equipment and process models into an LNG train spanning gas treatment, liquefaction, storage, and loading. The project view pulls those contributions together per tonne of LNG loaded and shows scenarios side by side. The dashboard values are illustrative. The workflow shows how a change to an equipment or operating assumption can be traced through to the project result. The short video below walks through that workflow, from a single equipment model to the full train.
This short video walks through that workflow, from a single equipment model to the full train:
What changes when you compare the drives?
The equipment model gives you a view of the package itself. Once it sits inside the project model, you can ask how it changes the operation of the train. For the gas turbine scenario, estimate fuel use at the expected loads and account for fuel supply and on-site combustion. For the electric-drive scenario, estimate electricity demand at the same duty and account for the power that would supply it. Keep equipment manufacturing impacts visible alongside the operating inputs if they are in scope. Apply the same throughput and equipment lifetime assumptions when converting those impacts to a per-tonne basis.
Suppose electric drive looks better with one plausible power supply and worse with another. That tells you the decision depends on the power assumption. Test plausible operating loads too. If the result is stable across the power cases but changes at part load, the supplier’s part-load performance curve becomes a higher-priority request. IEA assessment of LNG supply and abatement options

Gas turbine baseline compared with electric drive on two power supplies, by emission scope.
Turn the result into a data request
Look for two things: stages that make a large contribution and assumptions that could change the comparison. Sometimes they point to the same missing data. Run the comparison again using plausible values for the inputs you’re least sure about. If the preferred option changes, find out what you need to measure or ask for before making the decision.
For the LNG example, the follow-up could be three specific requests:
Equipment supplier: Fuel or electricity demand at the specified compressor duty, including expected part-load conditions and auxiliary loads.
Site power team: The proposed power source and the emissions factor that represents it, including alternatives still being considered.
Process engineering: Expected production and hours at each load so both scenarios use the same operating profile.
For each request, record which assumption the data will replace and what would make you revisit the comparison. When a response comes in, update the affected input and rerun the scenarios. The team can then see whether the original conclusion holds and where uncertainty still matters.
A useful first-pass model leaves the team with something concrete: a shortlist of the supplier specifications and operating data that could change the decision. As that evidence comes in, update the relevant inputs and rerun the comparison.
Have a project design you’d like to screen? Book a walkthrough.