Draft eTariff Data Elements and Descriptions · Web viewFollowing is a guide describing the various...

Pipeline Segment Work Paper (2 of 5)NAESB Meeting 4/26/2007

The WGQ Pipeline Segment (Pipelines) believes the goal for the NAESB electronic tariff filing effort should be to assist the Federal Energy Regulatory Commission (Commission) in the development of an instruction manual for communicating tariff information to the Commission. The Pipelines have previously submitted proposed NAESB standards. The Pipelines feel that one definition and one standard would be sufficient for this process with the detailed requirements being provided in the Instruction Manual, in similar fashion to the instructions currently available for the filing of the Index of Customers. This Instruction Manual will contain information such as the definitions, data tables and code values tables required for entities to com-plete an electronic tariff filing.

The Pipelines work product consists of the following 5 documents that are being provided separately to en-hance readability:

1. Pipeline Segment Comments on the proposed standards as of April 12, 2007 (work paper previ -ously submitted = work paper 1 of 5).

2. A draft of the proposed Instruction Manual referred to in the Pipeline Segment Work Paper posted for the April 26, 2007 NAESB meeting that provides comments on the proposed standards posted for the March 13, 2007 NAESB meeting (this document – Pipeline work paper 2 of 5).

3. Examples of an electronic tariff filing through a potential eTariff Filing Portal (Pipeline work paper 3 of 5).

4. Draft Reference Code Table (Pipeline work paper 4 of 5).

5. Additional Pipeline Segment Questions (work paper 5 of 5).

In order, to work toward a mutually beneficial process, the Pipelines took numerous steps to compile the necessary information for the following Instruction Manual, including:

Studied the data tables and example provided by the Commission Staff for the March 13, 2007 and April 26, 2007 NAESB meetings, respectively, in an effort to clarify and further define the data tables into a meaningful reference for non-technical users. These data tables are the foundation upon which actual filing procedures will be developed.

Documented in the included Electronic Tariff Filing Process Flow Diagram a proposed method of data delivery, which is key to this electronic process. This process, as delineated on the flow chart, provides for a bifurcated submission process, which would allow for more flexibility for the submis-sion of various types of tariff data.

Compiled a draft reference code table based on the eTariff Filing Rules Listing as published on the FERC website. This document indicates the codes for the various filing types, and the codes for the corresponding attachments and other information, such as whether or not the document (attach-ment) can be waived. This table should be included in the Instruction Manual for easy reference.

Developed an example of a natural gas tariff filing using a FERC website portal to demonstrate how a Company could utilize a web-based interface to electronically transmit a tariff filing. This example includes mock-ups of what the website could look like and what types of menus could be available.

To gain a better understanding of the Commission’s requirements, the Pipelines generated an addi-tional list of questions for the Commission Staff, which is being provided in a separate work paper.

Taken all together, the work product of the Pipelines should be viewed as a framework for a comprehen-sive electronic tariff filing solution for all of the affected energy industries. While the following Instruction Manual is only a first draft, it is the Pipeline recommendation that it should form the basis of the Electronic Tariff Filing Instruction Manual to be included in the Commission order in Docket No. RM01-5-000.

of 50


Federal Energy Regulatory Commission

Instruction Manual for Electronic Tariff Filing

RM01-5-000 – Attachment __

Issued Mo/Day/Year

of 50


Table of Contents

Topic Details Page

Table of Contents 3

Introduction 4

Business Process Electronic Tariff Filing Process Flow Diagram

5

Example of a Tariff Filing through a Potential eTariff Filing Portal

6

Explanation of Business Process 7

Internet Transport Process/Mecha-nism

8

Glossary of Terms and Data Ta-bles

Explanation of 2 Versions Provided 9

Glossary of Terms - Clean 10

Data Tables - Clean Filing Data 11

Filing Attachment Data 19

Tariff Content Data 22

Glossary of Terms - Redlined 28

Data Tables - Redlined Filing Data 29

Filing Attachment Data 36

Tariff Content Data 39

Reference Tables Filing Types, their related codes and required attachments for each type

45

For each Filing Type – a list of doc-ument attachments that can be waived

Cross Reference of Filing Types to Attachment Type Code

Attachment Reference Codes

List of Special Characters that are not valid for the Supporting Docu-ment File Name

Record Change Type

Acceptable File Formats 48

of 50


Introduction

This instruction manual is for use by an entity required to submit Tariff Filings to the Commission pur-suant to Title 18 Code of Federal Regulations Parts 35, 154, 284, 341 or other Parts as required by the Commission. Following is a guide describing the various processes/mechanisms, data tables, and refer-ence tables used in the submission of Tariffs, OATTS, Rate Schedules, certain service agreements, Statement of Conditions, rates, and any other material the Commission requires a Company to file.

of 50


of 50

Authorized Company User Logs in

Enters filing data Chooses Processing

option 1 or 2

FERC eTariff Portal / System

Accept upload Validate filing

completeness Send Filing

Company e-mail Notice

If valid, process filing-otherwise place filing in error queue

Enter Metadata for each attachment and upload attachment

If correction for pre-vious filing identify item in error queue

Validate for com-pleteness

If valid, allow Tariff content data to be entered. Or else place filing in error queue

1

UPLOAD ENTIRE FILING 1

ENTER COMPONENTS 2

Tariff Filing

FERC eTariff Portal / System

Complete Filing PDF

FERC Databases

FERCeLibrar

y

FERC eTariff Portal / System (Tariff Content

Data)

Choose to upload Metadata and associ-ated Tariff records

Or enter Metadata and upload individual Tar-iff records

Enter data/upload records

Filing Company

e-Mail NoticeSubmit

Send

Send

Send

Update

Error Queu

e

a

b

aa

b

a

b

Assumes: Metadata / upload would be an XML file

FERC eTariff Portal

FERC eTariff Portal


Example of a Tariff Filing through a Potential eTariff Filing Portal

For readability, the example screen pages are provided in the attached docu-ment titled 2006 0426 PL Example Tariff Filing.pdf.

of 50


Explanation of Business Process

NOTE: Once the overall business approach / process is agreed to, this section will contain a narra-tive description of the process that matches the diagram and the example (previous pages).

of 50


Internet Transport Process/Mechanism Technical Specifications

Note: This section will address the technical aspect of ‘how’ to submit the filing such as valid formats. See Page 48 for a list of acceptable file formats for attachments.

Some example information for this section might be: XML Tags – does this = ‘element name’ in the data tables?File formats – if ASCII or XML – what is the structure?Error handlingPage set up – margins, characters per line, etc.

of 50


GLOSSARY OF TERMS and DATA TABLES

Following are two versions of a proposed Glossary of Terms and Data Tables. Both are based on the FERC STAFF PROPOSED eTARIFF FRAMEWORK work paper posted for the March 13, 2007 NAESB meeting. Both versions reflect the edits proposed by the Pipeline Segment. The first version of these documents is ‘clean’ and the second version is provided in redline format.

of 50


CLEAN VERSION

Glossary of Terms

