867 Historical Usage Ver/Rel Implementation Guideline. Pennsylvania New Jersey Delaware Maryland. For Electronic Data Interchange

Transcription

1 Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 867 Historical Usage Ver/Rel Historical Usage (4010) 1 IG867HUv6-2x

2 Table of Contents Summary of Changes... 3 General Notes... 5 Pennsylvania Notes... 6 How to Use the Implementation Guideline X12 Structure Data Dictionary for 867 Historical Usage Segment: ST Transaction Set Header Segment: BPT Beginning Segment for Product Transfer and Resale Segment: N1 Name (8S=LDC Name) Segment: N1 Name (SJ=ESP Name) Segment: N1 Name (G7=Renewable Energy Provider Name) Segment: N1 Name (8R=Customer Name) Segment: REF Reference Identification (11=ESP Account Number) Segment: REF Reference Identification (12=LDC Account Number) Segment: REF Reference Identification (45=LDC Old Account Number) Segment: PTD Product Transfer and Resale Detail (SU=Summary) Segment: QTY Quantity Segment: DTM Date/Time Reference (150=Service Period Date) Segment: DTM Date/Time Reference (151=Service Period Date) Segment: PTD Product Transfer and Resale Detail (RT=Rate) Segment: REF Reference Identification (LO=Load Profile) Segment: REF Reference Identification (NH=LDC Rate Class) Segment: REF Reference Identification (PR=LDC Rate Sub-Class) Segment: QTY Quantity Segment: MEA Measurements Segment: DTM Date/Time Reference (150=Service Period Date) Segment: DTM Date/Time Reference (151=Service Period Date) Segment: PTD Product Transfer and Resale Detail (PM=Meter Detail) Segment: REF Reference Identification (MG=Meter Number) Segment: REF Reference Identification (MT=Meter Type) Segment: REF Reference Identification (NH=LDC Rate Class) Segment: REF Reference Identification (TU=Type of Metering) Segment: QTY Quantity Segment: MEA Measurements Segment: DTM Date/Time Reference (150=) Segment: DTM Date/Time Reference (151=) Segment: PTD Product Transfer and Resale Detail (FG=Scheduling Determinants) Segment: REF Reference Identification (LF=Loss Factor) Segment: REF Reference Identification (LO=Load Profile) Segment: REF Reference Identification (NH=LDC Rate Class) Segment: REF Reference Identification (PR=LDC Rate Sub-Class) Segment: REF Reference Identification (BF=LDC Bill Cycle) Segment: REF Reference Identification (SV=Service Voltage) Segment: REF Reference Identification (MG=Meter Number) Segment: REF Reference Identification (KY=Special Meter Configuration) Segment: QTY Quantity (KC=Peak Load Contribution) Segment: DTM Date/Time Reference (007=PLC Effective Date) Segment: QTY Quantity (KZ=Network Service Peak Load) Segment: SE Transaction Set Trailer Example: Historical Usage Summarized by Account Example: Historical Usage Summarized by Rate Example: Historical Usage Summarized by Meter Example: Historical Usage Requested by Renewable Energy Provider Examples: Pennsylvania, Maryland & New Jersey Net Metering / Customer Generation Examples: Pennsylvania Effective Dates for PLC/NSPL Historical Usage (4010) 2 IG867HUv6-2x

3 Summary of Changes June 29, 1999 Version 1.0 July 21, 1999 Version 1.0a October 1, 1999 Version 1.0c November 4, 1999 Version 1.1 December 23, 1999 Draft version 1.1MD1 January 17, 2000 Draft version 1.1MD2 February 24, 2000 Version 1.1MD3 March 31, 2000 Version 1.1MD4 May 14, 2000 Version 1.2 August 11, 2000 Version 1.2a September 10, 2000 Version 1.3 October 19, 2001 Version 1.3rev01 December 13, 2001 Version 1.3rev02 January 9, 2002 Version 2.0 December 10, 2003 Version May 12, 2004 Version Initial Release. Changes made since last draft: Changed EGS to ESP and EDC to LDC throughout the guideline. Added notes page with LDC Definitions and ESP Definitions. Added How to use the implementation guideline page. In addition, changed all headers to the true X12 definition. Also corrected the Table on Page 4 to reflect X12 definitions and added the words "X12 Structure to the title on that page. Added Note for New Jersey to indicate all utilities plan to send summarized data by account (SU loop). No utility plans to send the data by meter (PM loop) Added note to clarify the utility will send the current transmission obligation and capacity obligation values. Historical Capacity and Transmission obligation is NOT being sent via this transaction. Corrected words in Example for transmission and capacity obligation. Added clarifying comment to SU loop to indicate there should be one SU loop for each unit of measurement (applies to all states). Added Delaware Delmarva Information Moved rules from the data dictionary to the Notes section of the implementation guide. Clarified the PTD loops to indicate that there must be one loop per unit of measure. Clarifications to several NJ Use items. Clarification to examples. This is a FINAL version for Pennsylvania and New Jersey Add Maryland use to document the changes were added to the version 1.1 of the regional standards Added Data Dictionary Added Table of Contents Clarified REF*45 only used when LDC sending transaction. Clarified use of Old Acct Number (REF*45) for MD Clarified use of FG loop for MD Add load profile and LDC rate code to FG loop for MD future use This transaction is considered FINAL for Maryland This document is a new finalized version of PA and MD. NJ is still using Version 1.1. Indicate PSEG will use the PTD01=PM loop, rather than the PTD01=SU loop. This transaction is a new FINAL version for Pennsylvania, New Jersey, Maryland, and Delaware (Delmarva only). Incorporate Delaware Electric Coop (DEC) information for Delaware Incorporate PA Change Control 028 change REF*11 from optional to conditional if supplier of record is requesting usage Incorporate NJ Change Control to allow sending of LDC rate code and LDC load Profile in the FG loop. Incorporate DE Change Control to allow sending of LDC rate code and LDC load Profile in the FG loop. Indicate not used by DEC. This transaction is a new FINAL version for Pennsylvania, New Jersey, Maryland, and Delaware. Incorporate changes for NJ add TOU values to both PTD*SU and PTD*PM loops. FG loop make REF*NH required, add optional REF*BF. Add REF*TU to PTD*PM loop. Incorporate changes for PA Change Control 040. This allows TOU information to be provided optionally. 867 Historical Usage (4010) 3 IG867HUv6-2x

