MARKET AND TRANSMISSION SETTLEMENTS · Market and Transmission Settlements Validations 1 INTRODUCTION PURPOSE The purpose of this document is to describe the validations associated

MARKET AND TRANSMISSION

SETTLEMENTS Member Data Exchange Validations

Published on 1/16/2019

By IT Settlements

Southwest Power Pool, Inc.

REVISION HISTORY

DATE OR

VERSION NUMBER AUTHOR

CHANGE

DESCRIPTION COMMENTS

0.1 – 3/8/2018 Nikki Eason Initial draft for SMS

0.2 – 6/29/2018 Nikki Eason Updated based on latest requirements

1.0 – 12/21/2018 Nikki Eason Published final version for SMS

1.1 – 1/16/2019 Nikki Eason Removed bookmark errors


CONTENTS

Revision History ......................................................................................................................................................................... i

Introduction ............................................................................................................................................................................... 1

Purpose ................................................................................................................................................................................... 1

Supporting Documents ..................................................................................................................................................... 1

Glossary .................................................................................................................................................................................. 1

Market Settlement – Bilateral Settlement Schedules ............................................................................................... 3

Create Header ....................................................................................................................................................................... 3

Update Header ..................................................................................................................................................................... 5

Approve Header .................................................................................................................................................................. 6

Create Profile ........................................................................................................................................................................ 7

Approve Profile .................................................................................................................................................................... 8

End Contract ......................................................................................................................................................................... 9

Search Contracts ............................................................................................................................................................... 10

Search Contracts By Date Range ................................................................................................................................ 11

Query FSE Source Sink Report .................................................................................................................................... 12

Market Settlement – Meter Data ..................................................................................................................................... 13

Submit Meter Data ........................................................................................................................................................... 13

Query Calibration Report .............................................................................................................................................. 14

Query Interchange Report ............................................................................................................................................ 15

Query Meter Report Card .............................................................................................................................................. 16

Market Settlement – Results ............................................................................................................................................. 17

Query Determinant Report ........................................................................................................................................... 17

Query EQR Data ................................................................................................................................................................. 17

Query FERC Formatted EQR Data .............................................................................................................................. 18

Query Invoice ..................................................................................................................................................................... 18

Query Settlement Statement ........................................................................................................................................ 19

Query Settlement Data ................................................................................................................................................... 19

Transmission Settlement – Submissions ..................................................................................................................... 20

Submit Direct Assignment ............................................................................................................................................ 20

Submit Monthly Assessment ........................................................................................................................................ 22

Submit MVAR...................................................................................................................................................................... 23


Submit Network Hourly Load ...................................................................................................................................... 24

Submit NITS/Coincident Peak ..................................................................................................................................... 25

Submit Schedule 12 ......................................................................................................................................................... 27

Transmission Settlement – Results ................................................................................................................................ 28

Query Determinant Report ........................................................................................................................................... 28

Query Invoice ..................................................................................................................................................................... 28

Query Transmission Customer Netting Invoice ................................................................................................... 29

Query Settlement Statement ........................................................................................................................................ 29

Query Settlement Data ................................................................................................................................................... 30

Query Transmission Summary Report .................................................................................................................... 30

Settlement – Calendar .......................................................................................................................................................... 31

Query Calendar By Calendar Date ............................................................................................................................. 31

Query Calendar By Calendar Month ......................................................................................................................... 31

Query Calendar By Operating Date ........................................................................................................................... 31


Market and Transmission Settlements Validations 1

INTRODUCTION

PURPOSE The purpose of this document is to describe the validations associated with user submissions and

queries available in the Settlements UI and API for Market and Transmission Settlements.

This document, along with the corresponding XSDs, fully describes the validations of the

Settlements Web Services.

SUPPORTING DOCUMENTS The following table describes the primary supporting documents for the business validations

defined in this document.

Document Description

Integrated Marketplace Protocols

The Market Protocols developed by SPP provide background information, guidelines, business rules, and processes for the operation and administration of the SPP Integrated Marketplace and the Reliability Unit Commitment processes, including market settlements, billing, and accounting requirements.

Transmission Settlement Business Practices

The Transmission Settlement Business Practices were developed by SPP to provide background information and detailed settlement calculations for all applicable SPP Tariff Schedules and Attachments pertaining to settlement of Transmission Service.

GLOSSARY Acronyms referenced in this document.

Acronym Description

API Automatic Programmatic Interface

