Concept

System boundary

structural

Overview

A system boundary is the line an analysis draws around a process to separate what it models internally from what it treats as crossing that line at a given quantity and price. It fixes the scope of every balance and every cost: anything inside is built and accounted for in detail, while anything crossing the boundary is counted once — as a purchased input, a sold output, or an emission.

Body

The boundary is a control surface. A system boundary is a closed surface drawn around a chosen set of unit operations. Operations inside it are modeled in detail — their streams, duties, and costs are resolved. Everything outside is not modeled; it enters the analysis only through the streams that cross the boundary. The boundary is what turns an open, indefinitely-extending web of industrial activity into a finite system that can be quantified.

Everything crossing the boundary is an input, an output, or an emission. A stream crossing inward is a feed: it is taken as given — a quantity at a price — rather than produced inside, so it enters the economics as a feedstock or energy cost. A stream crossing outward is a product or byproduct, carrying revenue or a credit; or, if it is waste, an emission or a disposal cost. Nothing wholly inside the boundary appears in the external accounting — only the crossings do. This is why the boundary, not the internal detail, sets what the analysis is an analysis of.

The boundary is the control volume for every balance. A mass balance is always taken over a defined region, and the system boundary is that region: what crosses inward must equal what crosses outward plus accumulation (zero at steady state). Drawing the boundary is therefore the first act of any balance — it declares which streams are the system’s inlets and outlets. The same region should serve the physical balance, the cost accounting, and the emissions accounting; they are three ledgers kept over one control volume.

Where the boundary is commonly placed. Boundaries nest at recognizable levels: a single unit operation; the process units alone; the whole plant (“gate-to-gate” — everything on-site between feed delivery and product dispatch); “cradle-to-gate,” reaching upstream to include the production of the purchased feedstocks and energy; and “cradle-to-grave,” reaching downstream through product use and end-of-life. Each step outward pulls more activity inside the modeled region and converts a former purchased input into an internally-produced stream.

System boundary vs. battery limits. The battery limits (ISBL / OSBL) are a related but narrower, on-site notion: the physical fence separating the process equipment from the supporting utilities and infrastructure on the same site, used chiefly to allocate capital cost. The system boundary is the broader analytical scope — it can sit anywhere from a single operation to cradle-to-grave, including upstream and off-site activity that no on-site fence contains. The two coincide only when the analysis happens to be scoped exactly to the plant’s process units.

The boundary is a modeling choice. Like the granularity with which a process is cut into unit operations, where the boundary falls is chosen, not given by nature. Two valid analyses of the same technology can draw it differently — one buying hydrogen at the fence, another making it inside — and report legitimately different numbers. A boundary is meaningful only once it is stated; an unstated boundary is the hidden assumption behind a levelized cost or a carbon intensity that two readers can each interpret a different, incompatible way.

Limits & typical error

The boundary is frequently the single largest lever on the headline number — larger than any choice inside it. Moving the boundary to include or exclude an upstream step restructures the whole cost or emissions stack rather than one line of it. For a process whose purchased feedstock dominates cost, whether that feedstock crosses the boundary as a purchase or is produced inside it can move the result by a large fraction of the levelized cost — plausibly tens of percent — more than refining any equipment size within the boundary would. The internal model can be identical and the answer still differ substantially purely from where the line is drawn.
Mismatched boundaries make two numbers non-comparable. A gate-to-gate cost or carbon intensity set beside a cradle-to-gate one compares unlike systems; the gap between them can be entirely a boundary artifact with no physical meaning. Side-by-side cost curves and “X is cheaper than Y” claims hold only when both figures share a boundary — and because the boundary is so often unstated, the mismatch routinely goes unnoticed.
A boundary drawn too narrowly silently truncates real costs and emissions. Costs and emissions occurring just outside the line do not disappear; they are simply uncounted. A gate-to-gate boundary that omits upstream feedstock production reports a cost and a carbon intensity that are real for the plant yet understate the delivered product’s true figure — the classic undercount of counting only what happens inside the fence.
The economic, physical, and carbon boundaries can diverge unnoticed. A common error is drawing the line in one place for cost (buying a feed across the fence) and another for emissions (counting, or not counting, that feed’s upstream carbon). When the three ledgers are not taken over the same control volume, the cost per unit and the carbon per unit describe different systems and cannot be combined or traded off coherently.
Cutting through a coupled loop leaves the crossing streams ill-defined. A boundary that slices a recycle loop, a heat-recovery loop, or a tightly coupled pair of operations creates “crossing” streams that are really internal — their flows are set by the loop the cut has split, not by the outside world. The balance cannot close cleanly at such a surface, and any cost assigned to the partial loop is arbitrary. Boundaries drawn at genuine breakpoints (a storage tank, a product specification, a site gate) avoid this; boundaries drawn mid-loop do not.
Shared boundaries invite double-counting or gaps. Where two analyses abut — one process’s product is another’s feed, or two products share a feedstock — the same stream can be counted in both systems or in neither, and a byproduct credit can be claimed on both sides of the shared line. The crossing must be booked exactly once, as a cost to one side and a revenue to the other, or the combined accounting is internally inconsistent.

Mini-example

Green ammonia makes the boundary’s leverage concrete. Hold the synthesis loop identical — H₂ and N₂ combined at roughly a 3:1 molar ratio, about 20% conversion per pass, ammonia condensed out and the unconverted gas recycled (the running-example baseline) — and draw the boundary two ways:

Gate-to-gate, around the synthesis plant only. Hydrogen and nitrogen cross the boundary inward as purchased feeds; ammonia crosses outward as product. The electrolyzer is outside the line and is never modeled — its hydrogen simply arrives at a contract price. The cost is then dominated by that purchased-hydrogen price, and the plant’s carbon intensity reflects only the synthesis step.
Power-to-ammonia, boundary pushed upstream to include electrolysis. Now electricity, water, and air cross inward; hydrogen no longer crosses at all, because it is produced inside. The electrolyzer becomes a modeled unit operation with its own equipment and power costs, and the dominant input cost shifts from hydrogen to electricity. The carbon intensity now inherits the grid’s carbon rather than a hydrogen supplier’s.

Same chemistry, same loop, two legitimately different costs per tonne of NH₃ and two different carbon intensities — the gap comes entirely from where the line was drawn, not from anything modeled inside it. (That hydrogen price dominates the first version and electricity price the second is the running example’s qualitative result; the actual cost shares are sourced figures, not assumed here.)

To show the edge, a separate one-line instance: draw the boundary through the synthesis recycle — cutting between reactor and separator — and the “crossing” stream is the large internal recycle, several times the fresh feed, whose flow is set by the very loop the cut has split; the balance cannot close there, so that surface is not a usable boundary.