06.08.2013 Views

Regulation of Fuels and Fuel Additives: Renewable Fuel Standard ...

Regulation of Fuels and Fuel Additives: Renewable Fuel Standard ...

Regulation of Fuels and Fuel Additives: Renewable Fuel Standard ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

producer would need to report the volumes that were not assigned a RIN to the EPA in its<br />

annual RFS report, along with the connection to exports, in order to demonstrate that<br />

RINs were legitimately not assigned to these batches. We request comment on these<br />

special-case approaches to exported renewable fuels.<br />

As described in Section III.D.2, there are cases in which there is not a one-to-one<br />

correspondence between gallons in a batch <strong>of</strong> renewable fuel <strong>and</strong> the RINs generated for that<br />

batch. For instance, extra-value RINs can be generated in cases where the Equivalence<br />

Value is greater than 1.0. If the RVO assigned to the exporter were based strictly on the<br />

actual volume <strong>of</strong> the exported product, it would not capture the extra-value RINs which<br />

generally are not assigned to batches. Thus we propose that the RVO assigned to an exporter<br />

be based not on the actual volume <strong>of</strong> renewable fuel exported, but rather on a volume<br />

adjusted by the Equivalence Value assigned to each batch. The Equivalence Value is<br />

represented by the RR code within the RIN as described in Section III.D.2.a. Thus the<br />

exporter would multiply the actual volume <strong>of</strong> a batch by that batch's Equivalence Value to<br />

obtain the volume used to calculate the RVO.<br />

In cases wherein an exporter obtains a batch <strong>of</strong> renewable fuel whose RIN has already<br />

been separated by an obligated party or blender, the exporter may not know the Equivalence<br />

Value. We propose that for such cases the exporter simply use the actual volume <strong>of</strong> the batch<br />

to calculate its RVO. This will introduce some small error into the calculation <strong>of</strong> the RVO<br />

for cases in which the renewable fuel had in fact been assigned an Equivalence Value greater<br />

than 1.0. However, we believe that the potential impact <strong>of</strong> this error would be exceedingly<br />

small. We request comment on our proposed approach to exporters <strong>of</strong> renewable fuel <strong>and</strong><br />

any alternative approaches that could ensure that production volumes <strong>of</strong> renewable fuel can<br />

be used as an accurate surrogate for consumed volumes.<br />

5. How Would The Agency Verify Compliance?<br />

The primary means through which the Agency would verify an obligated party's<br />

compliance with its RVO would be the annual reports. These reports would include a variety<br />

<strong>of</strong> information required for compliance <strong>and</strong> enforcement, including the demonstration <strong>of</strong><br />

compliance with the previous calendar year's RVO, a list all transactions involving RINs, <strong>and</strong><br />

the tabulation <strong>of</strong> the total number <strong>of</strong> RINs owned, used for compliance, transferred, retired<br />

<strong>and</strong> expired. Reporting requirements for obligated <strong>and</strong> non-obligated parties are covered in<br />

detail in Section IV.<br />

In its annual reports, an obligated party would be required to include a list <strong>of</strong> all RINs<br />

held as <strong>of</strong> the reporting date, divided into a number <strong>of</strong> categories. For instance, a distinction<br />

would be made between current-year RINs <strong>and</strong> previous-year RINs as follows:<br />

Current-year RINs: RINs that came into existence during the calendar year<br />

for which the report is demonstrating compliance.<br />

- 82 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!