BSS Bilateral Settlement Schedules

DA Direct Assignment

MA Monthly Assessment

MP Market Participant

MVAR MegaVahr

NITS Network Interface Transmission Schedule

S12 Schedule 12



TC Transmission Customer

TO Transmission Owner

UI User Interface

URL Uniform Resource Locator

WSDL Web Service Definition Language

XSD XML Schema Definition



MARKET SETTLEMENT – BILATERAL SETTLEMENT

SCHEDULES

The validations defined in this section apply to the submission and query of Bilateral Settlement

Schedules (BSS) for Market Settlement via the Settlements BSS UI and API.

CREATE HEADER

Certificate Permissions:

o Assigned the Bilateral Settlement Schedules “Manage Contract Headers” role

o Permitted to create headers for Asset Owner (buyer and/or seller) associated with the Market Participant

Submission Validation Rules:

Input Data Required Validation ContractName Yes Must be unique within the Header Start and

Header End Date. The same Contract Name cannot be used for more than one BSS header within the same date range.

Product Yes Must be submitted as DAENERGY, REGUPOBL, SPINOBL, RTENERGY, REGDNOBL or SUPPOBL

Buyer Yes Must be effective in the commercial model for the specified Start Date and End Date

Seller Yes Must be effective in the commercial model for the specified Start Date and End Date

AutoConfirmIndicator Yes Must be submitted as TRUE or FALSE SubmitterIndicator Yes Must be set to BUYER, SELLER or BOTH SettlementLocation No Must not be null if Product is DAENERGY or

RTENERGY. Must be null if product is REGUPOBL, SPINOBL, REGDNOBL, or SUPPOBL. If submitted, must be effective in the commercial model for the specified Start Date and End Date and associated with the Seller

ReserveZoneNameError! Bookmark not defined.

No Must not be null if product is REGUPOBL, SPINOBL, REGDNOBL, or SUPPOBL Must be null if product is DAENERGY or RTENERGY. If submitted, must be effective in the commercial model for the specified Start Date and End Date and associated with the SELLER



Must not be ‘SPP’. MaxQuantity Yes Must be greater than zero and less than or equal to

4000 StartDate Yes Must be valid Operating Date EndDate Yes Must be greater than or equal to the Header Start

Date



UPDATE HEADER



o Permitted to manage headers for Asset Owner (buyer and/or seller) associated with the Market Participant

Update Criteria:

o Updating a header may only occur on an unapproved header or an approved header with no profile data submitted.


Input Data Required Validation HeaderId Yes Must be associated with a submitted Contract

Header associated with the MP ContractName Yes Must be unique within the Header Start and

Header End Date. The same Contract Name cannot be used for more than one BSS header within the same date range.

Product Yes Must be submitted as DAENERGY, REGUPOBL, SPINOBL, RTENERGY, REGDNOBL or SUPPOBL

BuyerError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Start Date and End Date

SellerError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Start Date and End Date

AutoConfirmIndicator Yes Must be set to TRUE or FALSE SubmitterIndicator Yes Must be BUYER, SELLER or BOTH SettlementLocationError! Bookmark not defined.

No Must not be null if Product is DAENERGY or RTENERGY. Must be null if product is REGUPOBL, SPINOBL, REGDNOBL, or SUPPOBL. If submitted, must be effective in the commercial model for the specified Start Date and End Date and associated with the Seller

ReserveZoneNameError! Bookmark not defined.

No Must not be null if product is REGUPOBL, SPINOBL, REGDNOBL, or SUPPOBL. Must be null if product is DAENERGY or RTENERGY. If submitted, must be effective in the commercial model for the specified Start Date and End Date and associated with the SELLER Must not be ‘SPP’.

MaxQuantity Yes Must be greater than zero and less than or equal to 4000



StartDate Yes Must be a valid Operating Date EndDate Yes Must be greater than or equal to the Header Start

Date

APPROVE HEADER


o Assigned the Bilateral Settlement Schedules “Approve Contract Headers” role

o Permitted to approve contracts for Asset Owner (buyer and/or seller) associated with the Market Participant


Input Data Required Validation HeaderId Yes Must be associated with a submitted Contract Header associated

with the MP. Associated Contract Header must have a status of PENDING.

Confirmation Yes Submit as True for Approved or False for Denied



CREATE PROFILE


o Assigned the Bilateral Settlement Schedules “Manage Profile Data” role