4 January 20, 2006 Version 2-0-3D October 23, 2006 Version 2-0-4D November 3, 2006 Version 2-0-5D February 12, 2007 Version 2-0-6F July 4, 2009 Version 2-0-8D January 24, 2010 Version 2.1 November 4, 2010 Version 2.1.1D February 28, 2011 Version 3.0 February 16, 2012 Version 3.01 March 8, 2013 Version 6.0 March 17, 2014 Version 6.1 Incorporate NJ Change Control 005 (NJ CleanPower program changes) Incorporate NJ Change Control 006 to reflect current practices Incorporate PA Change Control 043 (Add K4 kilovolt amperes) Incorporate NJ Change Control 009 (NJ Clean Power RECO unmetered) Incorporate NJ Change Control 011 (Clarify PSEG use of LDC Rate Type) Incorporate NJ Change Control 012 (Change Billing Cycle (REF*BF) to indicate it will be required for all utilities. PSEG and RECO will be implementing in 1Q 2007). Considered FINAL for PA and NJ Incorporate NJ Change Control PSEG-E-HU (Indicate PSEG will send SU loop, will send REF*NH in FG loop) Incorporate PA Change Control 049 (PTD*FG, QTY*KC, QTY*KZ required for PJM participants)incorporate PA Change Control 052 (REF*BF required for PJM participants) Incorporate PA Change Control 053 (REF*NH required for PJM participants) Incorporate PA Change Control 054 (REF*LO required for PJM participants) Incorporate PA Change Control 055 (PECO modifications RT loop) Incorporate MD Change Control RM17-HU This transaction is a new FINAL version for Pennsylvania, New Jersey, Maryland, and Delaware. Incorporate PA Change Control 65 (REF*LF and REF*SV required for First Energy) Incorporate PA Change Control 71 (add QTY01=KA as optional) Incorporate MD Change Control Admin (Admin/Cleanup for MD) This transaction is a new FINAL version for Pennsylvania, New Jersey, Maryland, and Delaware. Incorporate PA Change Control 081 (Clarify RT loop) Incorporate PA Change Contorl 085 (REF*KY) Incorporate PA Change Control 090 (REF03 in REF*KY) Incorporate PA Change Control 093 (admin updates) Incorporate MD Change Control 008 (clarify PEPCO HU/HI support) Incorporate MD Change Control 010 (PEPCO AMI Support) Moving to v6.0 to align versions across all transaction sets Cleaned up references to Allegheny and APS throughout document Incorporate PA Change Control 087 (add DTM segments to be used with QTY*KC and QTY*KZ to denote current and future values) Incorporate PA Change Control 095 (REF03 in REF*KY) Incorporate PA Change Control 101 (remove AMT*LD from request; rescinds CC 58) Incorporate PA Change Control 102 (increase REF*BF length in Data Dictionary) Incorporate PA Change Control 103 (uniform net meter consumption reporting) Incorporate MD Change Control 014 (make REF*LF & REF*SV same as PA) Incorporate PA Change Control 114 (add REF*PR to PTD*FG & PTD*RT loops) Incorporate MD Change Control 026 (PHI new CIS; changes to 867HU) Incorporate MD Change Control 029 (uniform net meter data reporting) Incorporate MD Change Control 030 (Net Meter Indicator in REF*KY) Incorporate NJ Change Control Electric 015 (Net Meter Indicator in REF*KY) Incorporate NJ Change Control Electric 016 (uniform net meter data reporting) Incorporate NJ Change Control Electric 019 (ACE new CIS: changes to 867HU/HI) Incorporate NJ Change Control Electric 028 (clarify RECO support of 867HU) Incorporate NJ Change Control Electric 031 (RECO removal from IG) Incorporate NJ Change Control Electric 032 (PSE&G admin updates) Incorporate NJ Change Control Electric 035 (REF*MG in PTD*FG to Optional) Incorporate MD Change Control 037 (clean up MD notes section) 867 Historical Usage (4010) 4 IG867HUv6-2x

