Round 2 Sampling Review

Download Report

Transcript Round 2 Sampling Review

Load Research Project
Review of Processes for
Round 2 Sampling
Presented by ERCOT Staff
To the Profiling Working Group Meeting
On April 24, 2007
LRS Topics to Review
 VEE Standards
 Sample Point Replacement Rules and Process
 Oil/Gas Issues
 TDSP.csv Record Format
 Details of transactions sent by the TDSP
 FTP Replacement Software
 Primary ERCOT Contacts
 Final Comments
 Questions?
VEE Standards
 ERCOT suggests continuing the use of current IDR standards
 Avoid confusion with multiple standards
 Consistency across TDSP’s
 Minimize the multiplication of errors when sample data is extrapolated
to the population
 Facilitates ERCOT validation upon receipt of data.
 The link to the VEE standards is
http://www.naesb.org/REQ/req_form.asp click on Uniform Business
Practices for Unbundled Electricity Metering, Volume 2 - Published
12/05/00.
 Exemptions as specified in Protocols, Section 10.11.3 “TDSP Polled
Settlement Meters.”
Sample Point Replacement Rules
 A sample point should be replaced for any of the following reasons:
 Unsafe conditions/vicious animals (Initially or subsequently as a result of a
change)
 Demolition / service removed / ESIID switches to Inactive status
 Customer refusal (permission requested only if necessary for access)
 Equipment / installation issues
 De-energized 12 months at time of selection
 De-energized 6 consecutive months after installation
 Incorrect weather zone (identified after sample selection)
 Premise switches to BUSIDRRQ
 Premise has competitively owned NIDR meter
 Note: The above list is not meant to be all inclusive.
 For Round 2, a change in the voltage level no longer triggers a
replacement.
Oil/Gas Issues
 ERCOT has screened the sample list to eliminate known oil/gas
locations however others most certainly exist.
 If an oil/gas point is found during the installation process, then do not
install an IDR and go to a replacement sample point.
 Be sure to indicate on the reason for replacement that the point was
determined to be an oil/gas point.
 If a sample point is switched to BUSOGFLT profile type, then the
point must be replaced.
Replacement Point Process
 Use the following process to replace a sample point:
 Submit Remove Recorder (TD05) and a Stop (terminate) Sample Point
(LP01) transactions using the TDSP.csv record format for the sample
point being replaced. Be sure to include the reason for termination in
the LP01. Of course, the TD05 does not need to be sent if no recorder
was installed.
 Select the replacement sample point IN ORDER from the list (i.e. do
not skip sample points because another one down the list is more
convenient)
 Submit an Install Recorder (TD02) transaction using the TDSP.csv
record format for the recorder installed at the replacement point
 If no replacement samples are available, please call or send email to
the Load Profile Group at ERCOT.
TDSP.csv Record Format
fld
Name
Description
Len
1
Sample Designation
Designation of the sample of which the ESI ID is part of
2
Sample Description
Long Description of sample
3
Operation Code
Decode for the operation or even that will be verified within
ERCOT internal systems
4
ESI ID
5
Type
Comments
ERCOT
only
20
VARCHAR
MANDATORY for all operations. Supplied by ERCOT
256
VARCHAR
ERCOT creates for internal use
4
VARCHAR
MANDATORY for all operations, For operation code refer to Events Guide
The ESI ID associated with the sample site and Device ID
36
VARCHAR
Must be alphanumeric; Defined by Texas SET Protocols
Recorder ID
The TDSP-defined identifying number of the IDR,
associated with an ESI ID. This should be a one-to-one
relationship with ESIIDs
17
VARCHAR
MV-90 Recorder ID allows for 20, but ERCOT will be prefixing with TDSP code to prevent any
Recorder ID duplications among the TDSPs. Recorder is optional IF AND ONLY IF the ERCOT
sample load flag is populated by ERCOT only. Recorder ID is mandatory for all TDSPs
6
Sender
Entity sending the information
3
VARCHAR
MANDATORY for all operations; 1=ERCOT, 2=TDSP
7
Sample Begin Date
8
Date
ERCOT population only when a sample begin date, YYYYMMDD
Y
8
Sample Termination Date
Termination of a sample.
8
Date
ERCOT populate only when a sample has been terminated, Format is YYYYMMDD
Y
9
Sample Point Begin Date
Date when an ESI ID became an active part of a sample
8
Date
Format is YYYYMMDD
Y
10
Sample Point Termination Date
Date when an ESI ID is no longer participating in a sample
8
Date
Format is YYYYMMDD
11
Reason for Sample Point Termination
Reason the sample point was terminated from the sample
256
12
IDR Installation Date
Date the IDR was installed at a sample point
13
IDR Removal Date
Date the IDR was removed from a sample point
14
Load Profile Type
Load Profile Type in LodeStar
15
Weather Zone
16
8
VARCHAR
Y
Required if Sample Point Termination Date/Time is specified, else optional
Date
Format is YYYYMMDD
Format is YYYYMMDD
8
Date
20
VARCHAR
Load Profile type in LodeStar as assigned by TDSP per Profile Decision Tree
Y
Weather Zone based on service address zip code
2
INTEGER
Weather Zone in LodeStar as assigned by TDSP per Profile Decision Tree; in numeric form
from table decode
Y
Service Voltage
Secondary or Primary or Transmission service voltage
level
1
VARCHAR
Defines the service voltage as (S)econdary or (P)rimary or (T)ransmission
17
Stratum Number
Stratum number for sample
2
INTEGER
ERCOT-defined sample stratum number
Y
18
Sequence Number
Sequence number for sample sites
30
VARCHAR
Sequence number will contain a P (Prime) or R (Replacement)
Y
19
TDSP
The TDSP number stored in LodeStar
3
INTEGER
MANDATORY for all operations, MRE code, Must be 3 characters in length
20
TDSP Rate Class
The TDSP defined rate class or tariff under which the ESI
ID is served
2
INTEGER
The TDSP rate class under which the ESI ID is served; from PUCT website decode
21
Effective Date
8
Date
100
MANDATORY for all operations, Format is YYYYMMDD. Use current date if not for TDSP Rate
class
Transaction Details – TD02
 TD02 – Install IDR
 Required Fields in CSV file definition:
 Operation Code = Field 3
 ESIID = Field 4
 Recorder ID (RECID) = Field 5
 Sender = Field 6 (2 = TDSP)
 IDR Installation Date = Field 12 (CCYYMMDD)
 TDSP = Field 19 (MRE Code, Must be 3 characters in length)
 Effective Date = Field 21 (CCYYMMDD)