o Permitted to create profiles for Asset Owner (buyer and/or seller) associated with the Market Participant

Submission Window Validation:

o If submitted after close window, accept submission, but return warning indicating the window is closed and data may not be used.

Completeness:

o XML payload must contain hourly interval data for every hour of a single operating day.


Parameters Required Description HeaderId Yes Must be associated with a Contract Header confirmed/approved by

both Buyer and Seller IntervalEnding Yes Must fall within the Contract Header Start Date and End Date MwValue Yes Must be less than or equal to MAXQUANTITY in the Contract

Header



APPROVE PROFILE


o Assigned the Bilateral Settlement Schedules “Approve Profile Data” role

o Permitted to approve profiles for Asset Owner (buyer and/or seller) associated with the Market Participant




Parameters Required Description HeaderId Yes Must be associated with a Contract Header confirmed/approved by

both Buyer and Seller OperatingDay Yes Must fall within the Contract Header Start Date and End Date Confirmation Yes Submit as True for Approved or False for Denied



END CONTRACT



o Permitted to end contracts for Asset Owner (buyer and/or seller) associated with the Market Participant


Parameters Required Description HeaderId Yes Must be associated with a submitted Contract Header associated with

the submitter

Note: Ending a contract will set the end date of the header to the end of the current calendar day or to the end of the maximum date with profile data APPROVED and PROCESSED, whichever date is greater. Its purpose is to end a header early after it has been confirmed by both parties. All profile data previously submitted after the new end date will be placed into a TERMINATED status and will not be used for settlement calculations.



SEARCH CONTRACTS


o Assigned the Bilateral Settlement Schedules “Query Contract Headers and Profiles” role

o Must be scoped to view reports for the submitted Asset Owner (Buyer or Seller)

Query Validation Rules:

Parameters Required Description ViewProfileData Yes Must be submitted as True or False ViewAllHeaders Yes Must be submitted as True or False

Header Search Criteria HeaderID Yes Must be associated with a submitted Contract

Header associated with the submitter or submitted as nil

Buyer Yes NERC ID for Buyer; may be submitted as nil Seller Yes NERC ID for Seller; may be submitted as nil Product Yes Must be submitted as DAENERGY, REGUPOBL,

SPINOBL, RTENERGY, REGDNOBL or SUPPOBL or submitted as nil

ContractName Yes Name associated with Contract associated with submitter; may be submitted as nil

ContractType Yes Type of BSS Contract (e.g. BSS, FSE, GFA); may be submitted as nil

ConfirmationSearchFilter –HeaderStatus

Yes Must be submitted as CONFIRMED, PENDING, DENIED, TERMINATED, PROCESSED, ERROR or nil

ConfirmationSearchFilter –SellerConfirmedStatus


ConfirmationSearchFilter –BuyerConfirmedStatus


MyPendingHeadersOnlyFlag No When set to true, the results will only contain Contract Headers in a PENDING status

Profile Search (optional) ConfirmationSearchFilter –ProfileStatus


ConfirmationSearchFilter -SellerConfirmedStatus


ConfirmationSearchFilter -BuyerConfirmedStatus


MyPendingProfilesOnlyFlag No When set to true, the results will only contain Contract Profiles in a PENDING status.

OperatingDay Yes Must be a valid Operating Date in or nil.



SEARCH CONTRACTS BY DATE RANGE


o Assigned the Bilateral Settlement Schedules “Query Contract Headers and Profiles” role

o Must be scoped to view reports for the submitted Asset Owner (Buyer or Seller)


Parameters Required Description ViewProfileData Yes Must be submitted as True or False ViewAllHeaders Yes Must be submitted as True or False

Header Search Criteria HeaderID Yes Must be associated with a submitted Contract

Header associated with the submitter or submitted as nil

Buyer Yes NERC ID for Buyer; may be submitted as nil Seller Yes NERC ID for Seller; may be submitted as nil Product Yes Must be submitted as DAENERGY, REGUPOBL,

SPINOBL, RTENERGY, REGDNOBL or SUPPOBL or submitted as nil

ContractName Yes Name associated with Contract associated with submitter; may be submitted as nil

ContractType Yes Type of BSS Contract (e.g. BSS, FSE, GFA); may be submitted as nil

ConfirmationSearchFilter -HeaderStatus






MyPendingHeadersOnlyFlag No When set to true, the results will only contain Contract Headers in a PENDING status

Profile Search Criteria ConfirmationSearchFilter -ProfileStatus