5 General Notes Use Historical Usage will be provided to an ESP upon Request. The request will be made using the 814E and 814HU documents. Historical Usage can be requested for an entity that is already a customer of the ESP Historical Usage can be requested for any customer that has not restricted the release of their historical usage. This is state dependent, some states allow this scenario, others do not. The Historical Usage Transaction Set is sent by the LDC only one time per ESP request. No corrections or changes will be transmitted. The Historical Usage data is correct for the point in time that is it requested. Subsequent adjustments to Historical Usage will not be transmitted to the ESP. LDC Definitions: ESP Definitions: Renewable Energy Provider Definition: If providing history totalized for an account, use "SU" (Summary) in PTD01, else if providing history by meter, use "PM" (Physical Meter) in PTD01. The term LDC (Local Distribution Company) in this document refers to the utility. Each state may refer to the utility by a different acronym: EDC Electric Distribution Company (Pennsylvania, Delaware) LDC Local Distribution Company (New Jersey) EC Electric Company (Maryland) The term ESP (Energy Service Provider) in this document refers to the supplier. Each state may refer to the supplier by a different acronym: EGS Electric Generation Supplier (Pennsylvania) TPS Third Party Supplier (New Jersey) ES Electric Supplier (Delaware) ES Electricity Supplier (Maryland) The term Renewable Energy Provider in this document refers to the party that provides Renewable Energy Credits (RECs). This party does not provide generation to the account. Each state may refer to the Renewable Energy Provider by a different acronym: GPM Green Power Marketer (New Jersey) Note: The transaction will either have an ESP or a Renewable Energy Provider, but not both. 867 Historical Usage (4010) 5 IG867HUv6-2x

6 Pennsylvania Notes The Pennsylvania default is 12 months of Historical Usage, the following EDCs offer more than 12 months a. PECO default is 24 months Requirements for uniform support of Net Metered Customers SU (Account Services Summary) Loop reports consumption summarized/totalized for account by unit of measure for net metered customers. (First Energy, PPL, and UGI support) 1. When the customer s consumption is greater than generation for a given service period, the KH will be reported as net consumption (QTY01 w/actual = QD or estimated = KA) with the total generation subtracted from total consumption. 2. When the customer s generation is greater than consumption for a given service period, the KH will be reported as net generation (actual = 87 or estimated = 9H) with the total consumption subtracted from total generation). 3. In either scenario, the QTY02 will never be signed negative. RT (Rate) Loop reports consumption summarized/totalized by rate and by unit of measure for net metered customers. (PECO supports) 1. When the customer s consumption is greater than generation for a given service period, the KH will be reported as net consumption (QTY01 w/actual = QD or estimated = KA) with the total generation subtracted from total consumption. 2. When the customer s generation is greater than consumption for a given service period, the KH will be reported as net generation (actual = 87 or estimated = 9H) with the total consumption subtracted from total generation). 3. In either scenario, the QTY02 will never be signed negative. PM (Meter Detail) Loop reports consumption provided by meter by unit of measure for net metered customers: (Duquesne only) 1. Single meter reporting both in and out flow. a. When the customer s consumption is greater than generation for a given service period, the KH will be reported as net consumption (QTY01 w/actual = QD or estimated = KA) with the total generation subtracted from total consumption. b. When the customer s generation is greater than consumption for a given service period, the KH will be reported as net generation (actual = 87 or estimated = 9H) with the total consumption subtracted from total generation). c. In either scenario, the QTY02 will never be signed negative. 867 Historical Usage (4010) 6 IG867HUv6-2x

7 Demand Maryland Notes Measured/Billed Demand add note to Demand segment to indicate PE, BGE, Pepco and Delmarva do not store measured demand, and will send Billed demand. Historical Interval Usage Historical Usage Reporting Maryland EDI CC 15 added support of the EDI 867 Historical Interval (HI) transaction for Maryland. As of 1/28/13 the actual implementation dates have yet to be determined or if the historical data will be provided at the account or meter level for all ECs. BG&E Note: If this is a Historical Usage (HU) request for an interval account, the response will be accepted with a status of SNP. This informs the supplier that the historical interval data is available on the web. If this is a Historical Usage (HU) request for a non-interval account, the response will be accepted and the historical usage will be provided via an 867HU. As of January 16, 2014 BGE supports EDI requests for pre-enrollment historical data Delmarva MD & PEPCO MD Note: Effective with new CIS, the supplier will receive 867HU for non-interval billed accounts and the 867HI for interval billed accounts. Historical Usage requests will be processed as follows: LIN05 Scenario REF1P Code 867 Action LIN05 = HU available on non-interval account No REF1P sent 867HU sent HU LIN05 = HU not available REF1P = HUU No 867 sent HU LIN05 = HI HI available No REF1P sent 867HI sent LIN05 = HI Neither historical interval detail or REF1P = HIU No 867 sent summary data available LIN05 = HI HI data unavailable BUT summary HU No REF1P sent 867HU sent data is available LIN05 = HI HI request on non-interval account No REF1P sent 867HU sent Potomac Edison Note: PE will provide an 867HU (Monthly Historical Information) for all Historical usage (HU) requests. Requests for historical interval data must be made outside of EDI. Historical Usage Reporting Level Providing historical monthly data o Delmarva, PEPCO, Potomac Edison & BGE totalized to account level (PTD*SU loop) Net Meter Data Reporting Requirements Maryland EDI Change Control 029 adopted uniform net meter data reporting for Maryland. Utility support as of December 2014 BGE est. by end of 1Q 2015 PHI (Delmarva & PEPCO) with new CIS Potomac Edison (FE) by end of 2Q 2015 (IU/HIU) 867 Historical Usage (4010) 7 IG867HUv6-2x

