Skip to content
Conduit
Reference

ERCOT's issue taxonomy, in full.

MarkeTrak is where the ERCOT retail market resolves the things that transactions alone cannot fix: a customer enrolled by mistake, usage two parties disagree about, a record one side has and the other does not.

All reference

The taxonomy is two levels. A case type routes an issue into a resolution workflow; a subtype selects the specific problem within it, and determines what evidence the case has to carry. A subtype is only valid under its parent type, which is the constraint most home-grown trackers miss — and the reason a case raised from a generic ticketing tool so often comes back.

The largest bucket by far is Day to Day, which covers the ordinary retail failures: cancels, missing enrollment transactions, usage and billing disagreements, rejected transactions, and both sides of an inadvertent gain. The Data Extract Variance families are narrower and more mechanical — they exist to reconcile what ERCOT holds against what a market participant holds, one attribute at a time.

The expensive one

Inadvertent gain, both sides

An inadvertent gain is a customer who ended up on a retailer's service without a valid enrollment — most often a switch submitted against the wrong ESI ID. It is modelled from both sides, because both have work to do: the gaining retailer has a customer it should not be serving and will be charged for, and the losing retailer has lost one it should still have. Resolving it means a case on each side and a regain transaction back through the market.

Both sides, as subtypes

Inadvertent gain — gainingIaGg
You are serving a customer you should not be. You are also billing them, and about to be charged for their delivery.
Inadvertent gain — losingIaGl
A customer you should still have has gone. The case is how you get them back, and the regain transaction is what actually does it.

22 subtypes · IssueD2D

Day to Day

Day-to-day retail market issues — the largest bucket (enrollments, cancels, usage/billing, IAG, …).

  • Cancel with approval

    CancelWA

  • Cancel without approval

    CancelWoA

  • Missing enrollment transaction

    MissEnrollTrxn

  • Usage / billing

    UsageBilling

  • Rejected transaction

    RejectTrxn

  • REP of record

    RepRecord

  • Projects

    Proj

  • Siebel

    Siebel

  • 997 issue

    D2d997

  • Inadvertent gain — gaining

    IaGg

  • Inadvertent gain — losing

    IaGl

  • Premise

    Premise

  • Service address

    ServiceAddr

  • Safety net

    SafetyNet

  • 650 service order

    ServiceOrder

  • Move-out / meter removal

    MoveOutMeterRemoval

  • AMS LSE interval — dispute

    AMSLSEIntervalDispute

  • AMS LSE interval — missing

    AMSLSEIntervalMissing

  • Redirect fees

    RedirectFees

  • Market rule

    MarketRule

  • Customer rescission

    CustomerRescission

  • Other

    Other

5 subtypes · IssueDevChar

Data Extract Variance — Characteristics

Data Extract Variance — ESIID characteristics (region, load profile, station, ZIP, loss factor).

  • Region

    Region

  • Loss factor

    Loss

  • Load profile

    Profile

  • Station

    Station

  • ZIP code

    Zip

6 subtypes · IssueDevExist

Data Extract Variance — Existence

Data Extract Variance — record existence mismatch between ERCOT and the market participant.

  • Present at the participant, absent at ERCOT

    ExistMPNotERCOT

  • Present at ERCOT, absent at the participant

    ExistERCOTNotMP

  • ERCOT start time

    ExistERCOTStartTime

  • Inactive record date

    ExistInactiveRecordDate

  • Status

    ExistStatus

  • Un-retire an ESI ID

    ExistUnretireESIID

4 subtypes · IssueDevIDR

Data Extract Variance — IDR usage

Data Extract Variance — IDR (interval) usage discrepancy.

  • Usage at the participant, absent at ERCOT

    IDRUsageMPNotErcot

  • Usage at ERCOT, absent at the participant

    IDRUsageErcotNotMP

  • Date mismatch

    IDRUsageDate

  • kWh mismatch

    IDRUsagekWh

4 subtypes · IssueDevNIDR

Data Extract Variance — Non-IDR usage

Data Extract Variance — non-IDR usage discrepancy.

  • Usage at the participant, absent at ERCOT (TOU)

    NonIDRUsageMPNotErcotTOU

  • Usage at ERCOT, absent at the participant

    NonIDRUsageErcotNotMP

  • Date mismatch

    NonIDRUsageBothDate

  • kWh mismatch

    NonIDRUsagekWh

6 subtypes · IssueDevLSE

Data Extract Variance — LSE interval

Data Extract Variance — LSE (load serving entity) present / interval.

  • At the participant, absent at ERCOT — active

    LSEPresentMPNotErcotActive

  • At the participant, absent at ERCOT — de-energized

    LSEPresentMPNotErcotDeEnergized

  • At ERCOT, absent at the participant

    LSEPresentErcotNotMP

  • Start date does not match

    LSEPresentBothStartDateNoMatch

  • End date does not match

    LSEPresentBothEndDateNoMatch

  • Start and end dates do not match

    LSEPresentBothStartAndEndDateNoMatch

No enumerated subtypes

Types that take a case directly.

These case types route to a workflow without a subtype selection beneath them.

ERCOT initiated

IssueERCOTInitiated

An issue ERCOT itself opens against a market participant.

Load profile adjustment

IssueLoadProfile

Load Profile Adjustment (LPA).

Bulk insert

IssueBulkInsert

Submission of many issues at once from a single file, rather than one case at a time.

Background report

IssueBackgroundReport

A report request run in the background against case data.

On authority

All 10 case types and 47subtypes are generated from the taxonomy our platform validates against. The wire code shown against each is the authoritative token; the plain-English label beside it is our rendering, not ERCOT’s official display string.

How Conduit works these cases

A backlog of these is a bad week.

Conduit models every type and subtype on this page, runs the clocks, and closes the inadvertent gain loop end to end.

Book a demoMarkeTrak