MyPendingProfilesOnlyFlag No When set to true, the results will only contain Contract Profiles in a PENDING status

DateRangeStart Yes Must be a valid Operating Date DateRangeEnd Yes Must be a valid Operating Date and greater

than or equal to the Date Range Start



QUERY FSE SOURCE SINK REPORT


o Assigned the Bilateral Settlement Schedules “View Fse Source Sink Report” role

o Must be scoped to view reports for the submitted Market Participant


Parameters Required Description OperatingDate Yes Must be a valid Operating Date MarketParticipantError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Date

Group Yes Must be a FSE group associated with the Market Participant

Location Type No Must be set to “SOURCE” or “SINK” Settlement LocationError! Bookmark not defined.

No If submitted, must be effective in the commercial model for the specified Operating Date and associated with the Market Participant



MARKET SETTLEMENT – METER DATA

The validations defined in this section apply to the submission and query of Meter Data for Market

Settlements via the Settlements UI and API.

SUBMIT METER DATA


o Assigned the Settlements Meter Data “Submit Meter Data” role

o Must be scoped to submit for the submitted Meter Location



Completeness:

o XML payload must contain all interval data for the submitted Operating Date


Parameters Required Description EntityNameError! Bookmark not defined.

Yes Must be effective in the commercial model for the submitted Operating Date and modeled as a Meter Agent

EntityType Yes Must be submitted as “MeterAgent” OperatingDate Yes Must be a valid previous Operating Date

Hourly Interval MeterLocationError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Date and associated with the Meter Agent; Meter Location must be registered to submit hourly data

Timestamp Yes Submission timestamp IntervalEnding Yes Must be a valid Operating Hour for the submitted

Operating Date Value Yes Value must be between -10,000 and 10,000 MWH.

Five-Minute Interval MeterLocationError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Date and associated with the Meter Agent; Meter Location must be registered to submit five-minute data

Timestamp Yes Submission timestamp IntervalEnding Yes Must be a valid Five-minute Interval Ending for the

submitted Operating Date Value Yes Value must be between -10,000 and 10,000 MWH.



QUERY CALIBRATION REPORT


o Assigned the Settlements Meter Data “View Meter Reports”, “View Meter Reports for MP” or “View Meter Reports for AO” role

o Must be scoped to view reports for the submitted Entity Name and Entity Type



Yes Must be effective in the commercial model for the submitted Operating Date

EntityType Yes Must be submitted as “MeterAgent”, “MarketParticipant” or “AssetOwner”