8 Net Meter Data Reporting Requirements (Cont.) SU (Account Services Summary) Loop reports consumption summarized/totalized for account by unit of measure for net metered customers. (Delmarva, PEPCO, Potomac Edison and BGE) 1. When the customer s consumption is greater than generation for a given service period, the KH will be reported as net consumption (QTY01 w/actual = QD or estimated = KA) with the total generation subtracted from total consumption. 2. When the customer s generation is greater than consumption for a given service period, the KH will be reported as net generation (actual = 87 or estimated = 9H) with the total consumption subtracted from total generation). 3. In either scenario, the QTY02 will never be signed negative. 867 Historical Usage (4010) 8 IG867HUv6-2x

9 New Jersey Notes Historical Usage Information Atlantic City Electric: Effective with new CIS, the supplier will receive 867HU for noninterval billed accounts and the 867HI for interval billed accounts. Historical Usage requests will be processed as follows: LIN05 Scenario REF1P Code 867 Action LIN05 = HU available on non-interval account No REF1P sent 867HU sent HU LIN05 = HU not available REF1P = HUU No 867 sent HU LIN05 = HI HI available No REF1P sent 867HI sent LIN05 = HI Neither historical interval detail or REF1P = HIU No 867 sent summary data available LIN05 = HI HI data unavailable BUT summary HU No REF1P sent 867HU sent data is available LIN05 = HI HI request on non-interval account No REF1P sent 867HU sent Rockland Electric Company: follows the New York EDI 867 Historical Usage standard. The NY standard does not include PTD*FG loop which is required for the other NJ electric utilities in PJM. Rockland Electric sends PLC in REFPR segment of BQ loop NSPL is provided manually upon request, contact Rockland Electric for details Net Meter Data Reporting Requirements NJ EDI Change Control Electric 016 mandates specific data requirements in support of net metered customers. Implementation by utility as follows o Atlantic City Electric with new CIS (est. early 2015) o JCP&L 4Q 2014 (867MU/HU) and 1Q 2015 (867IU) o PSE&G currently supported, see below for additional PSE&G notes SU (Account Services Summary) Loop reports consumption summarized/totalized for account by unit of measure for net metered customers. (used by Atlantic City Electric JCP&L) 1. When the customer s consumption is greater than generation for a given service period, the KH will be reported as net consumption (QTY01 w/actual = QD or estimated = KA) with the total generation subtracted from total consumption. 2. When the customer s generation is greater than consumption for a given service period, the KH will be reported as net generation (actual = 87 or estimated = 9H) with the total consumption subtracted from total generation). 3. In either scenario, the QTY02 will never be signed negative. SU (Account Services Summary) Loop reporting both consumption and billed usage for net metered customers. (used by PSE&G Only) 1. Reports customer s billed usage in the QTY01 = QD. This value is the billed usage amount which is the net of the generation/consumption.. 2. Reports customer s actual KH consumption in the MEA segment. The QTY01 less the MEA03 = customer s generation KH. 3. In either location (QTY02/MEA03) the value will never be signed negative. 867 Historical Usage (4010) 9 IG867HUv6-2x

10 How to Use the Implementation Guideline Segment: REF Reference Identification Position: 030 Loop: LIN Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Notes: PA Use: NJ Use: Example: Recommended by UIG Must be identical to account number as it appears on the customer s bill, excluding punctuation (spaces, dashes, etc.). Significant leading and trailing zeros must be included. Request: Accept Response: Reject Response: Same as PA REF*12* Required Required Required The Notes: section generally contains notes by the Utility Industry Group (UIG). This section is used to show the individual State s Rules for implementation of this segment. One or more examples. This section is used to show the X12 Rules for this segment. You must look further into the grayboxes below for State Rules. Des. Element Name X12 Attributes Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 12 Billing Account LDC-assigned account number for end use customer. Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier This column shows the use of each data element. If state rules differ, this will show Conditional and the conditions will be explained in the appropriate grayboxes. These are X12 code descriptions, which often do not relate to the information we are trying to send. Unfortunately, X12 cannot keep up with our code needs so we often change the meanings of existing codes. See graybox for the UIG or state definitions. This column shows the X12 attributes for each data element. Please refer to Data Dictionary for individual state rules. M = Mandatory, O= Optional, X = Conditional AN = Alphanumeric, N# = Decimal value, ID = Identification, R = Real 1/30 = Minimum 1, Maximum Historical Usage (4010) 10 IG867HUv6-2x

11 867 Historical Usage X12 Structure Functional Group ID=PT Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 ST Transaction Set Header M 1 Must Use 020 BPT Beginning Segment for Product Transfer and M 1 Resale LOOP ID - N N1 Name O REF Reference Identification O 12 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - PTD >1 Must Use 010 PTD Product Transfer and Resale Detail M REF Reference Identification O 20 LOOP ID - QTY >1 110 QTY Quantity O MEA Measurements O DTM Date/Time Reference O 10 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - CTT CTT Transaction Totals O 1 n1 Must Use 030 SE Transaction Set Trailer M 1 Transaction Set Notes 1. The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is the sum of the value of quantities (QTY02) for each QTY segment. 867 Historical Usage (4010) 11 IG867HUv6-2x