Line Term Definition

1 Commission Federal Energy Regulatory Commission.

2 Company An entity required to submit Tariff Filings to the Commission pursuant to Parts 35, 154, 284, 341 or other Parts as required by the Commission.

3 Database A compilation of all Tariffs, OATTS, Rate Schedules, certain service agreements, Statement of Conditions, rates, and any other material the Commission requires a Company to file. A Company must have no more than one Database in effect at any time. A Database must contain at least one Record.

4 Field An element of a Record. A Field will have a defined format, may be required, conditional or optional and may have restricted values. A Field may contain text or a document (e.g. a .pdf file).

5 Record A single occurrence (row) in a Database. A Record may consist of multiple Fields.

6 Tariff Filing or Filing A Company filing made pursuant to Title 18 Code of Federal Regulations Parts 35, 154, 284, 341 or other Parts as required by the Commission. The Tariff Filing / Filing will include all of its components: e.g.: Transmittal Letter, form of notice, supporting documents, and required Tariff Records of Tariffs, OATTS, Rate Schedules, service agreements, Statement of Conditions, rates, and any other material the Commission requires to be filed.

7 Tariff Record A sheet, section or complete tariff document contained in the database for a Company.

8 Type of Filing A specific Commission defined Tariff Filing / Filing that may be filed by a Company pursuant to Title 18 Code of Federal Regulations Parts 35, 154, 284, 341 or other Parts as required by the Commission.

of 50


CLEAN VERSION

Draft Electronic Tariff Data Elements and Descriptions

Introduction

The following specify the Data Dictionary for electronic tariff filings. Conceptually, an electronic tariff filing consists of the following items: Filing Data - describes the overall filing. Filing Attachment Data - supporting documents required by specific filing types. Tariff Content Data - the actual tariff "text" or "content" of the Tariff itself with its associated metadata.

Filing DataThis data defines the filing and this data will be provided with each submission.

Business Name Element Name

Definition of Data Element Field Format

(length)

Valid Values Comments / Conditions Pipeline Segment Questions, Comments and Examples

Company Identifier company_id A FERC-Designated company identifier code.

Numeric (10) Any number between 1 and 2,147,483,648

Required. Is this the Current Company No. assigned by FERC?

of 50




(length)


Database Identifier database_id A unique identifier for the database for the Company as it pertains to the database being modified by the filing. This can be any value in the allowable range of numbers, but it must be unique for each company database. A company must have no more than one active database.


Required.

This will be assigned by the Company.

Could be “1” for all submitting entities. Is this a problem or will the combination of the company identifier and the database identifier be used to differentiate them?

Does this mean you have only one version of a tariff volume(s) in a single database?

What does “active” mean?

If only one database is “active” at a time, how does a TSP submit overlapping changes (i.e. during a rate case settlement and or later needing to submit the revised rate sheets for a superseded database)?

Database Title database_title The title or name assigned to each company database.

Alphanumeric (100)

Free form text. Required for initial, first-time filings. After the initial submission, the Database Identifier is used.

Examples: “Stingray Pipeline Company THIRD REVISED VOLUME NO. 1” or "Trunkline Gas Company, LLC's tariff" (which may include a Volume No. 1 and Volume No. 2). Needs to have the ability to be general, not specific to one tariff volume.

Does alphanumeric include special characters (e.g. apostrophes)?

of 50




(length)


Filing Identifier filing_id A unique identifier for the specific filing for the Company.


Required.

Assigned by the Company. This can be any value in the valid range of numbers, but it must be unique across all filings for a specific Company.

