Month: August 2011

Tariff Record Version (TRV) Queue Processing

Tariff Record Version (TRV) Queue Processing runs automatically when TariffShark is running.  It is responsible for converting section-based and sheet-based Tariff Record Versions’ marked content edited in Microsoft Word into marked DOC, clean RTF, marked PDF, clean PDF, and plain text formats.  To make it unobtrusive, the work is done in the background.  To make it as quick and efficient as possible, the work is distributed across all logged in TariffShark users.

A section-based or sheet-based TRV is automatically submitted for document processing when a user saves the TRV’s content in Word.  Once submitted, it waits in a line (or queue) behind other TRVs that need to be processed.

Once in line, each TRV has up to three (3) attempts to finish processing successfully.  TRV queue processing status can be monitored from the Dashboard (for the context company).  A TRV that failed queue processing (one with zero retries left) can be re-submitted for processing from the “Failed Processing” tab on the Dashboard.  All document processing associated with a TRV queue item is performed on the client computer.   Files are temporarily saved in the temp folder and, once all content is ready, the data is permanently saved on the server.

As a user, you can manage the frequency at which TariffShark checks the queue for new content to be processed by adjusting the “Queue Processing Interval” setting.  Valid values are integer numbers between 5 and 300 (seconds).  If there are a lot of TRVs in the queue and you’d like them processed as quickly as possible, a low number of seconds keeps your computer busy processing TRVs.  If you don’t want your computer slowed down by processing TRVs, use a higher number of seconds, but be advised that the TRV Queue will be cleared out more slowly.  To learn how to change the Queue Processing Interval, check out the blog article entitled TariffShark Document Processing.

Automated Queueing of TRVs

If a TRV’s Document Layouts use Header and/or Footer Templates that leverage TariffShark data fields, any change in the fields’ values automatically submits the TRV for document processing.  Further, if a Header or Footer Template is updated, all TRVs that use Document Layouts that leverage the updated Template will automatically be submitted for processing.  Use great caution when updating Header and Footer Templates because if they’re widely used, many, many TRVs could be inserted into the TRV Queue.

No doubt, this is a complex topic…and we would be happy to clarify it further.  Simply comment below or contact TariffShark Support.

Does My eTariff Filing Have to Include Tariff Records?

In last week’s blog article, eTariff Filing Level Associations, we introduced nine broad filing type categories.  This article will use the same broad categories to answer the question “does my eTariff filing have to include tariff records”?

Normal – A “normal” filing generally initiates a statutory action against an existing eTariff.  As such, proposed changes to an electronic FERC tariff would be made by submitting tariff records.

New – A “new” filing establishes a new Tariff Id (FERC’s term for what TariffShark calls a Tariff Database).  This type of filing must include tariff records.

Refiled – Like a “new” filing, a “refiled” filing establishes a new Tariff Id.  This type of filing must include tariff records.

Compliance – The circumstances surrounding a “compliance” type filing vary greatly.  Some compliance filings will include tariff records and some will not.

Amendment – An “amendment” filing proposes changes to an earlier eTariff filing pending before the Commission.  What’s being amended in a amendment filing are tariff records.  Therefore, this type of filing must include tariff records.

Motion – A “motion” filing motions into effect tariff record from an earlier eTariff filing.  Therefore, tariff records must be included in a motion filing. In order to add tariff records from an earlier filing to a “motion” filing, the Filed Tariff Record Versions in the earlier filing must have a FERC Response of Suspended”.

Withdraw – The sole purpose of a “withdraw” type filing is to withdraw an earlier eTariff filing pending before the Commission.  A withdraw type filing must not include tariff records.

Report – Similar to an “amendment” filing, a “report” filing is used to supplement the record of an earlier eTariff filing pending before the Commission.  Unlike the “amendment” type, however, a report type consists solely of attachments.  Statutory tariff records are not allowed in this type of filing.  It is valid, however, to include pro forma tariff records within a “report” filing.

Cancellation – A “cancellation” filing proposed to cancel an entire Tariff Id (FERC’s term for what TariffShark calls a Tariff Database).  A cancellation filing must include a single tariff record, which carries the proposed effective date of the cancellation.

To summarize…

Type of Filing Includes Tariff Records?
Normal Always
New Always
Refiled Always
Compliance Sometimes
Amendment Always
Motion Always
Withdraw Never
Report Pro Forma Only
Cancellation Exactly 1

If you would like to know more including tariff records in your eTariff filings or if you have any other questions, please comment below or contact TariffShark Support.

eTariff Filing Level Associations

FERC’s eTariff rules allow you to associate an eTariff filing with an earlier eTariff filing.  This article will explain why you might want to associate two filings and how to do this in TariffShark.

When submitting an eTariff filing that relates to, acts upon, or extends an earlier eTariff filing, you associate it with the earlier filing.  Based upon the type of filing you are preparing, you may or may not be required to make an association with an earlier filing.

Normal – A “normal” filing generally initiates a statutory action against an existing eTariff.  As such, an associated filing would not be expected.

New – A “new” filing establishes a new Tariff Id (FERC’s term for what TariffShark calls a Tariff Database).  Filing associations are not expected within this type of filing.

Refiled – Like a “new” filing, a “refiled” filing establishes a new Tariff Id.  Filing associations are not expected within this type of filing.

Compliance – The circumstances surrounding a “compliance” type filing vary greatly.  Sometimes it makes sense to associate a “compliance” filing with an earlier eTariff filing and sometimes it doesn’t.

Amendment – An “amendment” filing proposes changes to an earlier eTariff filing pending before the Commission.  Therefore, “amendment” filings should always be associated with an earlier filing.

Motion – A “motion” filing motions into effect tariff record from an earlier eTariff filing.  Therefore, “motion” filings should always be associated with an earlier filing.

Withdraw – The sole purpose of a “withdraw” type filing is to withdraw an earlier eTariff filing pending before the Commission.  Therefore, “withdraw” filings should always be associated with an earlier filing.

Report – A “report” filing is used to supplement the record of an earlier eTariff filing pending before the Commission.  Therefore, “report” filings should always be associated with an earlier filing.

Cancellation – A “cancellation” filing proposed to cancel an entire Tariff Id (FERC’s term for what TariffShark calls a Tariff Database).  Filing associations are not expected with this type of filing.

In TariffShark, associating a Filing with another one is straightforward.

  1. Use the “Update Filing” command in the SmartBar to open the Update Filing screen for the Draft Filing you are preparing.
  2. Click the ellipsis button next to the Associated Filing field to select an earlier Filing to which an association should be made.
     
  3. Select the Associated Filing by clicking on it in the grid and then click the “Select” button.

If you would like to know more about Filing level associations or if you have any other questions, please comment below or contact TariffShark Support.