12 Data Dictionary for 867 Historical Usage Appl Field Field Name Description EDI Element Loop / Related EDI Qualifier Data Type 1 Purpose Code Transaction Set Purpose BPT01 = 52 X(2) 2 Transaction Unique Number identifying this BPT02 X(30) Reference Number transaction. 3 System Date Date this transaction was generated BPT03 9(8) from sender's system 4 Report Type Code Code to identify this transaction BPT04 = DD BPT01 = 52 X(2) contains detailed usage information 5 LDC Name LDC's Name N102 N1: N101 = 8S X(60) 6 LDC Duns LDC's DUNS Number or DUNS+4 Number N104 N1: N101 = 8S N103 = 1 or 9 X(13) 7 ESP Name ESP's Name N102 N1: N101 = SJ X(60) 8 ESP Duns ESP's DUNS Number or DUNS+4 N104 N1: N101 = SJ X(13) Number N103 = 1 or Renewable Energy Provider Name Renewable Energy Provider 's Name N102 N1: N101 = G7 X(60) 8.4 Renewable Energy Provider Duns Renewable Energy Provider 's DUNS Number or DUNS+4 Number N104 N1: N101 = G7 N103 = 1 or 9 X(13) 9 Customer Name Customer Name N102 N1: N101 = 8R X(60) 10 ESP Account ESP Customer Account Number REF02 N1: N101 = 8R X(30) Number REF01 = LDC Account LDC Customer Account Number REF02 N1: N101 = 8R X(30) Number REF01 = LDC Account LDC Customer Account Number REF03 N1: N101 = 8R X(80) Number - unmetered Unmetered REF01 = Old Account Number Previous LDC Customer Account Number REF02 REF03 = U N1: N101 = 8R REF01 = 45 PTD Loop for Historical Usage that is Summarized/Totalized by Account (PTD01 = SU) A PTD Loop will be provided for each type of consumption measured for the overall account (PTD01=SU) or by meter (PTD01 = PM) or by rate (PTD01=RT) in addition to the PTD loop that provides Scheduling Determinants when appropriate X(30) 13 Loop Identification Indicates if usage is provided totalized PTD01 = SU X(2) or by meter Quantity Qualifier Represents whether the quantity is QTY01 X(2) actual or estimated: KA = Estimated Quantity Delivered QD = Actual Quantity Delivered 87 = Actual Quantity Received (Net Meter) 9H = Estimated Quantity Received (Net Meter) 13.2 Quantity Delivered Represents quantity of consumption QTY02 9(15) delivered for billing period Quantity Delivered Indicates unit of measurement for QTY03 X(2) Unit of Measurement quantity of consumption delivered during billing period. 867 Historical Usage (4010) 12 IG867HUv6-2x

13 13.4 Consumption Represents quantity of consumption delivered for service period. Contains the difference in the meter readings (or as measured by the meter) multiplied by various factors, excluding Power Factor. MEA03 MEA02 = PRQ 9(9).9(4) 13.5 Unit of Measure Unit of measure for readings. MEA04 X(2) 13.6 Measurement Significance Code Code used to benchmark, qualify, or further define a measurement value. MEA07 X(2) 13.7 Start date of the period for which these readings are provided 13.8 End date of the period for which these readings are provided DTM02 QTY: DTM01 = 150 X(8) DTM02 QTY: DTM01 = 151 X(8) PTD Loop for Historical Usage that is Summarized/Totalized by Rate (PTD01 = RT) A PTD Loop will be provided for each type of consumption measured for the overall account (PTD01=SU) or by meter (PTD01 = PM) or by rate (PTD01=RT) in addition to the PTD loop that provides Scheduling Determinants when appropriate 15.1 Loop Identification Indicates if usage is provided totalized or by meter. PTD01 = RT X(2) 15.2 Profile Group A code for the Load Profile used for this REF02 PTD: REF01= LO X(30) rate. Differs by LDC. Codes posted on LDC s Web site LDC Rate Code Code indicating the rate a customer is being charged by LDC per tariff. Codes posted on LDC s Web site REF02 PTD: REF01= NH X(30) 15.4 LDC Rate Sub-Class Code to provide further classification of REF02 PTD: REF01= PR X(30) LDC Rate Code 15.5 Quantity Qualifier Represents whether the quantity is QTY01 X(2) actual or estimated: KA = Estimated Quantity Delivered QD = Actual Quantity Delivered 87 = Actual Quantity Received (Net Meter) 9H = Estimated Quantity Received (Net Meter) 15.6 Quantity Delivered Represents quantity of consumption QTY02 QTY01 9(15) delivered for billing period Quantity Delivered Indicates unit of measurement for QTY03 X(2) Unit of Measurement quantity of consumption delivered during billing period Consumption Represents quantity of consumption MEA03 MEA02 = PRQ 9(9).9(4) delivered for service period. Contains the difference in the meter readings (or as measured by the meter) multiplied by various factors, excluding Power Factor Unit of Measure Unit of measure for readings. MEA04 X(2) Measurement Significance Code Code used to benchmark, qualify, or further define a measurement value Start date of the period for which these readings are provided MEA07 X(2) DTM02 QTY: DTM01 = 150 X(8) 867 Historical Usage (4010) 13 IG867HUv6-2x

