Category: FERC

FERC Posts Updated eTariff Filing Types

On October 11, 2013, FERC issued a notice of changes to filing types that affect NGPA 311 Gas Pipelines. The specific changes are described thoroughly in the notice and go into effect on November 12, 2013.

We are updating TariffShark to be compliant with the changes and will notify our customers when the update is available for download.

Though omitted from the notice, we discovered that several other changes had been included in the updated Type of Filing CSV file that FERC posts on its eTariff webpage.  The unnoticed changes affect Oil Pipelines, go into effect on November 12, 2013, and are summarized below.

TOFC (Code) Filing Title Filing Category Description of Change
830 Rate Changes, Initial Rates & Other Tariff Changes Normal Citation updated
870 Cancellation of Tariff (partial) Normal Citation updated
970 New company tariff (Baseline) New Citation updated
1230 Amendment Amendment New filing type
1250 Concurrence Normal New filing type

We are updating TariffShark with these Oil program changes at the same time as we accommodate the changes for NGPA 311 Gas Pipelines.  We will blog again when the software update is available.

In the meantime, if you have any questions, please contact our support team.

Diagnose Problems Submitting to FERC’s eTariff Sandbox

In an earlier blog article, we described a method for submitting a tariff filing to FERC’s eTariff sandbox, which is helpful for users who don’t have TariffShark Hammerhead.  We also posted a screencast that shows how TariffShark Hammerhead has built-in FERC sandbox submission.  The purpose of this article is to help you diagnose why your computer may not be able to successfully submit a filing to FERC’s eTariff sandbox.

FERC’s eTariff sandbox is an FTP server.  FTP is an acronym for File Transfer Protocol, which provides a means for sending and receiving files over the Internet.  Some organizations have configured their corporate networks to block FTP, which also blocks the FERC eTariff sandbox.  In addition, some desktop computers are configured to run a software firewall.  A software firewall could also be blocking FTP.

When we are asked to diagnose problems sending files to FERC’s eTariff sandbox, we try to isolate the root cause.  One trick is to eliminate as many layers of software as possible, which we do by following this handy guide:

Use Windows command prompt to connect to FERC’s eTariff sandbox
[click to enlarge]

If a user is able to connect to FERC’s eTariff sandbox using the procedure above, then the problem is not one of blocked access and we will continue to dig deeper.

If you have questions about using FERC’s eTariff sandbox or run into problems trying to submit a filing to the sandbox, we’d love to hear from you.  Please comment below or contact TariffShark Support.

FERC Posts Updated Validation Error Codes

On February 11, 2013, FERC staff posted a small update to the list of Validation Error Codes that the Commission provides on its eTariff webpage.  The changes are summarized below.

The most significant change was to error code 120 which used to read “For an Amendment Compliance Withdrawn or Motion filing Associated Filing Identifier cannot be a Report Withdraw or Motion filing” and now reads “For an Amendment Compliance Withdraw Report or Motion filing Associated Filing Identifier cannot be a Report Withdraw or Motion filing”.  Essentially, the Commission is clarifying that a Report-type filing (note the highlighted word) may not be associated with a Report-type, Withdraw-type, or Motion-type filing.

Mistakenly, error code 158’s description was a copy of 159.  Error code 158 has been corrected to read “If provided the tariff record’s Record Binary Data RTF file is not well-formatted”.

Finally, a typographical error was corrected in the description of error code 121.

If you have any questions relating to these changes or to Validation Error Codes in general, you may post them below or contact TariffShark Support.

Waiving FERC Attachments

The Federal Energy Regulatory Commission (“FERC”) provides sets of rules that describe the types of eTariff filings and the supporting materials (FERC Attachments) that may be submitted for each type of filing. Separate sets of rules are provided for each FERC program (gas, oil, electric) which are aligned with the governing regulations. TariffShark incorporates and enforces these rules to help ensure a pain-free eTariff experience. For those interested, FERC provides a human-readable PDF that spells out the rules in some detail.

With that brief background out of the way, let’s dive into today’s topic: the waiving of FERC Attachments in eTariff.

Years ago, when eTariff was conceived, FERC staff set out to define the types of filings and associated attachments in a way that they closely mirrored the regulations. Specifically, for a given type of eTariff filing, the regulations describe which attachments are required and which are optional. FERC staff felt that defining the rules to parallel the regulations would help filers to understand the filing requirements and result in fewer rejected filings. Also, among the required attachments, a waiver may be requested under certain circumstances which would permit an eTariff filer to omit a required attachment. Another reason that a waiver might be requested for a specific attachment is when a filer chooses to include mandatory supporting material within another attachment, such as the transmittal letter. For example, when proposing changes to tariff language, it is necessary to provide a transmittal letter, the marked tariff changes, and a clean copy of the affected portions of the revised tariff. A filer could choose to provide three separate attachments or combine all three into the transmittal letter.

FERC staff’s intent caused something of an outcry from industry members. Some felt that it would be burdensome to provide a transmittal letter that included all required materials and to also request a waiver of those materials as separate attachments (on account of them being provided within the transmittal letter). In the end, FERC staff deferred to industries’ concerns.

So, while eTariff’s type of filing and attachment rules are capable of defining mandatory versus optional attachments and designating for which among the mandatory attachments a waiver may be requested, the rules have been implemented in a much simpler way. Across FERC programs, across all types of filings, transmittal letters are the only mandatory attachments and they are defined such that they cannot be waived. Therefore, while TariffShark supports the notion of requesting waivers for mandatory attachments, FERC’s type of filing and attachment rules do not define any such attachments, so you will not see this functionality within TariffShark. Further, this “dumbing down” of the rules places a greater burden on eTariff filers to be familiar with the regulations and to understand which attachments are required and which are optional for various eTariff filing scenarios.