From time to time, TariffShark may struggle to process a Tariff Record Version (TRV) document. When a TRV has failed document processing, the Failed Processing tab on the Dashboard will appear pinkish.
The rightmost column, titled Action in the image above, contains two buttons, Requeue and View, that can help you to complete processing of the TRV document.
Click the Requeue button to resubmit the TRV for document processing. This action essentially moves the TRV from the Dashboard’s Failed Processing tab over to its Processing Queue tab. If TariffShark is still unable to process the TRV’s content, it will turn up on the Failed Processing tab once again. If this happens, try the View button (described below).
Click the View button to open the marked content of the TRV that failed processing. The document will open in Microsoft Word.
TariffShark is often unable to process documents that contain section breaks. If your document contains section breaks, follow these steps to resolve:
- Using Microsoft Word, find and remove all section breaks (often times it’s best to replace them with page breaks).
- Save the document to your computer or network.
- Use the Build Content command for the TRV in TariffShark to import the document that you saved in the prior step.
If TariffShark still cannot process the document, let the TariffShark Support team help. If the TRV’s content isn’t confidential, please share the document with Support. To do so, click the View button in TariffShark’s Dashboard, save the document, and send it to support.
After submitting an eTariff filing and before FERC takes action on it, you may withdraw the entire proceeding by submitting a withdrawal-type filing. In this article I will describe the characteristics a withdrawal-type filing and outline the steps to take in TariffShark in order to prepare one.
Withdrawal-Type Filing Characteristics
The purpose of a withdrawal-type filing is to withdraw an entire proceeding before FERC has taken action on it. In order to indicate to the Commission which proceeding is being withdrawn, a withdrawal-type filing must be associated with an earlier, already-submitted eTariff filing. Also, a withdrawal-type filing does not propose changes to tariff language, therefore, it will never contain Tariff Record Versions or FTRVs. Finally, like all other eTariff filing types, a withdrawal-type filing must include a Transmittal Letter which describes the nature of the submittal.
How to Prepare a Withdrawal-Type Filing
Follow the steps below to prepare a withdrawal-type filing. The list is intentionally brief and does not go into great detail. If you have questions about the procedure, contact TariffShark Support.
- Create a withdrawal-type filing. The type of filing code to use depends on the FERC Program to which your company belongs. At the time of this writing, these are the FERC Programs and withdrawal-type filing codes.
Federal Power Act Electric (Market Based Rate) Public Utilities
100 Withdraw Entire Proceeding
Federal Power Act Electric (Traditional Cost of Service and Market Based Rates) Public Utilities
90 Withdraw Entire Proceeding
1060 Non-Jurisdictional Withdraw
NGA Gas Pipelines
NGPA 311 Gas Pipelines
810 Withdrawal of entire filing
900 Withdraw of Pending/Non-effective Tariff
110 Withdraw Non-Jurisdictional Filings
470 Withdraw (All PMA EFs)
- On the Update Filing window, enter the Validation Email address. For the Associated Filing field, click the ellipsis button and select the already-submitted filing you propose to withdraw.
- On the Filing Details window, on the FERC Attachments tab, update the Transmittal Letter attachment by uploading your transmittal letter.
At this point, the filing is ready to go. You may wish to Validate it in TariffShark before downloading the XML and submitting the filing.
TariffShark databases tend to grow larger and larger over time. If you think about it, this makes perfect sense. Each time an eTariff filing is made, Tariff Record Versions are added as are the filing’s FERC Attachments. Data is constantly being added to a TariffShark database and seldom deleted.
As the size of a database grows, so does the cost of maintaining it. The files that comprise the database require more space on disk and its backups run longer and also require more storage. Therefore, it may be wise to take any steps available to reduce database size. In a TariffShark database, there are opportunities for size reduction, which by and large come from tables in the database that store transient or audit data.
- Audit – All interactions between a TariffShark client and the application server are written to an audit table. The audit table can grow quite large over time. Records in the audit table are seldom if ever needed, but can be helpful when tracking down software issues. In any event, data in the audit table older than a few weeks provides no value.
- TRV Processing Queue – The Tariff Record Version processing queue is used to track and manage the processing of all TRV documents. This is truly transient data in that after a TRV document is processed successfully, the queue data is no longer needed.
- Binary Data – TariffShark stores binary data (Word documents and PDFs, for example) separately from other TariffShark data and seldom deletes table rows that are no longer needed. Over time, unneeded documents can take up quite a bit of space in the database.
Each of these database areas can be cleaned up and, as a result, database size reduced by running a separate administrative stored procedure that ships with TariffShark Hammerhead. If you would like to learn more about these stored procedures so that you can keep your TariffShark database running efficiently, contact TariffShark Support
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:
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.