14 15.12 End date of the period for which these readings are provided DTM02 QTY: DTM01 = 151 X(8) PTD Loop for Historical Usage that is provided by Meter (PTD01 = PM) A PTD Loop will be provided for each type of consumption measured for the overall account (PTD01=SU) or by meter (PTD01 = PM) or by rate (PTD01=RT) in addition to the PTD loop that provides Scheduling Determinants when appropriate 21 Loop Identification Indicates if usage is provided totalized or by meter. 22 Meter Number Serial number of this specific meter (may have multiple meters) 23 Meter Type Code indicating type of consumption measured & interval at which measurements are taken. 24 Type of metering used for billing Indicates the type of metering information that will be sent on the 867 transaction Quantity Qualifier Represents whether the quantity is actual or estimated: KA = Estimated Quantity Delivered QD = Actual Quantity Delivered 87 = Actual Quantity Received (Net Meter) 9H = Estimated Quantity Received (Net Meter) 25 Quantity Delivered Represents quantity of consumption delivered for billing period. 26 Quantity Delivered Indicates unit of measurement for Unit of Measurement quantity of consumption delivered during billing period. PTD01 = PM X(2) REF02 PTD: REF01 = MG X(30) REF02 PTD: REF01 = MT X(5) REF02= 41 (off peak) 42 (on peak) 43 (intermediate) or 51 (totalizer) QTY01 NM1: REF01 = TU REF03 = Meter Type (See REF*MT) X(2) X(2) QTY02 QTY01 9(15) QTY03 27 Consumption Represents quantity of consumption MEA03 MEA02 = PRQ 9(9).9(4) delivered for service period. Contains the difference in the meter readings (or as measured by the meter) multiplied by various factors, excluding Power Factor. 28 Unit of Measure Unit of measure for readings. MEA04 X(2) X(2) 29 Measurement Significance Code Code used to benchmark, qualify, or further define a measurement value. MEA07 X(2) 30 Start date of the period for which these readings are provided 31 End date of the period for which these readings are provided DTM02 QTY: DTM01 = 150 X(8) DTM02 QTY: DTM01 = 151 X(8) This PTD provides Scheduling Determinants when appropriate PTD Loop for Scheduling Determinants (PTD01 = FG) 867 Historical Usage (4010) 14 IG867HUv6-2x

15 32 Loop Identification Indicates if usage is provided totalized PTD01 = FG X(2) or by meter. 33 Loss Factor Loss Factor REF02 PTD:REF01=LF X(30) 34 Profile Group A code for the Load Profile used for this customer. Differs by LDC. Codes posted on LDC s Web site. 35 LDC Rate Code Code indicating the rate a customer is being charged by LDC per tariff. Codes posted on LDC s Web site 36 LDC Rate Sub-Class Code to provide further classification of LDC Rate Code 37 LDC Billing Cycle LDC Cycle on which the bill will be rendered REF02 PTD: REF01= LO X(30) REF02 PTD: REF01= NH X(30) REF02 PTD: REF01= PR X(30) REF02 PTD: REF01= BF X(4) 38 Service Voltage Service voltage REF02 PTD:REF01=SV X(30) 39 Meter Number Meter Number REF02 PTD: REF01=MG X(2) 40 Special Meter Configuration Code 41 Special Meter Configuration Information Used to convey there s a special meter present on the account. For example, Net Metering PPLEU-used to report the max K1 (demand) the special meter supports REF02 LIN: REF01 = KY X(3) REF03 LIN: RF01 = KY X(80) 42 Peak Load Contribution Peak load contributions provided to PJM for Installed Capacity calculation (coincident with PJM Peak). 43 Unit of Measure Indicates unit of measurement for quantity of consumption delivered during billing period. 44 Network Service Peak Load Customer's peak load contribution provided to PJM for the Transmission Service calculation (coincident with LDC peak). 45 Quantity Delivered Indicates unit of measurement for Unit of Measurement quantity of consumption delivered during billing period. QTY02 PTD: QTY01 = KC 9(15) QTY03 = K1 PTD: QTY01 = QD X(2) QTY02 PTD: QTY01 = KZ 9(15) QTY03 = K1 PTD: QTY01 = QD X(2) 867 Historical Usage (4010) 15 IG867HUv6-2x

16 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: ST*867* Must Use ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 867 Product Transfer and Resale Report Must Use ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 867 Historical Usage (4010) 16 IG867HUv6-2x

