TEA Handbook

Concept

structural

System boundary

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

Everything crossing is an input, an output, or an emission. Inside the closed control surface, operations are modeled in detail; outside enters only through the streams that cross. Inward is a feed taken as given — a feedstock or energy cost; outward is a product or byproduct carrying revenue or a credit, or a waste/emission. Nothing wholly inside appears in the external accounting. The same region is the control volume for a mass balance (in = out + accumulation, zero at steady state) — physical, cost, and emissions ledgers all kept over it.

Where it’s placed — and that it’s a choice. Boundaries nest: a unit operation; the process units; the whole plant (“gate-to-gate”); “cradle-to-gate,” reaching upstream to producing the feedstocks and energy; “cradle-to-grave,” through use and end-of-life. Each step outward turns a purchased input into an internally-produced stream. Where the line falls is chosen, not given: one analysis buys hydrogen at the fence, another makes it inside, and both report legitimately different numbers. It’s distinct from the battery limits (the narrower on-site capital fence); an unstated boundary is the hidden assumption behind a levelized cost or a carbon-intensity figure.

Limits & typical error

See also

  • Mass balance — the conservation check over the boundary as control volume.
  • Accounting (capex, opex & revenue) — the cost ledger for the inputs and outputs that cross the line, including the narrower ISBL/OSBL capital fence.
  • Levelized cost — the headline cost whose meaning depends on the “gate.”