If Company No. is 164, could the first filing be 1640001? Alternatively, could the date be incorporated (e.g. 1640403071 or 1640403072?

Will this data element be visible on the FERC website? Will it be a piece of information shown when the tariff is re-assembled by FERC? Will it be available for use as search criteria?

Filing Title/Description

filing_title The title given to the filing by the filing Company.

Alphanumeric (80).

Free form text. Required. Examples: “Non-conforming Agreements 03.2007” or "ACA Filing"


of 50




(length)


Type of Filing/Filing Reference Code

filing_type The type of Tariff Filing or Filing being made.

Numeric (10). Refer to http://www.ferc.gov/docs-filing/etariff/fil-soft-help/etariff-rules-table.pdf for the current list of codes.

Required.

Chosen on the FERC website from a drop down menu. Some examples are:

1000 (§ 35.13(a)(2)(iii) - Rate Schedule Changes Other Than Rate Increases/Compliance Filing)

3200 (§342.2(a) - Establishing Initial Rates - Cost of Service option)

This URL may need to be updated with the final order.

Could the initial choices in the dropdown menu be based on whether the Company is electric, gas, or oil?

The instruction manual should include a table of Filing Types, their related codes and required attachments for each type.(See attached table).

How will changes to the reference codes and filing requirements be communicated in the electronic tariff filing system? If the above referenced table is included in the electronic tariff instruction manual, it will need to be updated as changes occur.

Point of Contact First Name

poc_fname First name of the person (point of contact person) initiating the submission of the filing on the FERC website. This person will NOT be on the service list.

Character (30). Free form text. Required.

The Point of Contact person must already be a user e-Registered with FERC.

Must the logon i.d. user have to be the Point of Contact? If so, can the Point of Contact information data be pre-filled by the FERC?

Point of Contact Middle Initial

poc_midinit Middle initial of the person (point of contact person) initiating the submission of the filing on the FERC website. This person will NOT be on the service list.

Character (1). Free form text. Optional. Same questions as included for Point of Contact Person.

of 50




(length)


Point of Contact Last Name

poc_lname Last name of the person (point of contact person) initiating the submission of the filing on the FERC website. This person will NOT be on the service list.

Character (30). Free form text. Required. Same questions as included for Point of Contact Person.

Point of Contact Phone Number

poc_phone The phone number of the person (point of contact person) initiating the submission of the filing on the FERC website. This person will NOT be on the service list.

Character (15) Numeric. Form of 999999999999999

Required.

Digits are interpreted as:

(999) 999-9999 x99999

Same questions as included for Point of Contact Person.

Point of Contact email Address

poc_email The email address of the person (point of contact person) initiating the submission of the filing on the FERC website. This person will NOT be on the service list. This e-mail address will receive filing validation communication from the FERC.

Alphanumeric (100).

Free form text. Required.

The email address must be eRegistered with FERC.


Company Authorizing Person First Name

auth_fname First name of the person authorizing the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.


Company Authorizing Person Middle Initial

auth_midinit Middle initial of the person authorizing the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Character (1). Free form text. Optional.

of 50




(length)


Company Authorizing Person Last Name

auth_lname Last name of the person authorizing the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.


Company Authorizing Person Title

auth_title The company title of the person authorizing the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Character (30) Required.

This element added by Pipeline segment to comply with Regulations.

Company Authorizer/Signer email

auth_email The email address of the person authorizing the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Alphanumeric (100).

Free form text. Required.


Additional Communication First Name

comm_fname_1comm_fname_2comm_fname_3

First name of additional designee(s) for communication for the subject filing. This person will be on the service list.

Character (30) per entry

Optional.

May submit up to 3 entries.

Additional Communication Middle Initial

comm_midinit_1comm_midinit _2comm_midinit _3

Middle initial of additional designee(s) for communication for the subject filing. This person will be on the service list.


Optional.


of 50




(length)


Additional Communication Last Name

comm_lname_1comm_lname_2comm_lname_3

Last name of the additional designee(s) for communication for the subject filing. This person will be on the service list.


Optional.


Additional Communication Phone Number

comm_phone_1comm_phone_2comm_phone_3

Phone number of the additional designee(s) for communication for the subject filing. This person will be on the service list.

Numeric (15) per entry

Numeric. Form of 999999999999999

Required for each additional communication designee(s).

May submit up to 3 entries. Digits are interpreted as:

(999) 999-9999 x99999

Additional Communication email

comm_email_1comm_email_2comm_email_3

Additional designee(s) for communication for the subject filing. This person will be on the service list.

Alphanumeric (100) per entry

Free form text Required for each additional communication designee(s).

May submit up to 3 entries. The email address(es) must be eRegistered with FERC.

of 50




(length)


Associated Filing assoc_filing The previous filing to which the subject filing pertains (i.e. associated).

Numeric (10) Any number between 1 and2,147,483,648

Conditional.

his is not applicable to all filing types. Where it is used, it must refer to a previous filing, and the value should be that previous filing's "filing_id" value.

An example might be the subject filing is a compliance (or withdrawal) filing and the previous, applicable filing to which it pertains must be identified in this field.

What does “associated” mean? Associated filings could include:

Compliance filings

Requests for rehearing

What if the subject filing pertains to more than one unconsolidated previous filing(s)?

If we are complying with a previous order it would pertain and could relate to more than one filing (could all be under one docket number).

Fee reference code fee An indication of whether or not any fee is associated with the subject filing.

Use "Y" or "N" Required. Default value is “N”. In 18 CFR 154 it says there are no longer any fees. Do the fees referenced here apply to a segment other than Natural Gas? Is this to say whether a fee was submitted or what kind of fee or something else? Why was it added? How does a fee get attached?

Suspension Motion sus_motion An indication of whether or not the Tariff Records should automatically go into effect at the end of the applicable suspension period.

Use "Y" or "N" Required. Default value is “Y”. If the value is “N”, at the end of the suspension period, a separate filing is required to place the Tariff Records into effect.

of 50


Filing Attachment Data:This defines data for each supporting document that is either (1) being provided with the filing or (2) for which a waiver is requested


Definition of Data Element Field Format (length)




Required. Same as filing data.



Required.

Assigned by the Company. This can be any value in the allowable range of numbers, but it must be unique across all filings for a specific company.

Same as filing data.

Attachment Reference Code

att_ref The FERC assigned reference code for each attachment type.

Numeric (10) Please refer to http://www.ferc.gov/docs-filing/etariff/fil-soft-help/etariff-rules-table.pdf for the current list of codes.

Required.

If attachment pertains to a specific document defined for the type of filing, the appropriate document reference code must be used. If the attachment is an 'additional' or supplemental document that does not pertain to a specific supporting document required by the filing type, and does not already have a specific code assigned to it, the value should be “0”.

Note: the code is different for each filing type.

This site may need to be updated with the final order.

The instruction manual should include a table of Attachment Reference Codes, (See attached table).

Can there be more than one attachment with the same reference code in the same filing?

of 50





Waiver Requested waive_req An indication of whether or not the filing Company is requesting a waiver for submission of the document specified by the Attachment Reference Code.

Character (1) "Y" - waiver is requested

"N" or " " - waiver not requested

Conditional on whether the Attachment Reference Code allow for waiver of the attachment.

For each document that is requested to be waived, the attachment reference code (above) is provided, and a value of "Y" is entered here. If an actual document is being provided, this value should be "N" or left empty (i.e. “ “).

Does a waiver document need to be attached?

The instruction manual should include a table indicating for each Filing Type which attachment documents can be waived.

Supporting Document

doc_raw_data This is the actual document 'content'.

Binary (10 MB)

(see questions)

Actual document data.

Required if document is not waived.

The document file contents will be stored by the FERC electronically as binary data.

Transmitted in what format? Since it is not anticipated that the submitter will be expected to transmit the file as binary data the Field Format (length) entry needs to be updated to what is expected to be sent.

What if a single attachment is larger than 10 MB?

of 50





Supporting Document File Name

doc_filename The file name assigned by the submitter of the Supporting Document being attached.

Alphanumeric (64).

Free form text. Required if document is not waived.

This file name will be used to identify the document and the extension will be used for retrieval purposes. If a document is being attached a valid file name must be entered in this field. Valid file names cannot include special characters such as: ? / * \ " ' > <

The instruction manual should include a list of the special characters that are not valid for inclusion in file names.

Do we include file name extensions? (e.g., “Transmittal Letter.doc”). If yes, the definition of this data element needs to include that instruction.

Are spaces allowed in file names?

Document Security Level

doc_sec_lvl The level of security requested for the specific attached document corresponding to the applicable Attachment Reference Code.

Character (1) "P" - public

"B" - public non-Internet

"M" - privileged

"X" - Critical Energy Infrastructure

"W" – used only if waiver is requested for the attachment

Required. The attachments in this Filing Attachment Data are non-tariff information. Can this element also apply to Tariff Record level data in the Tariff Content Data section (i.e., maps)?

In the valid Values, does the waiver refer to a waiver of the security level or a waiver of the submission of the document?

of 50


Tariff Content DataThis provides the data for each Tariff Record of a Tariff document that is being submitted for filing.

Business Name Element Name Definition of Data Element Field Format (length)







Required. Assigned by the Company. This can be any value in the allowable range of numbers, but it must be unique across all filings for a specific company.

Same as filing data.Needs to have an identifier for when more than one filing is made on the same date. A, B, C or 1, 2, 3.

Option Designation filing_opt An identifier that designates the alternative Tariff Record option being submitted.

Character (1) "A" thru "Z" allowed.

Required. Default (no options are provided) is “A”. Options must increment through alphabet, i.e. a filing cannot have an "A" and a "C" option without also having a "B" option.

Database Identifier database_id A unique identifier for the database for the Company as it pertains to the database being modified by the filing. This can be any value in the allowable range of numbers, but it must be unique for each company database. A company must have no more than one active database.


Required. Assigned by the Company.


of 50




Record Identifier record_id An identifier for the Tariff Record within a given database that will not change as a result of revisions to the content of the Tariff Record (with same or different effective dates). No two different Tariff Records in the same database may have the same Record Identifier.


Required. Assigned by the Company. Each Tariff Record in the tariff has an associated Record Identifier number that does not change with each revision within a given database. To differentiate revisions to the Tariff Record, the user must rely upon the effective date and Record Effective Priority Order. The Record Identifier is not used for collation and does not have to be sequential.

Two issues:Example of non-sequential Record Identifiers:Sheet No. 143 could have Record Identifier 108 and Sheet No. 144 could have Record Identifier 109. To insert Sheet No. 143A between Sheet No. 143 and Sheet No. 144, Sheet No. 143A could have Record Identifier 347.

Example of revisions to a Tariff Record over time in a given data base:First Revised Sheet No. 143 and Second Revised Sheet No. 143 will both have Record Identifier 108. All subsequent revisions to Tariff Record Sheet No. 143 will continue to have Record Identifier 108.Won’t the above method be too difficult to track, especially for smaller companies?

Record Title record_title The name of the Tariff Record contents. When the Company database is assembled, this would be printed at the beginning of the record.

Alphanumeric (254).

Free form text. Optional. Assigned by the Company.

Is this topic (section) level name (e.g. “General Terms and Conditions” or “Gas Quality”)? It might need to be for company Web sites for adherence to current NAESB standards

Record Number record_num Textual identifier of the Tariff Record. When the Company database is assembled, this would be printed at the beginning of the content.

Alphanumeric (50).

Free form text. Required. Assigned by the Company.

Examples:First Revised Sheet 143Sub Second Revised Sheet No. 10A.01e.

of 50




Record Collation Value

record_sort When the company database is reassembled, this value will determine the sort order in which things are merged.

Alphanumeric (25).

Free form text. Required. Need to be able to include an intelligent numbering / alphabetical system by providing specific number of characters and delimiters. Examples:Sheet No. 143 = 00143Sheet No 567B = 00567.00BSheet No. 10A.01e = 00010.xxA.001.e.

Record Parent Identifier

record_parent The Record Identifier for the higher-level part of the tariff with which this Tariff Record belongs. The value provided must be a valid Record Identifier of another Tariff Record.

Numeric (10) If the submitter chooses not to use the functionality of this field, they must still populate the field with “0”. Otherwise, the value must be a valid Record Identifier

Required. Assigned by the Company. May be used to identify the Volume number of the Tariff for which this Tariff Record applies. Sheet based tariffs can use this to identify different volumes, i.e., First Revised Volume No. 1, Original Volume No. 2, Second Revised Volume No. 1.When a section based tariff approach is used, may be used to identify the section to which the Tariff Record is a subpart.

If this data element is being used to identify a volume of a tariff, how is the record for that Parent Record accomplished? Is the following scenario a correct utilization of this data element (not the only possible implementation)? A tariff has two volumes: each volume cover sheet has a Parent Record Identifier of 0. The cover sheet for Volume 1 has a Record Identifier of 100 and the cover sheet for Volume 2 has a Record Identifier of 200. Changes to a Tariff Record in Volume 1 will reflect a Parent Record Identifier as 100 and changes to Tariff Records in Volume 2 will have a Parent Record Identifier of 200.

Record Effective Date

eff_date The proposed effective date for the specified content.

Date (10) Valid Date values. Required. Is there a specific data format, i.e. MMDDYYYY or MM-DD-YYYY, etc.?

of 50




Record Effective Priority Order

apply_order An indicator that directs which of multiple changes of a given Tariff Record (the same Record Identifier) proposed to go into effect on the same day, will take precedence, i.e. the Tariff Record with the highest numeric value will supersede any other Tariff Records with the same Record Identifier also proposed to be effective for that day.


Required. Assigned by the Company. Default value is ‘1’. The value must be unique for a specific Tariff Record for a specific effective date.When the current tariff is assembled for a particular effective date and there are multiple Tariff Records with the same Record Identifier and the same effective date, the approved Tariff Record for that effective date with the highest priority number will be the effective Tariff Record.

Record Raw Data record_data The actual Tariff Record 'content’. This Record Raw Data would apply to sheet, section or total tariff depending on what granularity the filing company has chosen.

Binary?? (10 MB)See questions

Actual content data.

Required. Submitter will submit in the Valid Data Format of <TBD>.The FERC will convert the document submitted to binary.

Does ‘binary’ = native file format with extensions (e.g. WORD = .doc or EXCEL = .xls)?Field size limitation may be problematic – need to address how larger submission will work.Can the headers and footers as they currently exist be included in the Record Raw Data?

Record Plain Text record_text The plain text version of the content of the Record Raw Data. Formatting and other binary values are stripped from this content.

Alphanumeric (10 MB).

Free form text. This is not a field that will be submitted by a Company. It is the text extracted by FERC from the Record Raw Data submitted, i.e. all control codes and special binary characters are removed.

How should certain documents, i.e. maps, be submitted in order for FERC to be able to accomplish this?

of 50




Record Change Type

record_change A description of the type of change being requested.

Character (15) see instruction manual

Required.The instruction manual should include a list of the valid Record Change Type.

Examples: “NEW""CHANGE""CANCELLATION”Are there other types needed, e.g. “WITHDRAW” or PROFORMA”?

Associated Filing assoc_filing The previous filing to which the subject filing pertains (i.e. associated).Note that this is used in conjunction with the "assoc_ record_id" value and the "assoc_option" (below).


Conditional.

This is not applicable to all filing types. Where it is used, it must refer to a previous filing, and the value should be that previous filing's "filing_id" value.


Same questions as in Filing Data.

Associated Record Identifier

assoc_record_id This is used to associate the specific content with a previous filed content item. For example, withdrawal filings must identify the content being requested to be withdrawn.

Note that this is used in conjunction with the "assoc_filing" value (above) and the "assoc_option" (below).


Conditional. This is not applicable to all filing types. Where it is used, it must refer to a Record ID in previous filing, and the value here should be that data's " record_id" value.

How does this differ from the Record Identifier and Associated Filing data that is already provided elsewhere (i.e. If the Record Identifier cannot change, and it has already been entered at the beginning of the Record Data, isn’t this a repetition of previously provided info within the same filing event)?

of 50




Associated Option Designation

assoc_option An identifier that designates the alternative associated record option being submitted. Note that this is used in conjunction with the "assoc_filing" value and the "assoc_ record_id" (above).

Character (1) "A" thru "Z" Conditional – required only when an associated filing is identified. Where it is used, it must refer to correct Option Designation in a previous filing, and the value should be that previous data's "filing_opt" value.

Alternative Record Number

alt_sec_num This element added by FERC on its example.

This field is not necessary given the Record Number and the Record Collation Value are formatted as suggested above.

of 50


REDLINED VERSIONGlossary of Terms

Line Term Definition

1 Commission Federal Energy Regulatory Commission.

12 Company An entity company regulated by the FERC required to submit Tariff Filings to the Commission pursuant to Parts 35, 154, 284, 341 or other Parts as required by the Commission.

23 Database A Ccompilation of all tariffs, Tariffs, OATTS, Rate Schedules, certain service agreements, Statement of Conditions, rates, and any other material the Commission requires a Company to be filed in a data base format. A Company must have no more than one active Data base. Database in effect at any time. A Database must contain at least one Record.

34 Fields An Field is an element of a Record. A Field will have a defined format, may be mandatory or discretionary,required, conditional or optional and may will have defined formats, and have restricted values. A Field may contain text or a document (e.g. a .pdf file).

45 Record A single record of occurrence (row) in a Data base. A Record may will consist of multiple Fields. A record may contain a Field that is plain text or a document (such as a PDF file). A Data base must contain at least one Record.

56 Tariff Filing or Filing A Tariff Filing consists of a Company filing made pursuant to Title 18 Code of Federal Regulations Parts 35, 154, 284, 341 or other Parts as required by the Commission. The Tariff Filing / Filing will include with all of its components: e.g.: Transmittal Letter, form of Nnotice, supporting documents, and required Tariff Records of tariffs, Tariffs, OATTS, Rate Schedules, service agreements, Statement of Conditions, rates, and any other material the Commission requires to be filed. in a Data base format.

7 Tariff Record A sheet, section or complete tariff document contained in the database for a Company.

68 Type of Filing A specific Commission defined Tariff Filing / Filing that may be filed by a Company pursuant to Title 18 Code of Federal Regulations Parts 35, 154, 284, 341 or other Parts as required by the Commission.

of 50


REDLINED VERSION

Draft eElectronic Tariff Data Elements and Descriptions

Introduction

The following specify the Data Dictionary for eTariff electronic tariff filings. Conceptually, an eTariff electronic tariff filing consists of the following items: Filing Data - which describes the overall filing. Filing Attachment Data - supporting documents required by specific filing types. Tariff Content Data - the actual tariff "text" or "content" of the Tariff itself with its associated metadata.

Filing DataThis data defines the filing and this data will be provided with each submission. In some ways this could be considered defining the "container" to which the Filing Attachment Data and Tariff Content Data belong.



(length)

Restricted Valid Values

Comments / Conditions Pipeline Segment Questions, Comments and Examples


Numeric (10) Any number between 1 -and 2,147,483,648

Required. Is this the Current Company No. assigned by FERC?

of 50




(length)



Database Identifier Tariff_iddatabase_id

A unique identifier for each the database for that the Ccompany as it pertains to the database being modified by the filing. This can be any value in the allowable range of numbers, but it must be unique for each company database. A company must have no more than one active database.


Required.

This will be assigned by the Company.

Could be “1” for all submitting entities. Is this a problem or will the combination of the company identifier and the database identifier be used to differentiate them?

Does this mean you have only one version of a tariff volume(s) in a single database?

What does “active” mean?

If only one database is “active” at a time, how does a TSP submit overlapping changes (i.e. during a rate case settlement and or later needing to submit the revised rate sheets for a superseded database)?

Database Title tariff_titledatabase_title

The title or name to giveassigned to each company database. After the initial filing has been made, this value is no longer required; the "database identifier will suffice.

Alphanumeric (100)

Free form text. Only rRequired for initial, first-time filings.

After the initial submission, the Database Identifier is used.

Examples: “Stingray Pipeline Company THIRD REVISED VOLUME NO. 1” or "Trunkline Gas Company, LLC's tariff" (which may include a Volume No. 1 and Volume No. 2). Needs to have the ability to be general, not specific to one tariff volume.


of 50




(length)



Filing Identifier filing_id A unique identifier for the specific filing for that the cCompany. This can be any value in the allowable range of numbers, but it must be unique across all filings for a specific company.


Required.

Assigned by the Company. This can be any value in the valid range of numbers, but it must be unique across all filings for a specific Company..

If Company No. is 164, could the first filing be 1640001? Alternatively, could the date be incorporated (e.g. 1640403071 or 1640403072?

Will this data element be visible on the FERC website? Will it be a piece of information shown when the tariff is re-assembled by FERC? Will it be available for use as search criteria?

Filing Title/Description

filing_title The title given to the filing by the filing cCompany.

Alphanumeric (80).

Free form text. Required.Must not be empty. Examples: “Non-conforming Agreements 03.2007” or "ACA Filing"


of 50




(length)



Type of Ffiling/Filing rReference cCode

filing_type This defines tThe type of Tariff Filing or Ffiling being made.

Numeric (10). Refer to http://www.ferc.gov/docs-filing/etariff/fil-soft-help/etariff-rules-table.pdf for the current list of codes.

Required.

Chosen on the FERC website from a drop down menu. sSome examples are:

1000 (§ 35.13(a)(2)(iii) - Rate Schedule Changes Other Than Rate Increases/Compliance Filing)

3200 (§342.2(a) - Establishing Initial Rates - Cost of Service option)

This URL may need to be updated with the final order.

Could the initial choices in the dropdown menu be based on whether the Company is electric, gas, or oil?

The instruction manual should include a table of Filing Types, their related codes and required attachments for each type.(See attached table).

How will changes to the reference codes and filing requirements be communicated in the electronic tariff filing system? If the above referenced table is included in the electronic tariff instruction manual, it will need to be updated as changes occur.

Point of Contact First Name

poc_fname First name of the person (point of contact person) initiating the submission offor the filing on the FERC website. This person will NOT be on the service list.

Character (30). Free form text. Required. Must not be empty.

The Point of Contact person must already be a user e-Registered with FERC.

Must the logon i.d. user have to be the Point of Contact? If so, can the Point of Contact information data be pre-filled by the FERC?

Point of Contact Middle Initial

poc_midinit Middle initial of the person (point of contact person) initiating the submission of for the filing on the FERC website. This person will NOT be on the service list.

Character (1). Free form text. Empty/null allowed.Optional. Same questions as included for Point of Contact Person.

of 50




(length)



Point of Contact Last Name

poc_lname Last name of the person (point of contact person) initiating the submission of for the filing on the FERC website. This person will NOT be on the service list.

Character (30). Free form text. Must not be emptyRequired. Same questions as included for Point of Contact Person.

Point of Contact pPhone nNumber

poc_phone The phone number of the person (point of contact person) initiating the submission of for the filing on the FERC website. This person will NOT be on the service list.

Character (15) Numeric. Form of 999999999999999

Required.

dDigits are interpreted as:

(999) 999-9999 x99999


Point of Contact email aAddress

poc_email The email address of the person (point of contact person) initiating the submission of for the filing on the FERC website. This person will NOT be on the service list. This e-mail address will receive filing validation communication from the FERC.

Alphanumeric (100).

Free form text. Required. Valueemail should be entered



Company Authorizing pPerson First Name

auth_fname First name of the person point of the authorizing person for the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Character (30). Free form text. Must not be emptyRequired.

Company Authorizing pPerson Middle Initial

auth_midinit Middle initial of the person point of the authorizing person for the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Character (1). Free form text. Empty/null allowed.Optional.

Company Authorizing pPerson Last Name

auth_lname Last name of point the person point of the authorizing person for the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Character (30). Free form text. Required.Must not be empty.

of 50




(length)



Company Authorizing Person Title

auth_title The company title of the person authorizing the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Character (30) Required.

This element added by Pipeline segment to comply with Regulations.

Company Authorizer/Signer email

signer_emailauth_email

The email address of the person point of the authorizing person for the subject filing pursuant to §154.4 (b) (2) of Title 18 CFR. This person will be on the service list.

Alphanumeric (100).

Free form text. Value Valid email should be entered, and t Required.


Additional Communication First Name

comm_fname_1comm_fname_2comm_fname_3

First name of additional designee(s) for communication for the subject filing. This person will be on the service list.


Optional.


Additional Communication Middle Initial

comm_midinit_1comm_midinit _2comm_midinit _3

Middle initial of additional designee(s) for communication for the subject filing. This person will be on the service list.


Optional.


Additional Communication Last Name

comm_lname_1comm_lname_2comm_lname_3

Last name of the additional designee(s) for communication for the subject filing. This person will be on the service list.


Optional.


of 50




(length)



Additional Communication Phone Number

comm_phone_1comm_phone_2comm_phone_3

Phone number of the additional designee(s) for communication for the subject filing. This person will be on the service list.

Numeric (15) per entry

Numeric. Form of 999999999999999

Required for each additional communication designee(s).

May submit up to 3 entries. Digits are interpreted as:

(999) 999-9999 x99999

Additional Communication email

comm_email_1comm_email_2comm_email_3

Additional designee(s) for communication for the subject filing. This person will be on the service list.

Alphanumeric (100) per entry

Free form text Required for each additional communication designee(s).

May submit up to 3 entries. The email address(es) must be eRegistered with FERC.

Associated Filing assoc_filing The previous filing to which the subject filing pertains (i.e. associated). This is used to associate the filing with a previous filing made to FERC. For example, compliance filings and withdrawal filings must identify the previous, applicable filing to which they pertain.


Conditional.

This is not applicable to all filing types. Where it is used, it must refer to a previous filing, and the value here should be that previous filing's "filing_id" value.


What does “associated” mean? Associated filings could include:

Compliance filings

Requests for rehearing

What if the subject filing pertains to more than one unconsolidated previous filing(s)?

If we are complying with a previous order it would pertain and could relate to more than one filing (could all be under one docket number).

of 50




(length)



Fee reference code fee An indication of whether or not any fee is associated with the subject filing.

Use "Y" or "N" Required.

Default value is “N”.

In 18 CFR 154 it says there are no longer any fees. Do the fees referenced here apply to a segment other than Natural Gas? Is this to say whether a fee was submitted or what kind of fee or something else? Why was it added? How does a fee get attached?

Suspension Motion sus_motion An indication of whether or not the Tariff Records should automatically go into effect at the end of the applicable suspension period.

Use "Y" or "N" Required.

Default value is “Y”. If the value is “N”, at the end of the suspension period, a separate filing is required to place the Tariff Records into effect.

of 50


Filing Attachment Data:This defines data for each supporting document that is either (1) being provided with the filing or (2) for which a waiver is requested.










Required.

Assigned by the Company. This can be any value in the allowable range of numbers, but it must be unique across all filings for a specific company.


of 50






Attachment Reference Code

att_ref Different filing types have differing sets of requested supporting documentation. When an attachment is provided, and that attachment is meeting the request of a specific supporting document, the appropriate document reference code must be provided.

The FERC assigned reference code for each attachment type.

Numeric (10) Please refer to http://www.ferc.gov/docs-filing/etariff/fil-soft-help/etariff-rules-table.pdf for the current list of codes.

Required.

If attachment pertains to a specific document defined for the type of filing, the appropriate document reference code must be used. If the attachment is an 'additional' or supplemental document that does not pertain to a specific supporting document required by the filing type, and does not already have a specific code assigned to it, this the value may should be “0’”.

Some examples of attachments are:

§ 341.2(c)(1) - Transmittal letter

§ 346.2(b) - Cost-Of-Service Summary Schedule

§ 346.2(c)(1) - Statement A

§ 346.2(c)(2) - Statement B

Note: the code is different for each filing type.

This site may need to be updated with the final order.

The instruction manual should include a table of Attachment Reference Codes, (See attached table).

Can there be more than one attachment with the same reference code in the same filing?

of 50






Waiver Rrequested waive_req An indication of whether or not the filing Company The requested is requesting a waiver for submission of the document specified by the Attachment Reference Code.supporting documentation can be requested to be waived by the filing company.

Character (1) "Y" - waiver is requested

"N" or " " - waiver not requested

Conditional on whether the Attachment Reference Code allow for waiver of the attachment.

For each document that is requested to be waived, the attachment reference code (above) is provided, and a value of "Y" is entered here. Of course, if i I f an actual document is being provided, this value should be "N" or left empty (i.e. “ “).

Does a waiver document need to be attached?

The instruction manual should include a table indicating for each Filing Type which attachment documents can be waived.

Supporting Ddocument

doc_raw_data This is the actual document 'content'. That is, the binary data of the file contents as it is stored electronically.

Binary (10 MB)

(see questions)

None. Binary data. Actual document data.

Required if document is not waived.

The document file contents will be stored by the FERC electronically as binary data.

Transmitted in what format? Since it is not anticipated that the submitter will be expected to transmit the file as binary data the Field Format (length) entry needs to be updated to what is expected to be sent.

What if a single attachment is larger than 10 MB?

of 50






Supporting Ddocument fFile nName

doc_filename The file name assigned by the submitter of the Supporting dDocument being attached. This filename will be used to recreate the document when needed.

Alphanumeric (64).

Free form text. Required if document is not waived.

This file name will be used to identify the document and the extension will be used for retrieval purposes. If a document is being attached (e.g. a waiver not requested), a valid file name must be entered herein this field. Only vValid file names cannot include are permitted (e.g. the following cspecial characters are not allowed in filenamesuch as: ? / * \ " ' > <

The instruction manual should include a list of the special characters that are not valid for inclusion in file names.

Do we include file name extensions? (e.g., “Transmittal Letter.doc”). If yes, the definition of this data element needs to include that instruction.

Are spaces allowed in file names?

Document Security Level

doc_sec_lvl The level of security of requested for the specific attached document corresponding to the applicable Attachment Reference Code (if one is included).

Character (1) " " - only if waiver is requested

"P" - public

"B" - public non-Internet

"M" - privileged

"X" - Critical Energy Infrastructure

"W" – used only if waiver is requested for the attachment

Required. The attachments in this Filing Attachment Data are non-tariff information. Can this element also apply to Tariff Record level data in the Tariff Content Data section (i.e., maps)?

In the valid Values, does the waiver refer to a waiver of the security level or a waiver of the submission of the document?

of 50


Tariff Content DataThis provides the data for each section/sheetTariff Record, or complete contents, of a Tariff document that is being submitted for filingfiling. This information could also be provided in an XML file created by a tariff management program.


RestrictedValid Values







Required. Assigned by the Company. This can be any value in the allowable range of numbers, but it must be unique across all filings for a specific company.

Same as filing data.Needs to have an identifier for when more than one filing is made on the same date. A, B, C or 1, 2, 3.

Option Designation filing_opt In some cases, companies desire to submit several "options" for consideration by FERC. For example, one option may be to change 3 or 4 sheets in one way, but change them in a different way in another option. FERC can look at these changes grouped by option and decide if one is more appropriate than another. This designator allows this to be performed. If there is only 1 "option" of changes for review, this value should be "A".An identifier that designates the alternative Tariff Record option being submitted.

Character (1) "A" thru "Z" allowed.

Must not be emptyRequired. Default (no options are provided) is “A”. Options must increment through alphabet, i.e. a filing cannot have an "A" and a "C" option without also having a "B" option.

of 50





Database Identifier tariff_iddatabase_id

A unique identifier for each the database for that the Ccompany as it pertains to the database being modified by the filing. This can be any value in the allowable range of numbers, but it must be unique for each company database. A company must have no more than one active database.


Required. Assigned by the Company.


Record Identifier sect_idrecord_id

This is a unique identifier of the data contained. This identifier is what will track the changes to the content over time. The value must be unique for a specific company. An identifier for the Tariff Record within a given database that will not change as a result of revisions to the content of the Tariff Record (with same or different effective dates). No two different Tariff Records in the same database may have the same Record Identifier.


Required. Assigned by the Company. Each Tariff Record in the tariff has an associated Record Identifier number that does not change with each revision within a given database. To differentiate revisions to the Tariff Record, the user must rely upon the effective date and Record Effective Priority Order. The Record Identifier is not used for collation and does not have to be sequential.

Two issues:Example of non-sequential Record Identifiers:Sheet No. 143 could have Record Identifier 108 and Sheet No. 144 could have Record Identifier 109. To insert Sheet No. 143A between Sheet No. 143 and Sheet No. 144, Sheet No. 143A could have Record Identifier 347.

Example of revisions to a Tariff Record over time in a given data base:First Revised Sheet No. 143 and Second Revised Sheet No. 143 will both have Record Identifier 108. All subsequent revisions to Tariff Record Sheet No. 143 will continue to have Record Identifier 108.Won’t the above method be too difficult to track, especially for smaller companies?

of 50





Record Title sect_titlerecord_title

Theis is the name title of the Tariff Record contents. When the Company database is assembled, this would be printed at the beginning of the record.

Alphanumeric (254).

Free form text. Allowed to be empty.Optional. Assigned by the Company.

Is this topic (section) level name (e.g. “General Terms and Conditions” or “Gas Quality”)? It might need to be for company Web sites for adherence to current NAESB standards

Record Number sect_numrecord_num

Some form of tTextual identifier of the Tariff Record. When the Company database is assembled, this would be printed at the beginning of the content.

Alphanumeric (2550).

Free form text. Must not be emptyRequired. Assigned by the Company.

Examples:First Revised Sheet 143Sub Second Revised Sheet No. 10A.01e.

Record Collation Vvalue

sect_sortrecord_sort

When the company database is reassembled, this value will determine the sort order in which things are merged.

Alphanumeric (25).

Free form text. Must not be emptyRequired. Need to be able to include an intelligent numbering / alphabetical system by providing specific number of characters and delimiters. Examples:Sheet No. 143 = 00143Sheet No 567B = 00567.00BSheet No. 10A.01e = 00010.xxA.001.e.

of 50





Record Parent or Container Identifier

sect_parentrecord_parent

The Record Identifier for the higher-level part of the tariff with which this Tariff Record belongs.In some cases, portions of a Record are 'sub sections' of other portions. If this approach is used, t The value here provided must be a valid Record Identifier of another Tariff Record.

Numeric (10) If the submitter chooses not to use the functionality of this field, they must still populate the field with “0”. Otherwise, the value must be a valid Record Identifier between1 -and 2,147,483,648 if this content is a 'sub part' of other content, or “0” if not.

Required. Assigned by the Company. May be used to identify the Volume number of the Tariff for which this Tariff Record applies. Sheet based tariffs can use this to identify different volumes, i.e., First Revised Volume No. 1, Original Volume No. 2, Second Revised Volume No. 1.When a section based tariff approach is used, may be used to identify the section to which the Tariff Record is a subpart.

If this data element is being used to identify a volume of a tariff, how is the record for that Parent Record accomplished? Is the following scenario a correct utilization of this data element (not the only possible implementation)? A tariff has two volumes: each volume cover sheet has a Parent Record Identifier of 0. The cover sheet for Volume 1 has a Record Identifier of 100 and the cover sheet for Volume 2 has a Record Identifier of 200. Changes to a Tariff Record in Volume 1 will reflect a Parent Record Identifier as 100 and changes to Tariff Records in Volume 2 will have a Parent Record Identifier of 200.

Record Effective Date

eff_date This is tThe proposed effective date for the specified content. is supposed to go into effect.

Date (10) Valid Date values. Required. Is there a specific data format, i.e. MMDDYYYY or MM-DD-YYYY, etc.?

Record Effective Priority oOrder

apply_order An indicator that directs which of When multiple changes of a given Tariff Record (the same Record Identifier) to the same content are proposed to go into effect on the same day, this value will determine which change will take precedence, . Ii.e. the change filedTariff Record with the highest numeric priority value will supersede any other Tariff Records with the same Record Identifier also proposed to be effective for that day.be the one that becomes effective on the given date.

Numeric (10) Any number between 1 -and2,147,483,648

Required. Assigned by the Company. Default value is ‘1’. The value must be unique for a specific Tariff Record for a specific effective date.When the current tariff is assembled for a particular effective date and there are multiple Tariff Records with the same Record Identifier and the same effective date, the approved Tariff Record for that effective date with the highest priority number will be the effective Tariff Record.

of 50





Record rRaw dData sect_datarecord_data

This is theThe actual document Tariff Record 'content’. That is, the binary data of the contents as it is stored electronically. When the Company database is assembled, this is what is used to display the tariff record content. This is the field for those choosing to file the tariff, rate schedule, contract as a single document This Record Raw Data would apply to sheet, section or total tariff depending on what granularity the filing company has chosen.

Binary?? (10 MB)See questions

None. Binary data. Actual content data.

Required. Submitter will submit in the Valid Data Format ofis <TBD>.The FERC will convert the document submitted to binary.

Does ‘binary’ = native file format with extensions (e.g. WORD = .doc or EXCEL = .xls)?Field size limitation may be problematic – need to address how larger submission will work.Can the headers and footers as they currently exist be included in the Record Raw Data?

Record pPlain Ttext sect_textrecord_text

This is tThe plain text version of the content of the Record rRaw Ddata contents. Formatting and other binary values are stripped from this content. This is the field for those filing tariff sections. If tThis is plain text of the Record raw data contents it shwould apply to sheet, section or total tariff depending on what granularity the filing company has chosen..

Alphanumeric (10 MB).

Free form text. This is not a field that will be submitted by a Company. It is Tthe text extracted by FERC from the Record rRaw dData submitted, e.gi.e. all control codes and special binary characters are removed.

How should certain documents, i.e. maps, be submitted in order for FERC to be able to accomplish this?

Record Change tType change requested

sect_changerecord_change

This A description of bes the type of change being requested.

Character (15) "NEW""CHANGE""CANCELLATION"see instruction manual

Required. The instruction manual should include a list of the valid Record Change Type.

Examples: “NEW""CHANGE""CANCELLATION”Are there other types needed, e.g. “WITHDRAW” or PROFORMA”?

of 50





Associated Filing assoc_filing The previous filing to which the subject filing pertains (i.e. associated).This is used to associate the filing with a previous filing made to FERC. For example, compliance filings and withdrawal filings must identify the previous, applicable filing to which they pertain.

Note that this is used in conjunction with the "assoc_ sectrecord_id" value and the "assoc_option" (below).


Conditional.

This is not applicable to all filing types. Where it is used, it must refer to a previous filing, and the value here should be that previous filing's "filing_id" value.


Same questions as in Filing Data.

Associated Record Identifier

assoc_sect_idassoc_record_id

This is used to associate the specific content with a previous filed content item. For example, withdrawal filings must identify the content being requested to be withdrawn.

Note that this is used in conjunction with the "assoc_filing" value (above) and the "assoc_option" (below).


Conditional. This is not applicable to all filing types. Where it is used, it must refer to a Record ID in previous filing, and the value here should be that data's " sectrecord_id" value.

How does this differ from the Record Identifier and Associated Filing data that is already provided elsewhere (i.e. If the Record Identifier cannot change, and it has already been entered at the beginning of the Record Data, isn’t this a repetition of previously provided info within the same filing event)?

Associated Option Designation

assoc_option An identifier that designates the alternative associated record option being submitted. This is used to associate the specific content with a previous filed content item. For example, withdrawal filings must identify the content being requested to be withdrawn. And since filings can have multiple options, this value must be specified.

Note that this is used in conjunction with the "assoc_filing" value and the "assoc_ sectrecord_id" (above).

Character (1) "A" thru "Z" Conditional – required only when an associated filing is identified. This is not applicable to all filing types. Where it is used, it must refer to correct Option Designation in a previous filing, and the value here should be that previous data's "filing_opt" value.

of 50





Alternative Record Number

alt_sec_num This element added by FERC on its example.

This field is not necessary given the Record Number and the Record Collation Value are formatted as suggested above.

of 50


Reference Tables:

FERC will need to include the following tables: Filing Types, their related codes and required attachments for each type (See Note Below) For each Filing Type – a list of document attachments that can be waived (See Note Below) Cross Reference of Filing Types to Attachment Type Code (See Note Below) Attachment Reference Codes (See Note Below) List of Special Characters that are not valid for the Supporting Document File Name Record Change Types Acceptable File Formats (pulled from the NOTICE OF GUIDELINES FOR SUBMISSION OF CDs,

DVDs, AND OTHER ELECTRONIC MEDIA issued By FERC on April 12, 2007.)

Note: The Pipeline Segment compiled all of this data in one Excel Spreadsheet, which is posted in a separate work paper (work paper 4 of 5). Due to its size, it is best viewed electronically and does not lend itself to easy printing. The information contained within this spreadsheet is based on the eTariff Filing Rules Listing as published on the FERC website. This spreadsheet is preliminary in nature and should be considered a concept of how this reference information could be provided.

of 50


Acceptable File Formats

Description SuffixAdobe Portable Document Format (Acrobat 4.x or higher) .PDFAdvantica SynerGEE compatible Microsoft Access application MDB file Error: Reference source not found .MDBAdvantica SynerGEE input data set for pipe flow program Error: Reference source not found .PDAdvantica SynerGEE xy coordinate text file Error: Reference source not found .XYASCII Comma Separated Value .CSVASCII Text Format .TXTAutoCAD Drawing database Error: Reference source not found .DWGCorel WordPerfect .WPDESRI Shape Format (vector format created by the Environmental System Research Institute) main file 1 .SHPESRI Shape Format (vector format created by the Environmental System Research Institute) index file Error: Reference source not found .SHXESRI Shape Format (vector format created by the Environmental System Research Institute) dBase table Error: Reference source not found .DBFESRI Shape Format (vector format created by the Environmental System Research Institute) projection file Error: Reference source not found .PRJESRI ArcGIS auxiliary file Error: Reference source not found .AUXESRI ArcGIS external pyramid layer file used for rapid display of raster files Error: Reference source not found .RRDESRI ArcMap project file Error: Reference source not found .MXDESRI ArcIMS Project file (ArcXML) Error: Reference source not found .AXLESRI ArcView spatial bin file for shapefiles Error: Reference source not found .SBNESRI ArcView spatial bin index file for shapefiles Error: Referencesource not found .SBXESRI plain text file (world file) used to coordinate raster map images Error: Reference source not found .TWF

ESRI ArcGIS MrSid (LizardTech) image raster file Error: Reference source not found .SIDESRI ArcGIS MrSid georeferencing information (world) file Error: Reference source not found .SDWExtensible Markup Language .XMLGraphic Image Format .GIF

1 A detailed description of the content of the file and instructions for the public on how to obtain resources to view it must be included with the submission in light of National Archives and Records Administration regulations. This file type must only be submitted with Advantica SynerGEE, AutoCAD, ESRI, WinFlow, or WinTran files. of 50


Description SuffixGregg Engineering WinFlow library file Error: Reference source not found .LIBGregg Engineering WinFlow output file Error: Reference source not found .LOGGregg Engineering WinFlow output file Error: Reference source not found .NTPGregg Engineering WinFlow output file Error: Reference source not found .OVRGregg Engineering WinFlow input file Error: Reference source not found .WFPGregg Engineering WinTran time-varying schedule file Error: Reference source not found .SCHGregg Engineering WinTran output file Error: Reference source notfound .WTOGregg Engineering WinTran output file Error: Reference source notfound .WTSJoint Photographic Experts Group .JPGKeyhole Markup Language (xml-based structure for geographic data in an Earth browser such as Google Earth)Error: Reference source not found .KML

Lotus.WK1, .WK3, .WK4

Microsoft Excel .XLSMicrosoft Media Player 2 .WMV, .WMAMicrosoft Power Point .PPT, .PPSMicrosoft Word .DOCMotion Picture Experts Group Error: Reference source not found .MPGMP3 audio file (mp3) Error: Reference source not found .MP3RAW Image File (RGB 24-bit Graphics) .RAWRich Text Format .RTFTagged Image File Format .TIFWaveform sound (Microsoft Windows) Error: Reference source notfound .WAVWeb page file containing Hypertext Markup Language (HTML) markup .HTMWindows bitmap .BMPZip file compressed archive (must not be self-extracting) .ZIP

2 A written transcript and a detailed description of the content of the file must be included with the submission in light of the Americans with Disabilities Act. of 50

Draft eTariff Data Elements and Descriptions · Web viewFollowing is a guide describing the various...

Documents

Transcript of Draft eTariff Data Elements and Descriptions · Web viewFollowing is a guide describing the various...