SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

CRR Naming Convention

josephine avatar
josephine
6 diapositives · 234 Views · Feb 02, 2014

CRR Naming Convention. WMS February 20, 2008 Beth Garza. Nodal Protocols require a CRR naming Convention. 7.2.1 CRR Naming Convention

#one #triplet #trinity #unity #threesome #tierce #30 #ternary
CRR Naming Convention - slide 1
01 / 6CRR Naming Convention
1 / 17

Télécharger la présentation

CRR Naming Convention
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. CRR Naming Convention WMS February 20, 2008 Beth Garza

  2. Nodal Protocols require a CRR naming Convention 7.2.1 CRR Naming Convention The appropriate TAC subcommittee shall establish a task force that is open to Market Participants, comprised of technical experts, to develop a naming convention for CRRs consistent with the requirements of the Protocols. The naming convention must be approved by TAC before implementation. • In previous action, WMS has requested that ERCOT staff develop a proposal • Objectives: • Descriptive vs. unique

  3. CRRs have multiple attributes • No single attribute can guarantee uniqueness • The CRR system initially assigns a unique identifier (CRR_ID) to each CRR • A SegmentID may be assigned when a portion of a CRR (capacity or time period) is sold either in a subsequent auction or via bilateral trade

  4. Further Explanation of Attributes • CRR ID: unique identifier for each awarded/allocated CRR per market • Segment ID: differentiates CRRs that are broken out after auction (during trades, etc) • Account Holder : name as registered • Category: PTP (Point to Point) or FGR (Flowgate Right) • Hedge Type: Obligation or Option • CRR Type BASELOAD: PCRR Types, prior to payment, after payment switch to STANDARD CAPACITY: PCRR Types, prior to payment, after payment switch to STANDARD REFUND: PCRR Type PREAWARD: CRRs that have not yet been paid for STANDARD: CRRs that have been paid for • Source: source name (settlement point) • Sink: sink name (settlement point) • Flowgate: flowgate name, if applicable • Start Date: mm/dd/yyyy • End Date: mm/dd/yyyy • Time of Use: PeakWD (Peak Weekday), PeakWE (Peak Weekend) or Off-peak • MW: MW amount, per hour

  5. Fortunately the CRR system handles it • CRR system users are not required to keep track of uniqueness • The system presents each user with all of their CRRs • Any action that a user takes with an existing CRR is handled via dragging and dropping from their CRR inventory list

  6. Proposed WMS action • A unique CRR_ID and SegmentID combination, coupled with various descriptive CRR attributes meets the Nodal Protocol requirement for a CRR naming convention. • Examples of possible CRR name: PTP-OBL-From-HB_SOUTH-To-LZ_NORTH-362-1 PTP-OPT-From-AK_GT1__8040-To-LZ_WEST-363-1