SettlementType No If submitted, must be a valid Settlement Type (e.g. LIVE, S7, S53, S120, R#)

OperatingDate Yes Must be a valid Operating Date SettlementAreaError! Bookmark not defined.

No If submitted, it must be effective in the commercial model for the specified Operating Date

MeterLocationDetailLevel No If submitted, it must be Hourly HourEnding No If submitted, it must be a valid Hour Ending in the

submitted Operating Date. MeterAgentError! Bookmark not defined.

No If submitted, it must be effective in the commercial model for the specified Operating Date and associated with the submitted EntityName

MeterLocationError! Bookmark not defined.




QUERY INTERCHANGE REPORT


o Assigned the Settlements Meter Data “View Meter Reports” or “View Meter Reports for MP” role

o Must be scoped to view reports for the submitted Market Participant or Meter Agent




EntityType Yes Must be submitted as “MeterAgent”, “MarketParticipant”

SettlementType No If submitted, must be a valid Settlement Type (e.g. LIVE, S7, S53, S120, R#)


No If submitted, it must be effective in the commercial model for the specified Operating Date

InterchangeLocationDetailLevel No If submitted, it must be Hourly or FiveMinute HourEnding No If submitted, it must be a valid Hour Ending in

the submitted Operating Date. MeterAgentError! Bookmark not defined.


InterchangeLocationError! Bookmark not defined.




QUERY METER REPORT CARD


o Assigned the Settlements Meter Data “View Meter Reports” or “View Meter Reports for MP” role

o Must be scoped to view reports for the submitted Market Participant or Meter Agent




EntityType Yes Must be submitted as “MeterAgent”, “MarketParticipant”

SettlementType No If submitted, must be a valid Settlement Type (e.g. Live, S7, S53, S120, R#).


No If submitted, must be effective in the commercial model for the specified Operating Date and associated with the requested Meter Agent or Market Participant.

MeterLocationDetailLevel No If submitted, it must be Hourly or FiveMinute HourEnding No If submitted, it must be a valid Hour Ending in the

submitted Operating Date. MeterAgentError! Bookmark not defined.


MeterLocationError! Bookmark not defined.




MARKET SETTLEMENT – RESULTS

The validations defined in this section apply to the query of Settlement Results for Market

Settlement via the Settlements UI and API.

QUERY DETERMINANT REPORT


o Assigned the Settlements Reports “View AO Bill Determinant Reports” role

o Must be scoped to view reports for the submitted Asset Owner



Yes Must be effective in the commercial model for the specified Operating Date.

EntityTypeError! Bookmark not defined.

Yes Must be submitted as “AssetOwner”,

OperatingDate Yes Must be a valid Operating Date SettlementCategory Yes Must be submitted as “Market SettlementType Yes Specifies the Settlement Type (e.g. S1, S2, S7, S53, S120, R#) DeterminantInterval Yes Must be submitted as ‘FiveMinute’, ‘HourlyDaily’, or ‘ALL’.

QUERY EQR DATA


o Assigned the Settlements Reports “View AO EQR Data” role



Parameters Required Description OperatingDateStart Yes Must be a valid Operating Date OperatingDateEnd Yes Must be a valid Operating Date that is greater than or

equal to the OperatingDateStart. It also must be within 31 days of the OperatingDateStart.

AssetOwnerError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Date range



QUERY FERC FORMATTED EQR DATA


o Assigned the Settlements Reports “View AO EQR Data” role



Parameters Required Description OperatingDateStart Yes Must be a valid Operating Date OperatingDateEnd Yes Must be a valid Operating Date that is greater than or

equal to the OperatingDateStart. It also must be within 31 days of the OperatingDateStart.

AssetOwnerError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Date range

SettlementType Yes Must be a valid Settlement Type (e.g. S7, S53, S120, R#) or submitted as “LATEST”

QUERY INVOICE


o Assigned the Settlements Reports “View MP Settlement Invoices” role

o Must be scoped to view reports for the submitted Market Participant





Yes Must be submitted as “MarketParticipant”

InvoiceDate Yes Invoice Date RequestPDF* Yes Set to true (1) if the member wishes to receive a PDF

formatted invoice in the payload response; otherwise set to false (0)



QUERY SETTLEMENT STATEMENT


o Assigned the Settlements Reports “View Settlement MP Settlement Statements” or “View Settlement AO Settlement Statements” role

o Must be scoped to view reports for the submitted Market Participant or Asset Owner


Parameters Required Description

EntityNameError! Bookmark not defined.



Yes Must be submitted as “MarketParticipant” or “AssetOwner”

SettlementDate Yes Date the Statement was posted for members to download

QUERY SETTLEMENT DATA


o Assigned the Settlements Reports “View Settlement MP Settlement Statements” or “View Settlement AO Settlement Statements” role

o Must be scoped to view reports for the submitted Market Participant or Asset Owner






Yes Must be submitted as “MarketParticipant” or “AssetOwner”,




TRANSMISSION SETTLEMENT – SUBMISSIONS

The validations defined in this section apply to the submission and query of data for Transmission

Settlements via the Settlements UI and API.

SUBMIT DIRECT ASSIGNMENT


o Assigned the Transmission Settlements System (TSS) “Can Upload Transmission Settlements TO Files”

o Must be scoped to submit reports for the submitted Transmission Owner (reference the submitted EntityName and EntityType)





Yes Must be effective in the commercial model for the specified Operating Month and modeled as a Transmission Owner

EntityType Yes Must be submitted as “TransmissionOwner” OperatingMonth Yes Must be the month-end date of the prior

month Must be an Operating Month on or after May 2019.

ZoneNameError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Month

TSR Yes Must be the TSR associated with Transmission Customer

TransmissionCustomerError! Bookmark not defined.


LoadName Yes Must be submitted as string data TC_MO_ANC_1_SC_AMT No If submitted, must be a numeric value TC_MO_ANC_2_RV_AMT No If submitted, must be a numeric value TC_MO_ANC_3_REG_AMT No If submitted, must be a numeric value TC_MO_ANC_5_SPIN _AMT No If submitted, must be a numeric value TC_MO_ANC_6_SUPP _AMT No If submitted, must be a numeric value DISTRIBUTION_FACILITIES_DIRECT_ASSIGNMENT_AMT

No If submitted, must be a numeric value

TRANSMISSION_FACILITIES_DIRECT_ASSIGNMENT_AMT


METERING_AMT No If submitted, must be a numeric value SYSTEM_UPGRADE_AMT No If submitted, must be a numeric value POWER_FACTOR_AMT No If submitted, must be a numeric value



MISCELLANEOUS_ADJUSTMENT_AMT


REQUESTED_UPGRADE_AMT No If submitted, must be a numeric value GEN_IMBALANCE_DIRECT_ASSIGNMENT_AMT


ENERGY_IMBALANCE_DIRECT_ASSIGNMENT_AMT


COMMENT No Optional comments – no validation performed



SUBMIT MONTHLY ASSESSMENT


o Assigned the Transmission Settlements System (TSS) “Can Upload Transmission Settlements TO Files” or “Can Upload Transmission Settlements TC Files”

o Must be scoped to submit reports for the submitted Transmission Owner or Transmission Customer (reference the submitted EntityName and EntityType)






Yes Must be effective in the commercial model for the specified Operating Year and modeled as a Transmission Owner or Transmission Customer

EntityType Yes Must be submitted as “TransmissionOwner” or “TransmissionCustomer” and the Entity Type must be consistent with the type associated with the Entity Name in the commercial model

OperatingYear Yes Must be the previous calendar year

Must be an Operating Year on or after 2019.


Yes Must be effective in the commercial model for the specified Operating Year


Yes Must be effective in the commercial model for the specified Operating Year.

If the entity type is “TransmissionCustomer”, the submitted TransmissionCustomer name must match the submitted EntityName.

LoadName Yes Must be a string value

ZONAL_PRIOR_YR_AVG_CP_MW Yes Must be a numeric value

COMMENT No Optional comments – no validation performed



SUBMIT MVAR


o Assigned the Transmission Settlements System (TSS) “Can Upload Transmission Settlements TC Files”

o Must be scoped to submit reports for the submitted Transmission Customer (reference the submitted EntityName and EntityType)

Completeness:

o XML payload must contain all interval data for the submitted Operating Date






Yes Must be effective in the commercial model for the specified Operating Date and modeled as a Transmission Customer

EntityType Yes Must be submitted as “TransmissionCustomer”

OperatingDate Yes Must be a valid Operating Date

Must be an Operating Date on or after May 1, 2019.

SettlementLocationError! Bookmark not defined.

Yes Must be effective in the commercial model for the specified Operating Date and associated with the submitted EntityName and is modeled as a Qualified Generator

Timestamp Yes Must be a valid timestamp

IntervalEnding Yes Must be a valid Hour Ending within the submitted Operating Date

MVAR Value Yes Must be a numeric value



SUBMIT NETWORK HOURLY LOAD


o Assigned the Transmission Settlements System (TSS) “Can Upload Transmission Settlements TO Files” or “Can Upload Transmission Settlements TC Files”

o Must be scoped to submit reports for the submitted Transmission Owner or Transmission Customer (reference the submitted EntityName and EntityType)

Completeness:

o XML payload must contain all interval data for the submitted Operating Month






Yes Must be effective in the commercial model for the specified Operating Month and modeled as a Transmission Owner or Transmission Customer

EntityType Yes Must be submitted as “TransmissionOwner” or “TransmissionCustomer” and the Entity Type must be consistent with the type associated with the Entity Name in the commercial model

OperatingMonth Yes Must be the month-end date of the prior month

Must be an Operating Month on or after May 2019.






HourEnding Yes Must be a valid Hour Ending within the submitted Operating Month

TSRError! Bookmark not defined.

Yes Must be a valid TSR associated with the submitted TC and must be effective in the commercial model for the specified Operating Month

LoadMW Yes Must be a numeric value



SUBMIT NITS/COINCIDENT PEAK








EntityNameError! Bookmark not defined. Yes Must be effective in the commercial model for the specified Operating Month and modeled as a Transmission Owner

EntityType Yes Must be submitted as “TransmissionOwner”

OperatingMonth Yes Must be a previous Operating Month


ZoneNameError! Bookmark not defined. Yes Must be effective in the commercial model for the specified Operating Month and associated with the submitted EntityName

PeakHourEnding Yes Must be an Operating Hour within the submitted Operating Month

TO_NITS_ROLLING_12_MO_ZCP_AVG_MW Yes Must be a numeric value

TO_NITS_PRIOR_YR_ZCP_AVG_MW Yes Must be a numeric value

TO_NITS_MO_ZCP_MW Yes Must be a numeric value

TO_SCHED11_PRIOR_YR_ZCP_AVG_MW Yes Must be a numeric value

TO_NITS_ROLLING_12_MO_RCP_AVG_MW Yes Must be a numeric value

TO_NITS_PRIOR_YR_RCP_AVG_MW Yes Must be a numeric value

TO_NITS_MO_RCP_MW Yes Must be a numeric value



TO_SCHED11_PRIOR_YR_RCP_AVG_MW Yes Must be a numeric value

TSR Yes Must be the TSR associated with Transmission Customer




TC_NITS_ROLLING_12_MO_ZCP_AVG_MW No Must be a numeric value

TC_NITS_PRIOR_YR_ZCP_AVG_MW Yes Must be a numeric value

TC_NITS_MO_ZCP_MW Yes Must be a numeric value

TC_NITS_ROLLING_12_MO_RCP_AVG_MW No If submitted, must be a numeric value

TC_NITS_PRIOR_YR_RCP_AVG_MW Yes Must be a numeric value

TC_NITS_MO_RCP_MW Yes Must be a numeric value

Comments No Optional comments – no validation performed



SUBMIT SCHEDULE 12









Yes Must be effective in the commercial model for the specified Operating Month and modeled as a Transmission Owner

EntityType Yes Must be submitted as “TransmissionOwner”

OperatingMonth Yes Must be the month-end date of the prior month



Yes Must be effective in the commercial model for the specified Operating Month and associated with the submitted EntityName




TC_MO_SCHD12_MW Yes Must be a numeric value

Comments No Optional comments – no validation performed



TRANSMISSION SETTLEMENT – RESULTS

The validations defined in this section apply to the query of Settlement Results for Transmission

Settlement via the Settlements UI and API.

QUERY DETERMINANT REPORT


o Assigned the Settlements Reports “View TC Bill Determinant Reports” or “View TO Bill Determinant Reports” role

o Must be scoped to view reports for the submitted Transmission Owner or Transmission Customer





Yes Must be submitted as “TransmissionCustomer” or “TransmissionOwner”

OperatingDate Yes Must be a valid Operating Date SettlementCategory Yes Must be submitted as “TransmissionDaily” or

“TransmissionMonthly” SettlementType Yes Specifies the Settlement Type (e.g. S1, S2, S7, S53,

S120, R#) DeterminantInterval Yes Must be submitted as are ‘HourlyDaily’, and ‘ALL’.

QUERY INVOICE


o Assigned the Settlements Reports “View TC Settlement Invoices” or “View TO Settlement Invoices” role








formatted invoice in the payload response; otherwise set



to false (0)

QUERY TRANSMISSION CUSTOMER NETTING INVOICE


o Assigned the Settlements Reports “View TC Settlement Invoices” role

o Must be scoped to view reports for the submitted Transmission Customer





Yes Must be submitted as “TransmissionCustomer”


formatted invoice in the payload response; otherwise set to false (0)

QUERY SETTLEMENT STATEMENT


o Assigned the Settlements Reports “View TC Settlement Statement” or “View TO Settlement Statement” role











QUERY SETTLEMENT DATA


o Assigned the Settlements Reports “View TC Settlement Statement” or “View TO Settlement Statement” role









QUERY TRANSMISSION SUMMARY REPORT


o Assigned the Settlements Reports “View TC Summary Report” or “View TO Summary Report” role








InvoiceMonth Yes Must be a valid month

TSR No If submitted, must be a valid TSR associated with the submitted EntityName



SETTLEMENT – CALENDAR

The validations defined in this section apply to the query of the calendar for Market and

Transmission Settlements via the Settlements UI and API.

QUERY CALENDAR BY CALENDAR DATE


Parameters Required Description CalendarType Yes Must be a valid the Settlement Category (Market or Transmission)

CalendarDate Yes Must be a valid calendar day

QUERY CALENDAR BY CALENDAR MONTH



CalendarMonth Yes Must be a valid calendar month

QUERY CALENDAR BY OPERATING DATE



CHOICE (In this section the submitter needs to specify if the request is for an Operating Date or Operating

Month) OperatingDate No If submitted, must be a valid Operating Date OperatingMonth No If submitted, must be a valid Operating Month.

Note: Operating Month query is only valid for querying the events associated with a TransmissionMonthly settlement.