Contents
Introduction
This Module describes requirements for Projects that use shared infrastructure for the transport and intermediate storage of CO2. Because the Project's CO2 may be commingled with that of other users and cannot be measured directly at the point of entry to durable storage, the Module uses a mass-balance approach anchored at the point of capture to allocates transit losses along each segment of the shared chain and return the quantity attributable to the Project. It also contains guidance on other key aspects of shared infrastructure usage including emissions allocation, chain of custody tracking, and measurement and reporting requirements.
Applicability
This Module applies to Carbon Dioxide Removal (CDR) or Reduction Projects that capture CO2 and store it within durable storage reservoirs, where any part of the transport, handling, conditioning, or intermediate storage of the CO2 occurs within shared infrastructure. It applies where the quantity attributable to the Project cannot be established by direct measurement or physical segregation alone.
In this instance, ‘shared infrastructure’ refers to any infrastructure for CO2 transport or intermediate storage that is simultaneously or sequentially used by other entities in a manner that results in physical commingling of CO₂ streams or otherwise prevents direct measurement of Project-attributable quantities. Other users may include other CDR projects, industrial users, or CO₂ utilisation chains (for example, enhanced oil recovery), whose CO₂ may be destined for end uses other than durable storage. The presence of this other CO₂ in the shared infrastructure does not preclude application of this Module, provided the quantity attributed to the Project is determined on a verifiable mass-balance basis and is not double-counted.
Examples of shared CO2 transport infrastructure include the following components of a CO2 transportation system, where any such components are shared with other users:
- Transportation methods such as CO2 pipelines, ships, trains, barges, and trucks;
- Intermediate storage vessels, such as tanks and buffer vessels;
- Associated processes between the boundaries of the capture plant and storage facility, such as liquefaction, regasification, and gas treatment; and
- Other equipment, such as compressors, pumps, and heat exchangers.
Shared infrastructure may be owned, operated or controlled by the Project Proponent, or by one or more third parties. A third-party operator may account for the CO2 it transports and stores using its own allocation procedures, reflecting how its infrastructure is instrumented and operated, and certain regulatory or contractual obligations. This Module does not prescribe a single such method, but outlines a number of principles on creating a verifiable mass-balance across complex transport chains, supported by measurements of reasonable accuracy. Where a Project relies on an operator's accounting to establish its stored quantity, that accounting must be consistent with the principles set out in this Module, so that the quantity attributed to the Project is determined on the same mass-balance basis, is not overstated, and that no quantity of CO₂ is attributed to more than one project, entity, or claim.
Scope
The scope of this Module includes the transport, handling, conditioning, and intermediate storage of CO2 between the boundaries of a Project’s CO2 capture location and its durable storage reservoir. Within this boundary, the Module quantifies the mass of the Project's CO2 delivered to the point of entry to durable storage, net of transit losses within the transport system, such as by venting, leakage or fugitive emissions (Section 6). It also sets out how the shared infrastructure’s emissions (embodied, transport, and energy-use) are allocated to the Project, segment by segment (Section 7).
This Module’s responsibility ends at the point of entry to durable storage reservoir(s), the custody transfer or measurement point at which the Project’s CO₂ leaves the transport system and enters the storage system governed by the applicable Storage Module. From that point, the applicable storage Module governs the quantification of the durably stored CO2, together with durability, risk of reversal, and monitoring requirements.
For guidance on broader aspects of carbon removal and reduction pathways involving CO2 capture and storage, refer to the relevant Protocol and its associated storage Modules.
Relation to the Isometric Standard
Ownership
Transport and intermediate storage of CO2 through shared infrastructure typically involves multiple parties, for example distinct operators for capture facilities, transport and intermediate storage, and storage sites. To avoid Double Counting, a single Project Proponent must be specified as the sole owner of the Certificates in contracts with each of these operators, in accordance with the Ownership Section of the Isometric Standard.
Project Design Document
R-X3Z1-0For a Project using shared CO2 transport infrastructure, the Project Design Document (PDD) must include a description of the shared transport system, including the transport methods, intermediate storage, and associated processes and equipment used, the durable storage destination(s), and the components that are shared with other users, and the division of the transport pathway into Transport Infrastructure Segments (Section 5), including the boundaries of each segment and the points at which segments are designated.
Further documentation that must be included in the PDD is specified in the Section to which it relates.
Transport Infrastructure Segments
Where a Project uses shared CO2 transport infrastructure, CO2 is conveyed to durable storage through a chain of transport and intermediate storage assets. These assets may be operated by different parties, and along the chain the Project's CO2 may be combined with, or separated from, CO2 belonging to other users.
To make the attribution of CO2 consistent and auditable, the transport pathway between the boundary of the Project's capture facility and the entry to its durable storage reservoir is divided into a series of Transport Infrastructure Segments. A Transport Infrastructure Segment is a portion of the transport pathway across which the mode of transport, the CO2 streams and the Project's share of them, and the operator, all remain unchanged.
The Transport Infrastructure Segment, designated according to Section 5.1, is the common unit of accounting for this Module. The Project's share of each segment (Section 5.2) is used to quantify the Project's CO2 losses, segment by segment (Section 6), and to allocate embodied, transport, and energy-use emissions to the Project (Section 7), so that losses and emissions are apportioned on a single, consistent basis. The chain of custody to a given storage reservoir is the continuous, unbroken sequence of Transport Infrastructure Segments connecting the capture facility to that reservoir (Section 8).
Designation of Segments
The Project Proponent must divide the transport pathway, from the boundary of the capture facility to the entry point of the durable storage reservoir(s), into Transport Infrastructure Segment, and document this in the PDD. A new Transport Infrastructure Segment must be designated:
- each time two or more CO2 streams are merged;
- each time a CO2 stream is separated into two or more streams that follow different pathways, for example, to different destinations, operators, or modes of transport;
- at each change in the mode of transport (for example, from pipeline to ship, or from ship to truck);
- at each change of operator, or handover of custody, between parties responsible for the infrastructure; and
- at additional points determined by the Project Proponent for operational clarity, in agreement with Isometric.
Dividing or combining a single Project’s CO₂ across multiple vehicles for the same movement (the same origin, destination, operator and mode of transport) does not by itself designate a new segment; such carriage is handled as discrete consignments within a single segment under the batch transfer-mode requirements (Section 8).
Where a portion of the transport pathway is operated by a third party, and the Project Proponent cannot resolve the internal segment structure from the data available, that portion may be designated as a single Transport Infrastructure Segment. The Project's share of that segment (), and the CO₂ losses attributed to it, are then taken from the operator's allocation procedure, subject to the conditions in Section 9.4.
Quantification of Stored CO2
Protocols using shared transport and storage infrastructure determine the net Removal or Reduction for a Reporting Period based on a quantity stored in one or more durable storage reservoir(s), .
Where a Project is the sole user of dedicated transport infrastructure, is measured directly at the point of entry to durable storage and attributed in full to the Project.
Where the Project's CO2 is commingled with that of other users in shared CO2 transport infrastructure so that it is no longer physically distinguishable, it cannot be measured at the point of entry to durable storage as a quantity attributable solely to the Project. In this case, the quantity of the Project's CO2 delivered to the point of entry to durable storage at each destination i is determined from the quantity it captures and the CO2 lost in transit to that destination:
(Equation 2)
(Equation 3)
Where:
- is the gross mass of the Project's CO2 delivered to the exit point of the final Transport Infrastructure Segment in the chain of custody (i.e. the handover to durable storage) i over the Reporting Period, net of transit losses, in tonnes.
- is the gross mass of the Project's CO2 captured over the Reporting Period, as determined by the applicable Protocol, in tonnes.
- is the Project's attributable CO2 losses within the transport system along the custody chain to reservoir i, quantified in accordance with Section 6.1, in tonnes.
- = the proportion of the Project's captured CO2 routed to durable storage reservoir i; equal to 1 where all of the Project's CO2 is routed to a single reservoir.
- = the number of durable storage reservoirs receiving the Project's CO2 in the Reporting Period.
Equation 2 is stated in gross CO2 mass (i.e. the full mass of CO2 handled regardless of its origin, whether biogenic, fossil, or atmospheric), consistent with the definition of in the applicable Storage Module. Where a Protocol applies a biogenic or eligibility fraction (for example, in the Bio-CCS Protocol), that fraction is applied by the Protocol to and is unaffected by this Module.
All quantities in Equation 2 are masses of CO2, determined as the mass of the conveyed fluid multiplied by its CO2 concentration, so that variation in CO2 concentration or purity along the transport chain is accounted for.
The quantity determined under Equation 2 is reconciled, for each Reporting Period, against the quantity confirmed as durably stored, and is treated conservatively where the two do not reconcile, in accordance with Section 9.2.
Quantification of CO2 Transit Losses
The Project's transit losses to the point of entry to durable storage are the sum, over the segments forming the custody chain to that reservoir, of the Project's attributable share of the CO2 lost from each segment:
(Equation 4)
Where:
- is the Project's share of the CO2 conveyed through segment s, determined in accordance with Section 5.2 (equal to 1 for a segment used exclusively by the Project).
- is the total mass of CO2 lost from segment s over the Reporting Period, in tonnes CO2e, determined in accordance with Section 6.1.1.
- is the proportion of the Project’s CO₂ passing through segment s that is routed to durable storage reservoir i, determined on the same basis as (Equation 2). It equals 1 where segment s lies on the custody chain to a single reservoir, and for a segment serving more than one reservoir.
- the summation is taken over all Transport Infrastructure Segments forming the custody chain to reservoir i.
Determination of Segment Losses
The loss from each Transport Infrastructure Segment, , must be determined by one of the two methods below. Direct mass balance (Method A) must be used wherever the segment-level inflow, outflow and inventory measurements it requires are available. Source-level determination (Method B) may be used only where those measurements are not available, or cannot be obtained without unreasonable cost, with the reason documented and the associated uncertainty propagated into the conservative estimate of net Removals or Reductions.
The Project Proponent must state the method selected for each segment, and the justification where Method B is used, in the Project Design Document (Section 4.3).
Method A: direct mass balance. The segment loss is the difference between the CO2 measured entering and leaving the segment, adjusted for any change in the CO2 held within the segment over the Reporting Period:
(Equation 5)
- is the mass of CO2 measured entering segment s over the Reporting Period, in tonnes CO2e, determined in accordance with the measurement requirements of Section 9.1.
- is the mass of CO2 measured leaving segment s over the Reporting Period, in tonnes CO2e, , determined in accordance with the measurement requirements of Section 9.1.
- is the change in the mass of CO2 held within segment s between the start and end of the Reporting Period (Section 6.1.2), in tonnes CO2e; equal to zero for a segment that holds no CO2 inventory.
Method B: source-level. The segment loss is the sum of the CO2 released from the segment by each loss mechanism:
(Equation 6)
Where each term is the mass of CO2 lost from segment s over the Reporting Period through fugitive emissions, venting, and leakage respectively, in tonnes CO2. Each term must be determined from direct measurement in accordance with the measurement requirements of Section 9.1 or, where direct measurement is not feasible, from representative loss factors specific to the infrastructure, equipment, or operating conditions of the segment.
Where a loss factor is used in place of direct measurement, it must be representative of the segment to which it is applied. The Project Proponent may use:
- Infrastructure- or equipment-specific factors: a loss factor specific to the infrastructure or equipment type used in the segment, for example manufacturer-certified fugitive emission rates for the pipeline material or vessel type in use, results from independent system-wide pressure-decay or leak testing of the segment, or values published in a recognised industry standard for that equipment or operating condition.
- Regional factors: a loss factor determined for the geographic area in which the segment operates, produced by a reputable source such as a pipeline or utility operator, a governmental body, or an independent research organisation. The segment must lie within the area for which the factor was determined.
Transport System Inventory
CO2 may be retained within the transport system at the start or end of a Reporting Period, for example as line-pack within a pipeline, or as heel, the residual CO2 retained in a transit vessel or intermediate storage tank after offloading. This retained CO2 is within the transport system but has not been lost, and has not yet been delivered to the reservoir.
The change in the mass of CO2 held within each segment over the Reporting Period, , must be accounted for in the segment mass balance (Equation 5), so that retained CO2 is not misclassified as a loss.
Where a segment is shared, any CO2 added to its inventory during the Reporting Period is allocated to the Project on the same basis as the segment's losses (, Section 5.2).
The mass of the Project's CO2 held within a segment at the close of a Reporting Period must be carried forward as the mass held at the start of the following Reporting Period, so that no CO2 is double-counted or omitted across the period boundary. This treatment must be consistent with the provisions for temporal delays in Section 9.3.
The Project Proponent must state the approach taken to quantifying retained CO2, including the treatment of heel and line-pack, in the PDD.
may be taken as zero for a segment that operates at materially the same pressure, temperature, and composition at the start and end of the Reporting Period, such that the mass of CO₂ it contains is not materially different, where this is justified for that Reporting Period.
Where the Project relies on a third-party operator's allocation procedure, the operator's tracking of retained CO₂, including any running per-user balance of commingled CO₂, may be accepted in place of a Project-determined .
Emissions Accounting
GHG emissions accounting for CO2 transport infrastructure must be carried out in accordance with the GHG Accounting Module and Energy Use Accounting Module. The following sections provide guidance on specific considerations for shared CO2 transport infrastructure.
Where the Project relies on a third-party operator's allocation procedure, the operator's allocation to the Project of energy, fuel, and associated emissions across shared infrastructure may be used, in agreement with Isometric. Where the operator does not disaggregate an emissions component to the level of the Transport Infrastructure Segment, that component may be allocated on a reasonable basis agreed with Isometric.
Embodied Emissions
Embodied emissions associated with shared CO2 transport infrastructure must be accounted for and amortized in accordance with the GHG Accounting Module, which provides for proportional allocation where infrastructure is shared among multiple users.
Where a Project's CO2 is transported through more than one Transport Infrastructure Segment (as defined in Section 5), the allocation of embodied emissions must be applied to each segment in turn.
For each shared segment, the allocation basis must use the sum of:
- the capacity it used, i.e. the mass of the Project's CO2 conveyed through the segment; and
- the capacity it reserved but did not use, to the extent that capacity was not taken up by another user (and not less than zero).
This share is measured against the segment's total design capacity. In effect, a Project bears a percentage of the total embodied emissions, based on capacity it used plus any capacity it reserved and left idle, but never capacity left idle by the operator, or reserved capacity that another user takes up.
This allocation and its amortization schedule must be reviewed and updated as the Project's use, its reserved capacity, and the segment's total design capacity become known, in accordance with the GHG Accounting Module.
Transportation Emissions
Where CO2 is transported by non-pipeline modes (such as truck, rail, or ship), the emissions from that transport must be accounted for in accordance with the GHG Accounting Module, including the emissions of any empty return legs (for example, counting the full round-trip distance where the vehicle returns unloaded). Energy use associated with pipeline transport and functionally connected infrastructure is accounted for under Section 7.3.
Where a transport movement is used exclusively by the Project, its transport emissions are attributed directly to the Project. movement is exclusive to the Project where the consignment carries only the Project’s CO₂, even where the same vehicle carries other Projects’ CO₂ on other movements; any residual heel from a previous user is treated as retained inventory under Section 6.1.2.
Where a movement is shared, such as in a shipment in which the Project's CO2 is one part of a larger total volume, the transport emissions must be allocated to the Project at the level of each Transport Infrastructure Segment (Section 5), on the same capacity-based allocation basis as described in Section 7.1.
This allocation must be reviewed and updated as the Project's use and its booked capacity become known.
Energy Use Accounting
Shared CO2 transport infrastructure consumes energy, including the electricity, fuel, and heat used by compressors and booster stations, liquefaction and regasification, heaters, pumps, and intermediate storage.
Where energy-consuming infrastructure is shared among multiple users, the associated energy emissions must be allocated to the Project at the level of each Transport Infrastructure Segment (Section 5), based on the mass of the Project's CO2 handled within the segment relative to the total mass of CO2 handled within it, or by another justifiable allocation basis that more accurately reflects the Project's energy use (for example, where CO₂ streams enter the segment at different pressures and impose materially different compression requirements), subject to verification and consistent with the Energy Use Accounting Module.
Direct emissions from non-pipeline transport (truck, rail, or ship) are accounted for under Section 7.2.
Chain of Custody
The Project Proponent must maintain an unbroken and auditable chain of custody for the Project's CO2, from the point at which the Project assumes custody at the boundary of the capture facility through to the point at which the CO2 enters the durable storage reservoir.
Within shared infrastructure, the Project's CO2 may be kept physically separate from, or commingled with, CO2 from other sources, including where residual CO2 from a prior user is retained in a sequentially-used asset. The Project Proponent must identify, for each Transport Infrastructure Segment, which of the following applies:
Table 1. Chain of Custody Evidence Requirements
Transfer mode | Description | Custody evidence |
|---|---|---|
Batch | CO2 moved as discrete consignments (e.g. by truck, rail, or ship) | Each consignment assigned a unique identifier and documented on a per-consignment basis (e.g. bill of lading and metering or weighbridge records), recording the mass and CO2 concentration on dispatch and on receipt |
Continuous | CO2 moved as a continuous flow (e.g. by pipeline) | Continuous metering at the relevant segment boundaries, reconciled by mass balance over the Reporting Period |
Where a segment is operated by a third party, the Project Proponent must obtain the custody and transfer records for that segment, or arrange for the operator to provide them, in accordance with Section 9.4.
The chain of custody terminates where the Project's CO2 enters the durable storage reservoir. A storage confirmation from a third party storage provider evidences that the Project's CO2 was durably stored and closes the custody chain. The mass certified as stored is reconciled according to Section 9.2.
At Validation, the Project Proponent must document in the PDD, for each Transport Infrastructure Segment, the procedure for recording and reconciling CO2 mass and concentration at each point of transfer, consistent with the requirements for the relevant transfer mode, outlined above.
At Verification, the Project Proponent must provide the custody and transfer records for the Reporting Period.
Monitoring Requirements
Measurement of CO2
At each Transport Infrastructure Segment, the Project Proponent must identify the methods of measuring the mass and concentration of CO2, whether by the Project Proponent or the operator, to determine the segment's CO2 losses (Section 6.1) and to allocate project emissions between the users of that segment (Section 7). The required measurement approach depends on whether the segment uses continuous or batch transfer.
Metering Requirements
For segments with continuous flow (pipeline and other continuously-metered segments), the Project Proponent must confirm that:
- there is continuous CO₂ mass flow is continuously metered at the entry and exit of each segment; and
- CO₂ concentration is measured at each point where the CO₂ composition may change, including each point where the Project’s CO₂ is commingled with a stream of different composition, and any process that alters composition (such as treatment, conditioning, or a change of phase). A measured CO₂ concentration may be carried forward and applied to the metered mass across segments where the CO₂ composition does not materially change, including separations, changes of transport mode, and changes of operator, where the Project Proponent justifies this in the PDD.
For each consignment into a batch system (such as road, rail, or water), the Project Proponent must record the measured mass and CO2 concentration at loading and at receipt, reconciled against the preceding record:
- Mass of each consignment must be determined by one of: a legal-for-trade weighbridge or platform scale; calibrated static tank gauging using level, temperature and pressure together with a validated equation of state appropriate to the non-ideal behaviour of CO₂ at the relevant composition; or a calibrated mass or volumetric flow meter on the transfer line.
- CO2 concentration of each consignment must be determined by either a continuous inline analyzer meeting the requirements below, or, where inline analysis is impractical for discrete consignments, laboratory analysis of a representative sample drawn in accordance with a recognized sampling standard.
Metering instruments and analysis methods used under either transfer mode must meet the following requirements, consistent with the requirements applied at the capture facility and the storage reservoir under the applicable Protocol and Storage Module:
- for mass or flow metering and weighing instruments, have an accuracy of 2% of the measured value, or better, across the observed operating range; and for CO₂ concentration analysers, have an accuracy of 2% of full scale, or better;
- be calibrated at a frequency that meets or exceeds manufacturer requirements, and in any case at least annually; and
- be traceable to national standards.
A Project's transport chain may involve many measurement points across several segments, operated by different parties and built to different measurement specifications.
Where a segment is operated by a third party whose metering is installed to a different recognized specification, such as a custody-transfer or fiscal-metering standard, that specification may be accepted, in agreement with Isometric.
Where a pre-existing measurement point operated by a third party cannot meet the requirements, nor be accepted under an alternative recognized specification, the Project Proponent must document that point's measurement uncertainty and propagate it into the conservative estimate of net removals in accordance with the Uncertainty section of the Isometric Standard.
The loading and receipt records for a consignment are treated as reconciled where they agree to within their combined measurement uncertainty and the change in in-system inventory over the transfer (including heel and line-pack). A consignment whose records diverge beyond this tolerance must be handled as a measurement discrepancy under Section 9.1.3.
Where a consignment passes through intermediate storage, the Project Proponent must reconcile inventory before and after (tank level, pressure and temperature), stating the minimum heel and line-pack assumptions applied.
Measurement Discrepancies
At Verification, for each Reporting Period, the Project Proponent must provide a record of any discrepancy between the start-point and end-point measurements for each segment that exceeds their combined measurement uncertainty and the change in in-system inventory, together with the investigation of its cause, and evidence of any notification made to Isometric where the discrepancy was material.
Measurement Reconciliation
For each Reporting Period, the quantity of determined under Section 6 must be reconciled against the quantity confirmed as durably stored by the storage operator. The form this confirmation takes is determined by the applicable Storage Module.
This reconciliation operates over the Reporting Period across the whole transport chain, in addition to the per-transfer reconciliation under Section 9.1.1.
The two quantities are treated as reconciled where the difference between them falls within their combined measurement uncertainty and any change in the CO2 held within the transport system (in transit, as line-pack, or as retained heel) between the start and end of the Reporting Period.
Where the difference exceeds what measurement uncertainty and the change in in-system inventory can account for, the Project Proponent must investigate and document the cause. The quantity credited for the Reporting Period (Section 6, Equation 2) will be reduced to the lower of the capture-derived quantity and the quantity confirmed as durably stored.
At Verification, for each Reporting Period, the Project Proponent must provide the reconciliation of the capture-derived quantity against the storage confirmation and the quantified transit losses, together with, for any difference exceeding the combined measurement uncertainty and in-system inventory change, the investigation of its cause, the conservative quantity applied, and evidence of any notification made to Isometric where the difference was material.
Temporal Delays
Where CO2 is transported and intermediately stored through shared infrastructure, there may be a delay between the point at which CO2 is captured within a Reporting Period and the point at which it enters durable storage, so that a specific quantity of captured CO2, and its associated transit losses, cannot always be matched to the time it enters storage.
Where this matching is not possible, the Project Proponent may instead estimate, on the basis of the average per tonne of CO2 handled during the Reporting Period:
- CO2 losses within the transport system (as quantified under Section 6); and
- Emissions associated with transport and intermediate storage (as accounted for under Section 7).
The per-tonne average must be derived such CO2 losses and emissions are not understated.
At Validation, where the Project intends to use this per-tonne average basis, the Project Proponent must document the approach in the PDD, including the basis on which the per-tonne average is derived and why it is representative and conservative.
Data Reporting and Availability
The Project Proponent remains responsible for providing all data required to quantify and verify the Project's Removals or Reductions, CO2 losses, and emissions across every Transport Infrastructure Segment, including segments operated by third parties, in accordance with the Ownership section of the Isometric Standard.
Where a third-party operator reports the mass of CO2 handled on a periodic basis, for example a monthly certificate of the quantity of the Project's CO2 received into the operator's transport or storage system, this documentation may be used as the segment-boundary measurement for the custody-transfer point to which it relates. The documentation must state the Reporting Period, the mass and the CO2 concentration or purity basis of the quantity certified, and the metering standard on which it is based.
Data underlying the quantification is published in accordance with the Data Sharing requirements of the Isometric Standard.
Third-Party Allocation Procedures
Where shared infrastructure is operated by a third party, the Project Proponent may rely on the operator's allocation procedure to determine the quantity of the Project's CO₂ delivered to the point of entry to durable storage, together with its attributable transit losses and emissions. It may do so in place of determining these from segment measurements it holds directly.
Where the allocation procedure has already been verified by an independent third party, those reports may form part of the evidence, provided they are shared with the VVB.
At Validation, the Project Proponent must include in the Project Design Document:
-
G-Z6E8-0a summary of the operator's allocation procedure, sufficient to demonstrate that the quantity attributable to the Project is not overstated, including:
- the measurement points used;
- how the Project's share of the CO2 is derived from them, including any per-user balance maintained; and
- how losses are allocated across system users; and
- whether the procedure has already been independently verified or certified.
-
G-JV9X-0the arrangements for obtaining the evidence needed to verify the operator's allocation, including the agreements in place to examine the operator's underlying records, whether through continuous access or on a periodic spot-check or sample basis.
The operator's reporting may also be used to allocate energy, fuel, and embodied emissions to the Project (Section 7). Where the Project relies on the operator for any of these allocations, the Project. Proponent must outline in the PDD:
- the allocation of energy and fuel use to the Project across the shared infrastructure, as provided by the operator, and its consistency with the Energy Use Accounting Module ;
- the allocation of embodied emissions to the Project, as provided by the operator, such as an existing life-cycle assessment of the infrastructure — and its consistency with the GHG Accounting Module;
At Verification, for each Reporting Period, the Project Proponent must provide the evidence needed for the VVB to confirm that the procedure has been applied as documented, including:
- the operator's allocation report for the Reporting Period;
- any data used to verify the allocation, which may be relevant metering data, where available, and/or the results of any spot-check examination of the underlying records; and
- a log of any data gaps and the conservative treatment applied.
Data Gaps
Because shared transport relies on third-party operators, there is a risk of gaps arising in the data needed for quantification. Where a data gap occurs, the following requirements apply:
- the Project Proponent must apply a documented and conservative procedure to substitute or estimate the affected parameter such that the credited quantity of stored CO2 is not overstated;
- the substitute value must be derived from validated support data, for example a mass-balance reconciliation across the segment, custody-transfer or billing records, or measurement at an adjacent metering point;
- the resulting uncertainty must be carried through in accordance with the Uncertainty Accounting Section of the Isometric Standard. Each gap, its duration, and the substitution method used must be logged and disclosed at Verification.
As soon as it becomes apparent to the Project Proponent that a data gap has arisen or is likely to arise, the Project Proponent must notify Isometric without undue delay, so that the approach to handling it can be agreed ahead of Verification.
At Validation, the Project Proponent must assess in the PDD the risk of data gaps arising in shared transport, and document the conservative gap-handling procedure to address them.
At Verification, for each Reporting Period, the Project Proponent must provide a log of any data gaps and the substitution or reconstruction applied, and evidence of any advance notification made to Isometric.
Definitions
- AmortizationThe term used to describe allocation of Project emissions to multiple Removals or Reductions.
- AssetAny tangible or intangible property that has value and can be owned, controlled or utilized by an individual or organization. In the context of this module, an asset refers to a physical structure.
- Carbon Dioxide Removal (CDR)Activities that remove carbon dioxide (CO₂) from the atmosphere and store it in products or geological, terrestrial, and oceanic Reservoirs. CDR includes the enhancement of biological or geochemical sinks and direct air capture (DAC) and storage, but excludes natural CO₂ uptake not directly caused by human intervention.
- ConservativePurposefully erring on the side of caution under conditions of Uncertainty by choosing input parameter values that will result in a lower net CO₂ Removal or GHG Reduction than if using the median input values. This is done to increase the likelihood that a given Removal or Reduction calculation is an underestimation rather than an overestimation.
- Direct EmissionsEmissions that are produced by a specific CDR process and are directly controllable.
- Double CountingImproperly allocating the same Removal or Reduction from a Project Proponent more than once to multiple Buyers.
- DurabilityThe amount of time carbon removed from the atmosphere by an intervention – for example, a CDR project – is expected to reside in a given Reservoir, taking into account both physical risks and socioeconomic constructs (such as contracts) to protect the Reservoir in question.
- Embodied EmissionsLife cycle GHG emissions associated with production of materials, transportation, and construction or other processes for goods or buildings.
- EmissionsThe term used to describe greenhouse gas emissions to the atmosphere as a result of Project activities.
- LeakageThe increase in GHG emissions outside the geographic or temporal boundary of a project that results from that project's activities.
- ModuleIndependent components of Isometric Certified Protocols which are transferable between and applicable to different Protocols.
- PathwayA collection of Removal or Reduction processes that have mechanisms in common.
- ProjectAn activity or process or group of activities or processes that alter the condition of a Baseline and leads to Removals or Reductions.
- Project Design Document (PDD)The document that clearly outlines how a Project will generate rigorously quantifiable Additional high-quality Removals or Reductions.
- Project ProponentThe organization that develops and/or has overall legal ownership or control of a Removal or Reduction Project.
- ProtocolA document that describes how to quantitatively assess the net amount of CO₂ removed by a process. To Isometric, a Protocol is specific to a Project Proponent's process and comprised of Modules representing the Carbon Fluxes involved in the CDR process. A Protocol measures the full carbon impact of a process against the Baseline of it not occurring.
- ReductionThe term used to represent the reduction of greenhouse gasses emitted into the atmosphere from an existing emitter as a result of an emission reduction process.
- RemovalThe term used to represent the CO₂ taken out of the atmosphere as a result of a CDR process.
- Reputable SourceA source that would be widely considered trustworthy based on the process undertaken (e.g., peer review) or origin of the information (e.g., government body).
- ReservoirA location where carbon is stored. This can be via physical barriers (such as geological formations) or through partitioning based on chemical or biological processes (such as mineralization or photosynthesis).
- ReversalThe escape of CO₂ to the atmosphere after it has been stored, and after a Certificate has been Issued. A Reversal is classified as avoidable if a Project Proponent has influence or control over it and it likely could have been averted through application of reasonable risk mitigation measures. Any other Reversals will be classified as unavoidable.
- SourceAny process or activity that releases a greenhouse gas, an aerosol, or a precursor of a greenhouse gas into the atmosphere.
- StorageDescribes the addition of carbon dioxide removed from the atmosphere to a reservoir, which serves as its ultimate destination. This is also referred to as “sequestration”.
- Transport Infrastructure SegmentA discrete portion of a CO₂ transport pathway, bounded by documented measurement points, across which the mode of transport, the operator, and the allocation of CO₂ streams between users remain unchanged.
- UncertaintyA lack of knowledge of the exact greenhouse gas impact (removal, reduction, or avoidance) associated with a particular process or Environmental Attribute. Uncertainty may be quantified using probability distributions, confidence intervals, or variance estimates.
- Validation and Verification Bodies (VVBs)Third-party auditing organizations that are experts in their sector and used to determine if a project conforms to the rules, regulations, and standards set out by a governing body. A VVB must be approved by Isometric prior to conducting validation and verification.
- VerificationA process for evaluating and confirming the net Removals and Reductions for a Project, using data and information collected from the Project and assessing conformity with the criteria set forth in the Isometric Standard and the Protocol by which it is governed. Verification must be completed by an Isometric approved third-party (VVB).
Contributors
