Skip to content
Conduit
Reference

What a switch actually does, leg by leg.

A switch is not one transaction. It is a request out and six documents back, over days, from two counterparties — and the state of a customer is the state of that chain.

All reference

This is the part that surprises people migrating from a system that treats EDI as file handling. The individual documents are simple; the difficulty is that they arrive asynchronously, from different parties, and only mean something in relation to each other. A leg that never arrives is invisible unless you were expecting it.

Each chain below shows the initiating transaction a retailer submits and the legs the market generates in response. Where a chain branches on rejection, both paths are shown — the rejection branch is short, which is exactly why it is easy to miss when it happens.

The ones you live in

Enrollment, start to finish.

A switch and a move-in run the same shape: request, ERCOT to the wires company, result back, usage, initial read, first delivery invoice. The permit-required variant is where a move-in goes when the premise is not ready.

Switch

814_01

Change of REP of Record for an existing customer/ESI ID.

  1. 814_01Switch Request

    You submit this.

  2. 814_03Enrollment Notification Request

    ERCOT sends enrollment notification to the TDSP

  3. 814_04Enrollment Notification Response

    TDSP returns the enrollment result

  4. 814_05CR Enrollment Notification Response

    CR receives the accepted enrollment result

  5. 867_02Historical Usage

    Historical usage delivered

  6. 867_04Initial Meter Read

    Initial meter read establishes the actual start date

  7. 810_02TDSP Invoice

    TDSP invoice for delivery charges

If rejected instead

  • 814_02ERCOT rejects the switch request

Move-In

814_16

Service/enrollment in a customer's name at a premise.

  1. 814_16Move In Request

    You submit this.

  2. 814_03Enrollment Notification Request

    ERCOT sends enrollment notification to the TDSP

  3. 814_04Enrollment Notification Response

    TDSP returns the enrollment result

  4. 814_05CR Enrollment Notification Response

    CR receives the accepted enrollment result

  5. 867_02Historical Usage

    Historical usage delivered

  6. 867_04Initial Meter Read

    Initial meter read establishes the actual start date

  7. 810_02TDSP Invoice

    TDSP invoice for delivery charges

If rejected instead

  • 814_17ERCOT rejects the move-in request

Move-Out

814_24

Terminate the current customer's enrollment/service relationship.

  1. 814_24Move Out Request

    You submit this.

  2. 814_25Move Out Response

    TDSP/ERCOT return the move-out result

  3. 867_03Monthly or Final Usage

    Final usage (867_03F) establishes the end billing period

  4. 810_02TDSP Invoice

    TDSP invoice for final delivery charges

If rejected instead

  • 814_25TDSP/ERCOT reject the move-out

Move-In — Permit Required

814_16

Move-in that the TDSP holds pending a permit.

  1. 814_16Move In Request

    You submit this.

  2. 814_03Enrollment Notification Request

    ERCOT sends enrollment notification to the TDSP

  3. 814_28Complete Unexecutable or Permit Required

    TDSP reports Permit Required

  4. 814_29Complete Unexecutable or Permit Required Response

    ERCOT acknowledges the exception

  5. 814_04Enrollment Notification Response

    TDSP schedules after the permit is received

  6. 814_05CR Enrollment Notification Response

    CR receives the scheduled enrollment result

  7. 867_04Initial Meter Read

    Initial meter read establishes the actual start date

The rest

Cancels, changes, service orders and outages.

Shorter chains, but the same principle — the response leg is what tells you the request landed, and its absence is the thing worth alerting on.

Cancel Pending Transaction

814_08

Cancel a pending move-in, switch, or move-out.

  1. 814_08Cancel Request

    You submit this.

  2. 814_09Cancel Response

    TDSP/ERCOT return the cancel result

Date Change

814_12

Change the effective date of a pending transaction.

  1. 814_12Date Change Request

    You submit this.

  2. 814_13Date Change Response

    TDSP/ERCOT return the date-change result

Establish/Delete CSA

814_18

Establish or delete a Continuous Service Agreement.

  1. 814_18Establish/Delete CSA Request

    You submit this.

  2. 814_19Establish/Delete CSA Response

    Return the CSA establish/delete result

Historical Usage Request

814_26

Request historical usage for an ESI ID.

  1. 814_26Historical Usage Request

    You submit this.

  2. 814_27Historical Usage Response

    Return the request status/availability

  3. 867_02Historical Usage

    Historical usage data delivered

Maintain Customer Information

814_PC

Point-to-point customer/contact maintenance.

  1. 814_PCMaintain Customer Information Request

    You submit this.

  2. 814_PDMaintain Customer Information Response

    Counterparty responds to the maintenance request

Service Order

650_01

Discretionary field/meter work via a 650.

  1. 650_01Service Order Request

    You submit this.

  2. 650_02Service Order Response

    TDSP acknowledges/schedules/completes the service order

Switch Hold Maintenance

650_01

Add/remove a switch hold, then publish the updated state.

  1. 650_01Service Order Request

    You submit this.

  2. 650_02Service Order Response

    TDSP acknowledges the switch-hold service order

  3. 814_20ESI ID Maintenance Request

    TDSP publishes the updated switch-hold ESI ID attribute

Option 1 Outage — Status

T0

Request outage status from the TDSP.

  1. T0Option 1 Outages: Outage Status Request

    You submit this.

  2. T3Option 1 Outages: Status Response

    TDSP returns the outage status

Option 1 Outage — Trouble Report

T1

Submit a customer trouble/outage report.

  1. T1Option 1 Outages: Trouble Reporting Request

    You submit this.

  2. T2Option 1 Outages: Trouble Report Acknowledgement

    TDSP acknowledges the trouble report

  3. T3Option 1 Outages: Status Response

    TDSP provides a status update

  4. T4Option 1 Outages: Trouble Completion Report

    TDSP reports completion

On authority

All 13 chains are generated from the lifecycle catalog our simulated market runs, which is the same definition the platform uses to decide what it is waiting for. Timings are not shown here on purpose — real market response times vary by counterparty and by day, and publishing ours would imply a precision the market does not have.

Every document these chains use

Chains, not files.

Conduit correlates every inbound and outbound leg into the chain it belongs to, so a customer's market state is something you look at rather than reconstruct.

Book a demoMarket transactions