TariffShark Tiger User Guide
Not your version?
Filed Tariff Record Version
A Filed Tariff Record Version (FTRV) represents a Tariff Record Version (TRV) in a Filing. When a TRV is placed into a Filing, the result is the creation of an FTRV.
Record Change Type
When a TRV is in a Filing, it is there for a reason ... and that reason is known as a Record Change Type. The valid Record Change Type appear below, each with further explanation:
| Record Change Type | Details |
|---|---|
| New | When a Tariff Record is being filed with FERC for the very first time, such as might be the case when adding a section to a Tariff, the Record Change Type is "New". When the first TRV under a Tariff Record is being added to a Filing, TariffShark defaults the Record Change Type to "New". |
| Change | When filing an update to the language of a tariff section, which is probably the most common type of eTariff submittal, the Record Change Type is "Change". As subsequent TRVs under a Tariff Record are being added to a Filing, TariffShark defaults the Record Change Type to "Change". |
| Cancel | When filing to remove a Tariff Record from a Tariff or to remove an entire Tariff, the Record Change Type is "Cancel". |
| Withdraw | When filing to withdraw an FTRV that was previously filed, the Record Change Type is "Withdraw". |
| Pro Forma | When filing a preliminary change to one's Tariff without invoking statutory processing timelines, the Record Change type is "Pro Forma". |
FERC Response
An FTRV can be thought of as a proposal to FERC to affect a change in one's tariff. The status of such a change is called the "FERC Response". FERC Response, therefore, is a very important piece of FTRV data. TariffShark supports several FERC Response Values (defined below) and the ones that are valid for a given situation depend upon the Record Change Type. For example, it is not possible to assign a FERC Response of "Effective" to an FTRV that was submitted to FERC with a Record Change Type of "Pro Forma" because such a request is not an official proposal before the commission.
Each of the following FERC Response values is linked to the Glossary where you will find a detailed description.
- Accepted
- Approved Subject to Conditions
- Conditionally Accepted
- Conditionally Effective
- Draft
- Effective
- Overtaken by Events
- Pending
- Pending Tolled
- Pro Forma
- Rejected
- Retired
- Superseded
- Suspended
- Withdrawn
Effective Dates in TariffShark
There are three separate effective date fields in TariffShark. Two of these are stored in the database and the other is calculated (or derived) by the TariffShark software for display.
| Effective Date | Details |
|---|---|
| Proposed Effective Date | The Proposed Effective Date is the one you enter when you place a Tariff Record Version into a Filing. This is the date that is sent to FERC in the XML. This date is stored in TariffShark as a Filed Tariff Record Version (FTRV) data element. |
| FERC Effective Date | The FERC Effective Date is the one approved by FERC. This information is often included in a FERC order. However, it can also be inferred depending on the FERC program (gas, oil, electric) and the circumstances surrounding the filing (for example, oil tariffs typically go into effect 30 days after filing without the issuance of a FERC order). This date is stored in TariffShark as an FTRV data element. |
| Effective Date | The Effective Date, which appears in several grids in TariffShark, is a computed date. It takes into consideration the FTRV's FERC Response and displays either the Proposed Effective Date or the FERC Effective date. The "Effective Date" field is perhaps most frequently seen in the Tariff Record Versions grid on the Filing Details form. |
In TariffShark Hammerhead Release 4.0.x and earlier, the rules for computing "Effective Date" are ...
- If the FERC Response of the FTRV is Approved Subject to Conditions, Pending, Rejected, Draft, Overtaken by Events, Pro Forma, or Withdrawn, the Proposed Effective Date is used.
- If the FERC Response of the FTRV is Accepted, Effective, Suspended, or Retired, the FERC Effective Date is used. If the FERC Effective Date is empty, however, the Proposed Effective Date is used.
The rules for computing "Effective Date" in TariffShark Hammerhead SP1 Release 4.1 and later are ...
- If the FERC Response of the FTRV is Pending, Rejected, Draft, Overtaken by Events, Pro Forma, or Withdrawn, the Proposed Effective Date is used.
- If the FERC Response of the FTRV is Accepted, Approved Subject to Conditions, Effective, Suspended, or Retired, the FERC Effective Date is used. If the FERC Effective Date is empty, however, the Proposed Effective Date is used.
Effective Priority
As an FTRV is a proposal to FERC to affect a change in one's tariff on some effective date, sometimes multiple proposals are made via different TRVs under the same Tariff Record each requesting the same effective date. (This is common when making compliance filings against earlier statutory filings.) Under these circumstances, the filer must indicate to FERC which among the FTRVs requesting the same effective date is the most important. This is done by setting the "effective priority". TariffShark displays the Set Effective Priority command when it detects such situations.
Multiple Effective Dates
Throughout TariffShark there are screens that display TRV information in grids. When FTRV information in such a grid appears as "<multiple>", it means that the TRV exists in multiple Filings (put differently, there are multiple FTRVs for the TRV). Use the Tariff Record's Details command to view the full history of all activity under a Tariff Record.
Related Elements
- A Filed Tariff Record Version represents one Tariff Record Version's participation in a Filing.
See Also
FORMS
- Remove Filed Tariff Record Version from Filing
- Filed Tariff Record Version Details
- Set Effective Priority
- Update Filed Tariff Record Version
- Withdraw Filed Tariff Record Version