,,TD02,ESIID,RECID,2,,,,,,20071101,,,,,,,065,,20071101
Transaction Details – TD05
 TD05 – Remove IDR from Stop Sample Point
 Required Fields in CSV file definition:
 Operation Code = Field 3
 ESIID = Field 4
 Recorder ID (RECID) = Field 5
 Sender = Field 6 (2 = TDSP)
 IDR Removal Date = Field 13 (CCYYMMDD)
 TDSP = Field 19 (MRE Code, Must be 3 characters in length)
 Effective Date = Field 21 (CCYYMMDD)
,,TD05,ESIID,RECID,2,,,,,,,20070306,,,,,,065,,20070306
Transaction Details – LP01
 LP01 - Stop Sample Point Participation In Sample
 Required Fields in CSV file definition:
 Sample Designation = Field 1
 Operation Code = Field 3
 ESIID = Field 4
 Sender = Field 6 (2 = TDSP)
 Sample Point Termination Date = Field 10 (CCYYMMDD)
 Reason for Sample Point Termination = Field 11
 TDSP = Field 19 (MRE Code, Must be 3 characters in length)
 Effective Date = Field 21 (CCYYMMDD)
RESLO04,,LP01,ESIID,,1,,,,20071020,Reason for Sample Pt
termination in Sample,,,,,,,,065,,20071020
FTP Replacement Software
 The FTP Replacement Software - HTTPS protocol:
 provides a client-server based approach to allow TDSP’s to send and
receive files to/from the ERCOT server
 is defined as a PUSH/PULL protocol similar to FTP. The client scripts are
used to push and pull data files and reports
 uses SSL (Secure Socket Layer 128-bit encryption) to provide secure
communications between the TDSP and ERCOT so encryption of data
from the TDSP’s will not be required
 The FTP Replacement scripts SEND and RECEIVEALL are used by
the TDSP’s to communicate with the ERCOT server.
Send Data to ERCOT – SEND Command
 The SEND command is used to upload transaction and .LS
(interval data cut) files from the TDSP to the TDSP’s mailbox on
the ERCOT server.
 An upload is considered complete (successful) when the ERCOT
server responds to the SEND with a positive delivery Application
Acknowledgement indicating a successful status.
 An example of a SEND script is as follows:
MPCS SEND -FR 18352904900lr -TO 183529049L -UID
00000000000lr -PWD Lr000000000! -DIR C:\ERCOTFILES\OUT
-ARC C:\ERCOTFILES\ARCHIVE -REJ
C:\ERCOTFILES\REJECT -URL
https://naesb.ercot.com:44337/servlet/lrspilot/ebxml-100 -LOG
C:\ERCOTFILES\LOG\MPCSOutboundLOG.TXT
RECEIVEALL data from ERCOT – RECEIVEALL Command
 The RECEIVEALL command is used to download files to the
TDSP from the TDSP’s mailbox on the ERCOT server.
 Retrieved files are stored in the Market Participant’s directory
specified by the user in a command line parameter called –DIR.
 An example of a RECEIVEALL script is as follows:
MPCS RECEIVEALL -FR 18352904900lr -TO 183529049L -UID
18352904900lr -PWD Lr183529049! -DIR C:\ERCOTFILES\IN -ARC
C:\ERCOTFILES\ARCHIVE -REJ C:\ERCOTFILES\REJECT -URL
https://naesb.ercot.com:44337/servlet/lrspilot/ebxml-100 -LOG
C:\ERCOTFILES\LOG\MPCSInboundLOG.TXT
Primary ERCOT Contacts
 Each TDSP should call or email their primary ERCOT contact if they have any
questions regarding sample point transactions.
 Contact the ERCOT Help Desk with FTP Replacement related questions.
CenterPoint
Diana Ott
[email protected]
x3934
TXU ED
Ron
Hernandez
[email protected]
x6523
TNMP , Sharyland,
Nueces EC
Adrian
Marquez
[email protected]
x3915
AEP
Bill Boswell
[email protected]
x3169
Final Comments
 A copy of the “TDSP_CSV Operations Guide 1.4” has been
posted under Key Documents for this meeting
 Call or email your primary ERCOT contact with questions
regarding sample point transactions
 Contact the ERCOT Help Desk with FTP Replacement related
questions.
The COMSYS Vendor Management Program
Questions!