17 Segment: BPT Beginning Segment for Product Transfer and Resale Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit identifying data Syntax Notes: 1 If either BPT05 or BPT06 is present, then the other is required. Semantic Notes: 1 BPT02 identifies the transfer/resale number. 2 BPT03 identifies the transfer/resale date. 3 BPT08 identifies the transfer/resale time. 4 BPT09 is used when it is necessary to reference a Previous Report Number. PA Use: NJ Use: DE Use: MD Use: Example: Required Required Required Required BPT*52* * *DD Must Use BPT Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 52 Response to Historical Inquiry Response to a request for historical meter reading. Must Use BPT Reference Identification O AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier A unique transaction identification number assigned by the originator of this transaction. This number should be unique over all time. Must Use BPT Date M DT 8/8 Date (CCYYMMDD) The transaction creation date the date that the data was processed by the application system. Must Use BPT Report Type Code O ID 2/2 Code indicating the title or contents of a document, report or supporting item DD Distributor Inventory Report Usage 867 Historical Usage (4010) 17 IG867HUv6-2x

18 Segment: N1 Name (8S=LDC Name) Position: 080 Loop: N1 Level: Heading Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: N1*8S*LDC COMPANY*1* Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual 8S Consumer Service Provider (CSP) LDC Must Use N Name X AN 1/60 Free-form name LDC Company Name Must Use N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix Must Use N Identification Code X AN 2/20 Code identifying a party or other code LDC D-U-N-S Number or D-U-N-S + 4 Number 867 Historical Usage (4010) 18 IG867HUv6-2x

19 Segment: N1 Name (SJ=ESP Name) Position: 080 Loop: N1 Level: Heading Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: N1*SJ*ESP COMPANY*9* ESP1 Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual SJ Service Provider ESP Must Use N Name X AN 1/60 Free-form name ESP Company Name Must Use N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix Must Use N Identification Code X AN 2/20 Code identifying a party or other code ESP D-U-N-S Number or D-U-N-S + 4 Number 867 Historical Usage (4010) 19 IG867HUv6-2x

20 Segment: N1 Name (G7=Renewable Energy Provider Name) Position: 080 Loop: N1 Level: Heading Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. PA Use: Not used NJ Use: Required DE Use: Not used MD Use: Not used Example: N1*G7*RENEWABLE COMPANY*9* GPM Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual G7 Entity Providing the Service Renewable Energy Provider Must Use N Name X AN 1/60 Free-form name Renewable Energy Provider Company Name Must Use N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix Must Use N Identification Code X AN 2/20 Code identifying a party or other code Renewable Energy Provider D-U-N-S Number or D-U-N-S + 4 Number 867 Historical Usage (4010) 20 IG867HUv6-2x

21 Segment: N1 Name (8R=Customer Name) Position: 080 Loop: N1 Level: Heading Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: N1*8R*JANE DOE Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual 8R Consumer Service Provider (CSP) Customer End Use Customer Must Use N Name X AN 1/60 Free-form name Customer Name as it appears on the customer s bill 867 Historical Usage (4010) 21 IG867HUv6-2x

22 Segment: REF Reference Identification (11=ESP Account Number) Position: 120 Loop: N1 Level: Heading Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. PA Use: Conditional: Required if it was previously provided on an 814 to the LDC and the ESP is the supplier of record. NJ Use: Optional if it was previously provided on an 814 to the LDC and the ESP is the supplier of record. DE Use: Conditional: Required if it was previously provided on an 814 to the LDC and the ESP is the supplier of record. MD Use: Optional if it was previously provided on an 814 to the LDC and the ESP is the supplier of record. Example: REF*11* Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 11 Account Number ESP-assigned account number for end use customer. Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 867 Historical Usage (4010) 22 IG867HUv6-2x

23 Segment: REF Reference Identification (12=LDC Account Number) Position: 120 Loop: N1 Level: Heading Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. PA Use: NJ Use: DE Use: MD Use: Example: Required - Must be identical to account number as it appears on the customer s bill, excluding punctuation (spaces, dashes, etc.). Significant leading and trailing zeros must be included. Same as PA Same as PA Same as PA REF*12* Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 12 Billing Account LDC-assigned account number for end use customer. Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 867 Historical Usage (4010) 23 IG867HUv6-2x

24 Segment: REF Reference Identification (45=LDC Old Account Number) Position: 120 Loop: N1 Level: Heading Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. PA Use: Required if account number changed in the last 60 days. Note: Only used when LDC is sending this transaction. NJ Use: Same as PA DE Use: MD Use: Example: by BGE, PEPCO, or Delmarva. PE: Required if the account number has changed in the last 60 days. REF*45* Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 45 Old Account Number LDC s previous account number for the end use customer. Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 867 Historical Usage (4010) 24 IG867HUv6-2x

25 Segment: PTD Product Transfer and Resale Detail (SU=Summary) Position: 010 Loop: PTD Usage: Mandatory Max Use: 1 Purpose: To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data Syntax Notes: 1 If either PTD02 or PTD03 is present, then the other is required. 2 If either PTD04 or PTD05 is present, then the other is required. Semantic Notes: PA Use: NJ Use: Required if providing Historical Usage summarized/totalized by account. There must be one loop for each unit of measurement. Same as PA DE Use: MD Use: Examples: Same as PA Same as PA PTD*SU Must Use PTD Product Transfer Type Code M ID 2/2 Code identifying the type of product transfer SU Summary Consumption Summarized/Totalized for Account by unit of measure. 867 Historical Usage (4010) 25 IG867HUv6-2x

26 Segment: QTY Quantity Position: 110 Loop: QTY Max Use: 1 Purpose: To specify quantity information Syntax Notes: 1 At least one of QTY02 or QTY04 is required. 2 Only one of QTY02 or QTY04 may be present. Semantic Notes: 1 QTY04 is used when the quantity is non-numeric. Notes: Each QTY/MEA/DTM loop conveys consumption information about one metering period. PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: QTY*QD*5210*KH Must Use QTY Quantity Qualifier M ID 2/2 Code specifying the type of quantity KA Estimated Quantity Delivered Used when the quantity delivered is an estimated quantity. QD Actual Quantity Delivered Used when the quantity delivered is an actual quantity. 87 Actual Quantity Received (Net Metering) Used when the net generation quantity received is actual. 9H Estimated Quantity Received (Net Metering) Used when the net generation quantity received is estimated. Must Use QTY Quantity X R 1/15 Numeric value of quantity Must Use QTY Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken K1 Kilowatt Demand (KW) Represents potential power load measured at predetermined intervals K2 Kilovolt Amperes Reactive Demand (KVAR) Reactive power that must be supplied for specific types of customer's equipment; billable when kilowatt demand usage meets or exceeds a defined parameter K3 Kilovolt Amperes Reactive Hour (KVARH) Represents actual electricity equivalent to kilowatt hours; billable when usage meets or exceeds defined parameters K4 Kilovolt Amperes (KVA) KH Kilowatt Hour (KWH) 867 Historical Usage (4010) 26 IG867HUv6-2x

27 Segment: MEA Measurements Position: 160 Loop: QTY Max Use: 40 Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001) Syntax Notes: 1 At least one of MEA03 MEA05 MEA06 or MEA08 is required. 2 If MEA05 is present, then MEA04 is required. 3 If MEA06 is present, then MEA04 is required. 4 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required. 5 Only one of MEA08 or MEA03 may be present. Semantic Notes: 1 MEA04 defines the unit of measure for MEA03, MEA05, and MEA06. 1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value. Notes: PA Use: NJ Use: DE Use: MD Use: Examples: The MEA segment is sent for each QTY loop. The MEA will indicate the time of use that applies to the QTY. If meter readings are included in the MEA, they will indicate the time of use that the meter readings apply to. Optional field for time of use other than totalizer (MEA07=51). Optional for time of use equal to totalizer (MEA07=51) if that is the only time of use on the account. Must use for time of use other than totalizer (MEA07=51). Optional for time of use equal to totalizer (MEA07=51) if that is the only time of use on the account. Note: For PSE&G net metered customer, the customer s actual KH consumption is reported in the MEA03. The MEA03 less the QTY02 equals customer generation. MEA**PRQ*14*K1***51 (If meter measures multiple things, you need to send multiple QTY loops, one for each unit of measurement). Must Use MEA Measurement Qualifier O ID 1/3 Code identifying a specific product or process characteristic to which a measurement applies PRQ Consumption Must Use MEA Measurement Value X R 1/20 The value of the measurement Represents quantity of consumption delivered for service period. Contains the difference in the meter readings (or as measured by the meter) multiplied by Must Use MEA various factors, excluding Power Factor. Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken K1 Kilowatt Demand Represents potential power load measured at predetermined intervals K2 Kilovolt Amperes Reactive Demand Reactive power that must be supplied for specific types of customer's equipment; billable when kilowatt demand usage meets or exceeds a defined parameter K3 Kilovolt Amperes Reactive Hour 867 Historical Usage (4010) 27 IG867HUv6-2x

28 Represents actual electricity equivalent to kilowatt hours; billable when usage meets or exceeds defined parameters K4 Kilovolt Amperes (KVA) K5 Kilovolt Amperes Reactive KH Kilowatt Hour Must Use MEA Measurement Significance Code O ID 2/2 Code used to benchmark, qualify or further define a measurement value 41 Off Peak 42 On Peak 43 Intermediate 51 Total Totalizer 66 Shoulder 867 Historical Usage (4010) 28 IG867HUv6-2x

29 Segment: DTM Date/Time Reference (150=Service Period Date) Position: 210 Loop: QTY Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: DTM*150* Must Use DTM Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 150 Must Use DTM Date X DT 8/8 Date expressed as CCYYMMDD 867 Historical Usage (4010) 29 IG867HUv6-2x

30 Segment: DTM Date/Time Reference (151=Service Period Date) Position: 210 Loop: QTY Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: PA Use: Required NJ Use: Required DE Use: Required MD Use: Required Example: DTM*151* Must Use DTM Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 151 Must Use DTM Date X DT 8/8 Date expressed as CCYYMMDD 867 Historical Usage (4010) 30 IG867HUv6-2x

31 Segment: PTD Product Transfer and Resale Detail (RT=Rate) Position: 010 Loop: PTD Usage: Mandatory Max Use: 1 Purpose: To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data Syntax Notes: 1 If either PTD02 or PTD03 is present, then the other is required. 2 If either PTD04 or PTD05 is present, then the other is required. Semantic Notes: PA Use: NJ Use: DE Use: MD Use: Examples: Required if providing Historical Usage summarized/totalized by rate. Note: Different rates may have different bill periods. PTD*RT Must Use PTD Product Transfer Type Code M ID 2/2 Code identifying the type of product transfer RT Rate Consumption Summarized/Totalized for Rate. 867 Historical Usage (4010) 31 IG867HUv6-2x