Interchange Scheduling Reference Manual

Transcription

1 Interchange Scheduling Reference Manual November 07, 2017 Version 6.0

2 Revision History Date / Version # 09/12/2012 Version /09/2012 Version /18/2012 Version /28/2013 Version /1/2013 Version /13/2013 Version /12/2014 Version /28/2014 Version /4/2014 Version /21/2015 Version /1/2015 Version /21/2016 Version 4.0 Author Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Shari Brown Change Description Initial Creation of Draft Formal Draft for internal review and comments and edits from staff Completed Internal review and edits from Operations Market staff Added Market Import Service Info added examples for Ramp Reservation System and cleaned up references for publication Official Publication Revised for Protocol and BP changes as well as for EES move to MISO Revised for additional of Marketplace Tagging HUB Revised for helpful hint for OASIS links on Scenario Analyzer and EFFATC reports Revised for changes made since beginning of Marketplace Added (and enhanced) information from the Ramp Reservation User Guide. Added references to Transmission Service Reference Manual. Made clarifications to tags submitted for time changes. Added change due to Implementation of the IS Integration into SWPP footprint. Clarified Day Ahead Market timing requirements and noted new timelines effective 09/30 for OD 10/1. Made additional changes to accommodate IS integration and websmarttag. Added ramp validations and Tagging Information Appendix. Interchange Scheduling Reference Manual V6 1

3 09/29/2017 Version /07/2017 Version 6.0 Shari Brown Shari Brown Changes to accommodate new tag template, including addition of MO field. Corrected MIS service recall criteria. Updated default ramp duration information. Clarified that SPP pseudo-ties are not tagged. Updated tag validation information for Day Ahead Market tags. Rewrote section 2.2. Loss Supply tag type may be used if the tag sources and sinks in WECC or if the tag is dropping losses for WAUW (i.e., sources in SWPP and sinks in WECC). Corrected stated default ramp times for tags that source or sink in WECC. Ramp overlap denial reasons are shown in CP time. Interchange Scheduling Reference Manual V6 2

4 Table of Contents Revision History Introduction Purpose of the Interchange Scheduling Reference Manual Related/Referenced Documents Scheduling Overview Interchange Scheduling Interchange Coordinator (IC) Scheduling Systems Balancing Authority (BA) Transmission Service Provider (TSP) Purchase and Selling Entity (PSE) Process Overview for Interchange Scheduling SPP Balancing Authority Area and Neighboring Balancing Authorities Registration for SPP Interchange Scheduling NAESB Electric Industry Registry (EIR) SPP Market Registration Commercial Model Changes Settlement Locations Asset Owners/Market Participant PSE is mapped to a TC is mapped to a AO is mapped to an MP Transmission Service for Interchange Scheduling Transmission Losses for Interchange Transactions: Combining Transmission Service on Interchange Transactions Market Import Service (MIS) Ramp Reservation for Interchange Scheduling Ramp Capability Ramp Reservation Business Rules Ramp Reservation Validation...19 Interchange Scheduling Reference Manual V6 3

5 5.4 Ramp Reservation Deadlines e-tag Ramp Validation Ramp Availability Ramp Start/Stop Ramp Overlap Ramp Reservation System (RRS) Ramp Reservation (Submission) Display Ramp Reservation Status Ramp Availability Tagging Interchange Transactions Electronic Tagging (e-tag) Tag Transaction Types Interchange Schedule Types Import Export Through Market Types Day-Ahead Market Real Time Market (RTBM) Integrated Marketplace Transaction Types Fixed Interchange Transactions Dispatchable Interchange Schedules Up-to-TUC Interchange Schedules Dynamic Interchange Schedules External Dynamic Resources (EDR) HVDC Ties HVDC Tie Inadvertent Scheduling Interchange Transactions Interchange Schedules Electronic Scheduling System (webtrans) Validation of Tags for SPP Tariff Status Energy MW Interchange Scheduling Reference Manual V6 4

6 7.3.3 NERC Priority POR/POD Network Service Market Import Service (MIS-NN6) Source/Sink Validation of Tags for SPP Balancing Authority Late Start/Late Energy Profile Physical Path SPP Ramp Validation Validation of Tags for Integrated Marketplace SPP Market Bid/Offer SPP Market Timing For Day-Ahead SPP Marketplace Settlement Location SPP Market Losses Curtailments and Adjustments NERC Transmission Loading Relief (TLR) Market Adjustments Appendix A: Special Tagging Helpful Information...46 User Options: OATI Users/Non- OATI Users...46 OATI Users SPP Market Information Specification for Non-OATI Users Market Information on Tags...46 User Access Admin for OATI Users...46 Daylight Savings Time...47 Options for Spring Forward (Change to CDT) Two-Tag Option for Change to CDT One Tag Option for Change to CDT Options for Fall Back (Change to CST) Two-Tag Option for Change to CST One-Tag Option for Change to CST Recognizing the Right Tag/Schedule...50 Changing Time Zone Settings (OATI Users)...50 Appendix B: Tagging Information...51 Tag Information Section...51 Interchange Scheduling Reference Manual V6 5

7 Contact Information Section...52 Requests Section...53 Market Path Section...53 Market Information Section...54 Physical Path Section...54 Energy and Transmission Profiles Section...56 Transmission Allocation Section...57 Carbon Copy List Section...57 Loss Accounting Section...58 Appendix C: Tagging Examples...59 Import...59 Export...59 Through...60 Dynamic Tags...60 HVDC Ties Import...60 HVDC Ties Export...62 Appendix D: Glossary...64 Interchange Scheduling Reference Manual V6 6

8 1 Introduction 1.1 Purpose of the Interchange Scheduling Reference Manual The purpose of the Interchange Scheduling Reference Manual is to provide Transmission Customers and Market Participants (TC/MP) information on the business rules that are to be followed when scheduling with the SPP Balancing Authority and the Integrated Marketplace. Additionally, this document will allow the TC/MP the information necessary to assist them in determining if there are system changes related to Scheduling that they must make within their own companies. This document is a reference manual only and is not an official SPP Governing Document. 1.2 Related/Referenced Documents SPP Balancing Authority Operations Manual SPP Open Access Transmission Tariff Business Practices SPP Criteria Integrated Marketplace Protocols SPP Open Access Transmission Tariff Transmission Service Reference Manual NOTE: For Real-Time Scheduling Questions contact the Tariff/Interchange Desk at (501) Interchange Scheduling Reference Manual V6 7

9 2.1 Interchange Scheduling 2 Scheduling Overview Interchange is Energy transfers that cross Balancing Authority boundaries. An Interchange Transaction is an agreement to transfer Energy from a seller to a buyer that crosses one or more Balancing Authority Area boundaries. Interchange Scheduling in the Integrated Marketplace includes tagged Energy transactions that cross into, out of and through the SPP Balancing Authority Area (BAA). The SPP Integrated Marketplace boundary is the same footprint as the SPP BAA. Interchange Scheduling does not include tagging or scheduling transactions internal to the SPP Balancing Authority. These types of transactions are usually associated with Grandfathered Transmission Service and bilateral agreements between SPP members or internal to SPP members. SPP has included a process within the Market Settlement to manage these types of transactions through the use of Bilateral Settlement Schedules. Market Participants may optionally use Bilateral Settlement Schedules to account for the impact of these internal transactions on Integrated Marketplace settlement. Tags are not allowed for transactions within the Integrated Marketplace. 2.2 Interchange Coordinator (IC) The SPP Interchange Coordinator is the responsible entity that systematically coordinates implementation of valid and balanced Interchange Schedules between the SPP Balancing Authority and its neighboring Balancing Authorities and ensures communication of Interchange Information for Reliability assessment purpose. NERC allows ICs to have a third party service provide these services and SPP has contracted with a registered Tagging Authority for use of its systems. These systems perform the duties as described in the NERC Interchange (INT) standards and NAESB Business Practices. Interchange Scheduling Reference Manual V6 8

10 2.2.1 Scheduling Systems Most scheduling tools used by SPP fall within the responsibility of the Interchange Coordination and Balancing Authority functions. The following is a list of the electronic tools that SPP uses to accomplish Interchange Scheduling Processing: NAESB Electronic Interchange Registry (EIR) discussed in section 3 - Registration for SPP Interchange Scheduling Open Access Same Time Information System (websmartoasis, OASIS) discussed in section 4 - Transmission Service for Interchange Scheduling Ramp Reservation System (RRS) discussed in section 5 - Ramp Reservation for Interchange Scheduling Electronic Tagging (e-tag) discussed in section 6 - Tagging Interchange Transactions Electronic Scheduling System (webtrans) discussed in section 7 Scheduling Interchange Transactions 2.3 Balancing Authority (BA) SPP is the sole registered Balancing Authority (BA) for the SPP Integrated Marketplace footprint. As such, SPP acts as a Balancing Authority for confirmation and verification, approval or denial of all Interchange Schedules entering and/or leaving the SPP Balancing Authority Area (BAA). SWPP is the GCA and/or LCA and Scheduling Entity (SE) for all Interchange Schedules entering and/or leaving the SPP BAA as appropriate. As such, SPP has specific roles and responsibilities for NERC checkout processes that are associated with these entities. NOTE: See Appendix C: Tagging Examples, for examples of properly completed Tag Physical Path section of e-tags. These allow for proper checkout with the appropriate entities. GCA and LCA require active approvals prior to implementation of a tag. See section 7.4 Validation of Tags for SPP Balancing Authority. 2.4 Transmission Service Provider (TSP) SPP is the Transmission Service Provider under the SPP OATT. SPP is registered with the acronym SWPP for TSP. When SWPP Transmission Service is used, SPP Operators act as a TSP for confirmation and verification, approval, or denial of all Interchange Schedules entering and/or leaving the SPP Balancing Authority Area. SPP is also the TSP for the WAUW Balancing Authority located in WECC. Since, WAUW is the Balancing Authority, SPP is not the Interchange Coordinator or Scheduling party for WAUW only transactions. SPP acts on WAUW tags only as the Transmission Provider. WAUW performs all Interchange and scheduling responsibilities. TSP requires active approval prior to implementation of a tag. See section 7.3 Validation of Tags for SPP Tariff. Interchange Scheduling Reference Manual V6 9

11 2.5 Purchase and Selling Entity (PSE) The Purchasing and Selling Entity (PSE) has various roles in the tagging of schedules for use in the Integrated Marketplace for SPP. The PSE that creates the tag is the Creating Purchase and Selling Entity (CPSE) and may or may not be the same PSE that used as the Transmission Customer that settles with SPP for the Marketplace transaction. The example below shows a PSE that is also the SPP Transmission Customer. Transmission Customers are discussed in section 3 - Registration for SPP Interchange Scheduling. PSE as a Transmission Customer on Tag highlighted in YELLOW Tag Physical Path EXAMPLE: EXPORT BA TSP MO PSE POR POD S/E SWPP SWPP AECC01 Source: AECC.FULTON SWPP AECC01 CSWS EES SWPP EES ENTEMO CSWS EES MISO MISO Sink ENTEMO ENTEMO 2.6 Process Overview for Interchange Scheduling SPP follows NAESB requirements for Interchange Scheduling in the Integrated Marketplace. The general overall process for Scheduling is as follows: 1. Registration with NAESB and SPP for ability to create Transmission Service reservations, create tags, and participate in the SPP Integrated Marketplace discussed in section 3 - Registration for SPP Interchange Scheduling 2. Completed and confirmed Transmission Service must be available for ultimate tagging of the schedule discussed in section 4 - Transmission Service for Interchange Scheduling as well as the Transmission Service Reference Manual 3. Completed and approved Ramp Reservation (Optional) discussed in section 5 - Ramp Reservation for Interchange Scheduling 4. Completed e-tag All Interchange Transactions entering and/or leaving the SPP BAA must be electronically tagged, except in emergencies - discussed in section 6 - Tagging Interchange Transactions 5. Verified and Approved e-tags discussed in section 7.5 Validation of Tags for Integrated Marketplace 6. Communicate implemented Interchange Schedule to Interchange Coordinator 7. Schedule data to various SPP systems Interchange Scheduling Reference Manual V6 10

12 General Process for Interchange Scheduling in SPP Interchange Scheduling Reference Manual V6 11

13 2.7 SPP Balancing Authority Area and Neighboring Balancing Authorities For Interchange Scheduling, it is helpful to know the SPP BAA boundaries. SPP operates in the Eastern Interconnection. SPP is bounded by the following first tier Eastern Interconnection Balancing Authorities. All Energy scheduled between SPP and other Eastern Interconnection BAs must interface through the first tier BAs listed below. The Eastern Interconnection first tier neighboring BAs are: Associated Electric Cooperative, Inc. (AECI) Southwest Power Administration (SPA) Midwest Independent Service Organization (MISO) SPP is located on the Western edge of the Eastern Interconnection and is the major scheduling connection for Energy scheduled to and from the Western Interconnection (WECC) and the ERCOT Interconnection. All scheduling with the WECC and ERCOT must be accomplished via HVDC tie scheduling. See section 6.7 HVDC Ties. The HVDC ties between WECC and SPP are: 1. EDDY 2. BLKW 3. LAMAR 4. MCWEST 5. RAPID CITY EAST 6. STEGALL 7. SYDNEY The HVDC ties between ERCOT and SPP are: 1. ERCOTN 2. ERCOTE The HVDC tie between Canada and SPP is SASKATCHEWAN Interchange Scheduling Reference Manual V6 12

14 3 Registration for SPP Interchange Scheduling In order for a Transmission Customer to obtain Transmission Service and create Interchange Transactions that enter and/or leave the SPP BAA for use in the Integrated Marketplace, the customer must have completed Market Registration through the SPP Customer Relations process. REFERENCE: Transmission Service Reference Manual These customers must also have completed registry with the NAESB in order to tag transactions using Electronic Tagging systems. Customers must allow time for the registration approval and system integration process prior to commencing Interchange Scheduling transactions. 3.1 NAESB Electric Industry Registry (EIR) The EIR is set up for Balancing Authorities to have approval rights for all transaction entities that plan to schedule with their BA. All PSE, TOP, GOP, Sources, Sinks, etc. must be registered and approved by the SPP BA prior to commencing Interchange Scheduling. Purchasing Selling Entities (SPP Market Participants) must register their OASIS entity code and tagging code with EIR in order to purchase transmission and create tags in the SPP BA and Integrated Marketplace. The OASIS entity code is shown as the Company Name on the Transmission Service reservation. The Tagging code is shown on the tag in various locations. One of the major components on a tag for market settlements is the Transmission Customer associated with SPP Transmission Service. The Creating Purchasing Selling Entity (CPSE) is the entity that created the e-tag and the Transmission Customer is the PSE (not necessarily the same as the CPSE) entity shown as the owner of the SPP transmission under the Transmission Allocation section of the tag SPP Market Registration SPP Transmission Customers who intend to transact business with the SPP BA and Integrated Marketplace must register through the SPP Customer Relations Market Registration process. Through the SPP Market Portal, Market Participants (MPs) may access the applications that enable submission of Resource Offers, Demand Bids, and Virtual Bids and Offers into the Energy and Operating Reserve Markets. REFERENCE: Market Protocols section 6.1 Registration of Resources 3.2 Commercial Model Changes Whenever a Market Participant registers assets (resources, loads, etc.,) the SPP Commercial Model must be updated. SPP periodically uploads the model data up to one week prior to the effective date. The new data is available for use on the date that the new model is effective. An Interchange Scheduling Reference Manual V6 13

15 Asset Owner would not be allowed to tag against the newly updated data (e.g. resources or loads) for a transaction that flows before the effective date. When data is removed from the Commercial Model, it is deactivated the day before the Commercial Model change. This may take up to seven days to take effect. The Commercial Model determines the financial Market relationships for Market Participants and Asset Owners. Transmission Customers (PSE) are mapped to these entities in the Commercial Model. The Commercial Model describes how these financial entities relate to specific Nodes. REFERENCE: Market Protocols section Commercial Model Settlement Locations Sources and Sinks on e-tags are mapped to Settlement Locations. These Settlement Locations determine the Transmission Congestion pricing mechanisms. Settlement of all Energy related to schedules into, out of and through the SPP BA is performed as part of the Integrated Marketplace settlement at External Interface Settlement Locations. These External Interface Settlement Locations are pre-determined through off-line analysis and may consist of one or more Pricing Nodes (PNodes), which are linked to Nodes in the Network Model. In the following example of a Through Transaction, the Interface Settlement Locations for this tagged transaction and the entry of the Energy into the Marketplace through MISO is settled as an injection at the MISO External Interface Settlement Location and the exit of the Energy out of the Marketplace through ERCO is settled as a withdrawal at the ERCOT N External Interface Settlement Location. The interfaces are shown in yellow. In this situation, since the tag is a Through Transaction, the system uses a combination of the Source PSE/Source data field identification of the interface in and a combination of the Sink PSE/Sink data field for identification of the interface out. REFERENCE: Refer to Section for more information about Through Transactions. EXAMPLE: THROUGH/HVDC TAG External Source and Sinks for Mapping Table PHYSICAL PATH SECTION OF E-TAG Source MISO MISO BA TSP MO PSE POR POD S/E MISO MISO PSE-ID CIN CSWS MISO SWPP PSE-ID AMRN SPS SWPP SWPP PSE-ID SPS ERCOTN SWPP ERCO PSE-ID ERCOT-N ERCOT ERCO ERCO Sink PSE-ID ERCOT N REFERENCE: Market Protocols section Nodes and Pricing Nodes Interchange Scheduling Reference Manual V6 14

16 3.2.2 Asset Owners/Market Participant The SPP Integrated Marketplace uses a Translation Table to map the entities from the tag to the appropriate entities in the SPP Commercial Model. Purchasing and Selling Entity The Purchase and Selling Entity is the NAESB registered (NAESB EIR) name used on the tag to represent company ownership. All PSEs are mapped to a TC, which are mapped to an AO, and are then mapped to an MP in the Marketplace. For example, if a PSE is not registered as an SPP TC, then the tag will be rejected. Also, it is possible that the Creating PSE is different than the PSE used as the TC on the tag. Transmission Customer (TC) The PSE that is shown on the first leg of the SWPP Transmission Service on a tag. The Transmission Customer is mapped to the appropriate Asset Owner. Asset Owner (AO) An owner of any combination of: (1) registered physical assets (2) Transmission Congestion Rights or (3) any combination of financial assets within the SPP Balancing Authority Area. The Asset Owner is mapped to the appropriate Market Participant. Market Participant (MP) The entity in the Commercial Model that is financially obligated to SPP for market settlements. A single MP represents one or more Asset Owners PSE is mapped to a TC is mapped to a AO is mapped to an MP The Tag Physical Path example below highlights the PSE field in which the Transmission Customer for the TSR should have been identified on this transaction. In this case, SEPCPM (identified from the original Transmission Service Reservation) would be mapped to the appropriate Asset Owner and Market Participant for this Interchange Schedule. It is important to note that if another PSE other than the actual Transmission Customer Owner of the TSR is shown in this field on the e-tag, it will have no effect on the TC mapping or on settlements. Tag Example of PSE for Mapping Table Tag Physical Path EXAMPLE: MARKET IMPORT/HVDC TAG Source WACMM1 WACM BA TSP MO PSE POR POD S/E WACM LAPT WACMM1 EIPOR AU WACM PSCO MEANMN AU LAMR345 PSCO SWPP SEPCPM LAM345 SECI SWPP SWPP Sink SWPP SEPCPM SECI_SECI REFERENCE: Market Protocols section Asset Owners and Market Protocols section Market Participants Interchange Scheduling Reference Manual V6 15

17 Example of Commercial Model Relationships Whereas: AO = Asset Owner MP = Market Participant G = Generator L = Load D = Demand Interchange Scheduling Reference Manual V6 16

18 4 Transmission Service for Interchange Scheduling As outlined in the Transmission Service Reference Manual, customers use OASIS to request Transmission Service. Transmission Service Requests (TSRs) must be validated, accepted, and confirmed prior to submitting an e-tag to schedule the Service. Helpful information about procuring confirmed Transmission Service is outlined in the Transmission Service Reference Manual. SPP has specific rules for acquisition of TSRs. These business rules are described in the SPP OATT. Clarification and details for these rules are described in the SPP Business Practices. REFERENCES: Transmission Service Reference Manual, SPP OATT, SPP Business Practices This section overviews changes, relating to Interchange Scheduling with the SPP BA and settlement thereof, as a result of the implementation of the Integrated Marketplace. 4.1 Transmission Losses for Interchange Transactions: No physical Transmission Losses are allowed to be self-supplied on Interchange Transactions using SWPP Transmission Service in the SPP Integrated Marketplace. All losses are settled financially in the Integrated Marketplace. 4.2 Combining Transmission Service on Interchange Transactions SPP allows Transmission Customers to combine certain types of TSRs when tagging Interchange Transactions. The Business Rules for combining Transmission Service are documented in the SPP Business Practices and the Transmission Service Reference Manual. REFERENCE: Business Practice # 2350 Combining SPP Transmission Service Requests 4.3 Market Import Service (MIS) To prevent hoarding, Market Import Service (MIS) will be recalled if not scheduled within two hours after confirmation for Day-Ahead or 30 minutes after confirmation for Real-Time. The LCA on the tag must be SWPP. REFERENCE: Refer to the Transmission Service Reference Manual for more information about MIS. Interchange Scheduling Reference Manual V6 17

19 5 Ramp Reservation for Interchange Scheduling The SPP BA is required by NERC to evaluate all Interchange tags to ensure adequate Ramp Capability is available prior to approval. SPP has developed a Ramp Reservation System (RRS) to allow TCs to view the ramp that is available within the SPP BAA at any given time and to reserve the ramp needed for their transactions prior to tagging the transaction. All submissions of tagged Interchange Transactions into or out of the SPP BA will be evaluated against available Ramp Capability prior to approval by SPP. Ramp availability may be verified and pre-arranged by TCs (as mapped to AOs) ahead of submission of an e-tag through the RRS. Subsequent submission of a tag in which scheduled interchange is supported by an approved Ramp Reservation will be automatically approved with respect to Ramp Capability. NOTE: If an approved e-tag is adjusted, the adjusted e-tag will be re-validated for Ramp-Up and Ramp-Down for the adjusted time period, and may fail ramp validation. Use of the RRS is voluntary. Tagged transactions submitted without a Ramp Reservation or those that exceed the ramp reserved by the AO will be checked for remaining Ramp Capability and approved if available. Otherwise, the e-tag will be limited to the reserved ramp or will be denied if ramp was not reserved and there is no available ramp. Ramp validation is only applicable to scheduled Interchange that impacts SPP NSI (i.e. Imports or Exports of Energy to/from the SPP BA). Ramp validation is not performed on tagged transactions wheeling through the SPP BA. 5.1 Ramp Capability SPP Operations Engineering determines the available Ramp Capability within the SPP BAA based on current operating conditions and generation availability within the Integrated Marketplace. Ramp Capability is the maximum sustainable Ramp-Up and Ramp-Down capability expressed in MWs per minute. 5.2 Ramp Reservation Business Rules Every e-tag that is submitted by the CPSE where the Generating Control Area (GCA) or Load Control Area (LCA) is specified as SWPP will be validated for available Ramp Capability. Tags wheeling through the SPP BA where neither GCA nor LCA are SWPP will not be validated for ramp. The Energy MW profile on a tag physical path segment listing SWPP as the Scheduling Entity (SE) will be used to validate Ramp Capability. In the case of pancaked or stacked transactions, the Energy MW profile at the first (for Imports) or last (for Exports) tag physical path segment listing SWPP as the Scheduling Entity (SE) will be used to validate Ramp Capability. If no explicit start/stop ramp duration information is supplied in the e-tag, the default ramp duration will be used for this validation. The default ramp duration will be: Interchange Scheduling Reference Manual V6 18

20 20 minutes for tags that source and/or sink in WECC and begin at the top of the hour 10 minutes for tags that source and/or sink in WECC and begin at times other than the top of the hour 10 minutes for all other tags In the event that the start/stop ramp durations specified in the e-tag overlap such that there is insufficient time to reach the block accounting scheduled Energy MWs specified, the e-tag will be denied by SPP. 5.3 Ramp Reservation Validation The Integrated Marketplace ramp validation will first determine the Ramp-Up or Ramp-Down Capability required, in MWs/minute, at each schedule breakpoint based on the change in the proposed scheduled interchange Energy MWs divided by the ramp duration: Import tags: Ramp-Up is validated for Import ramp availability; Ramp-Down is validated for Export ramp availability. Export tags: Ramp-Up is validated for Export ramp availability; Ramp-Down is validated for Import ramp availability. Ramp Reservation requests will be approved immediately upon submission, subject to the verification of available Ramp-Up or Ramp-Down Capability, after accounting for all other approved Ramp Reservations and approved or pending e-tags. The available Ramp Capability in either direction will be offset by simultaneous reserved or tagged ramp commitments made in the opposite direction in accordance with netting rules established by the SPP Integrated Marketplace. NOTE: Refer to section 5.5 e-tag Ramp Validation for information on how webtrans validates e-tags for ramp. 5.4 Ramp Reservation Deadlines Reserved ramp that has not been tagged will be released for the entire Operating Day (OD) immediately after the Day-Ahead (DA) Market closing time. Real-Time (RT) reserved ramp that has not been tagged will be released for the entire duration of the Ramp Reservation at 30 minutes prior to the reserved ramp start time. Tags submitted by the TC subsequent to the release of any reserved ramp will be validated against the remaining available Ramp Capability in the order submitted. If a TC/MP does not submit a specific Ramp Reservation, the system will evaluate the submitted e-tag against the available capability. 5.5 e-tag Ramp Validation Ramp Availability The Integrated Marketplace ramp validation will first determine the Ramp-Up or Ramp-Down Capability required, in MWs/minute, at each schedule breakpoint based on the change in the proposed scheduled interchange Energy MWs divided by the ramp duration: Interchange Scheduling Reference Manual V6 19

21 Import tags: Ramp-Up is validated for Import ramp availability; Ramp-Down is validated for Export ramp availability. Export tags: Ramp-Up is validated for Export ramp availability; Ramp-Down is validated for Import ramp availability. The ramp validation will then determine if there are any unscheduled ramp commitments held by the CPSE under one or more Ramp Reservations matching the ramp start/stop times specified in the e-tag at each schedule breakpoint. If so, the unscheduled ramp commitments held on those Ramp Reservations will be allocated first to support the proposed e-tag schedule. Any additional Ramp Capability required beyond that supported by one or more Ramp Reservations, or the entire Ramp Capability required by the proposed scheduled interchange in the case where the CPSE does not have any supporting Ramp Reservation(s), will be validated against the remaining Ramp-Up or Ramp-Down Capability available. If there is sufficient Ramp Capability available to support the e-tag transaction, ramp commitments will be allocated to support the proposed scheduled interchange and the e-tag will be approved, subject to passing all other e-tag validations, by SPP. That is, an implied Ramp Reservation will be committed to support the e-tag from the remaining SPP Ramp Capability for the ramp required in excess of any pre-arranged Ramp Reservation(s) held by the CPSE on a first-come-first-served basis. If the proposed e-tag schedule would violate SPP Ramp Capability at any point in time, the e-tag will be denied by SPP with the reason Insufficient Ramp. EXAMPLE: Insufficient RampDown (-2.3 > 06:00:00 CS NOTE: Insufficient Ramp denial reasons always display in Central Standard (CS) time. The ramp validation will respect the netting of simultaneous Ramp-Up and Ramp-Down commitments according to SPP rules for such netting Ramp Start/Stop The Ramp Start/Stop validation ensures that the ramp start and stop values are less than the duration of the energy segment. EXAMPLE: A tag submitted with a 15 minute profile segment specified with a 20 minute ramp will be denied with the reason Ramp Start/Stop Ramp Overlap The Ramp Overlap validation ensures that a change to a tag will not cause simultaneous ramping in the opposite direction. EXAMPLE: If a change to a tag would cause ramp up while the tag is still ramping down, the change will be denied with the reason: Failed for Ramp 06:02:00 CP Interchange Scheduling Reference Manual V6 20

22 5.6 Ramp Reservation System (RRS) The RRS is part of the OATI webtrans. MPs or authorized AOs may gain secured login access to webtrans and the RRS with an authorized Username and Password in addition to an OATI x.509 electronic certificate issued by the OATI webcares system. webtrans is available over the Internet. Market Participants are directed to the OATI Help Desk at (763) to obtain an authorized user account for webtrans. Step Action Comments 1 Log in to webtrans via the Internet. A user ID, password, and certificate is required. 2 From the webtrans dashboard, click Marketplace from the toolbar. A drop-down menu displays. 3 Select Ramp from the drop-down menu. A sub-menu displays. 4 Select Ramp Reservation Summary from the sub-menu The Ramp Reservation Data screen displays. This screen allows you to filter for approved Ramp Reservations (See Section 5.8). It also contains a Ramp Reservation Entry button which allows you to request a new reservation. Interchange Scheduling Reference Manual V6 21

23 5.7 Ramp Reservation (Submission) Display The TC/MP or authorized AOs may submit Ramp Reservation requests using the RRS. Ramp Reservations are limited to a single designated OD in the SPP Integrated Marketplace. Ramp Reservations may be submitted and approved up to seven (7) days prior to a given OD in accordance with the SPP Integrated Marketplace Bid/Offer submission window. The Ramp Reservation Entry Form is accessible from the Ramp Reservation Summary display, which allows entry of a Ramp Reservation request. Step Action 1 Click Ramp Reservation Entry from the Ramp Reservation Data screen. 2 Enter the necessary data in the fields, including: Provider (e.g. SWPP) Operating Day Customer (e.g. Your PSE Code) Direction (Direction of Flow; e.g. Import) Start Time and Stop Time (Always CP) Energy MW (MW Amount to be reserved) Comments The Ramp Reservation Entry screen displays with a blank entry form. The Ramp Reservation profile should mirror the profile of the e-tag that will be submitted. NOTE: The information shown on the right side of this screenshot populates after you click Check, as shown in the next step. Interchange Scheduling Reference Manual V6 22

24 After entering the Ramp Reservation data, choose from the following options using buttons shown at the bottom of the screen. Option Action Comments 1 Click Check. This option will check the available Ramp-Up and Ramp-Down Capability needed to support the proposed scheduled interchange profile. Any violations of the total SPP Ramp Capability in either direction will be indicated and allow for the user to adjust the Energy profile as needed to avoid the ramp violations. No ramp commitments are held with the Check option, and there is no guarantee that subsequent submission of the Ramp Reservation request will be approved. 2 Click Commit. This option will perform the available Ramp-Up and Ramp-Down Capability verification; and if there is no violation of total SPP Ramp Capability in either direction, the Ramp Reservation will be approved and a corresponding ramp commitment for the proposed scheduled interchange will be held for the MP. If any violations of the total SPP Ramp Capability in either direction are detected, those violations will be indicated and allow for the user to adjust the Energy profile as needed to avoid the ramp violations similar to the Check option. 3 Click Clear. This option clears the data entered and allows the user to start with a clean screen. 4 Click Close. This option closes the screen. If this option is checked prior to clicking Commit, the data will be lost. Interchange Scheduling Reference Manual V6 23

25 5.8 Ramp Reservation Status Ramp Reservations that have been approved may be viewed from the Ramp Reservation Summary display. Details of the Ramp Reservation proposed scheduled Interchange profile, and all pending or approved e-tags that have been submitted that are supported by a given Ramp Reservation may be viewed by clicking on the assigned Ramp Reservation ID from the Ramp Reservation Data display. The ID displays in blue on the left of the screen below. After clicking on the Reservation ID for the PSE bucket, the Ramp Reservation Detail display will provide the details for that particular reservation. If a tag has been created against the ramp reserved, the tag will be indicated in the Ramp Commitment section. Interchange Scheduling Reference Manual V6 24

26 5.9 Ramp Availability SPP s Ramp Availability is the amount of up/down ramp left and ready to be reserved. It will change based on reservations and tags submitted, and it will be deducted from the Ramp Capability. Step Action 1 From the WebTrans dashboard, click Marketplace from the toolbar. 2 Select Ramp from the dropdown menu. Comments A drop-down menu displays. A sub-menu displays. To populate the data on the screen, you must either select filtering options or click the View Display button. 3 Select Ramp Availability from the sub-menu. 4 Click the View Display button. 5 Click on the Filter icon in the upper right-hand corner of the screen. The Ramp Availability Data screen displays. Data populates within the screen. The Filtering Options window displays. 6 Select SWPP from the Provider field drop-down menu. 7 Select the desired date range from the Range drop-down menu or click on the Calendar icon to select a date. Interchange Scheduling Reference Manual V6 25

27 Step Action 8 Select the desired block size from the Availability Block Size drop-down menu. 9 Enter the desired Ramp Duration from the drop-down menu. 10 Click Apply to apply the filters selected, or click Reset to reset the filters and start over. Comments NOTE: Block size is the increment displayed in minutes (e.g. a block size of 60 provides the ramp information hourly.) Users can set this field to smaller increments to fine-tune their requests. NOTE: Ramp duration is how long the ramp will spread the desired MWs over to ramp up or down (e.g. 10 or 20 minutes). NOTE: Results with applied filters are shown in the screenshot below. The Block Size is for 60 minutes (an hour) which users can see from the times in the Start and Stop columns. NOTE: The Available Ramp column displays the remaining ramp for the selected Block Size. Interchange Scheduling Reference Manual V6 26

28 6 Tagging Interchange Transactions 6.1 Electronic Tagging (e-tag) e-tagging is a process of electronically communicating a request for, securing approval of, and recording an Energy transaction. The functionality of the e-tag is used to track proof of Energy delivery as required by one or more regulatory bodies within the Eastern Interconnection. It is the responsibility of the CPSE to fill out and submit the e-tags. e-tags that do not comply with the following criteria are considered to be invalid and will be rejected. e-tags must: comply with the Market Protocols regarding selection of market types and transaction types have an existing confirmed SWPP transmission reservation fit within the parameters of the transmission reservation be compliant with the procedures specified in the SPP OATT and Business Practices have a unique tag ID NOTE: Refer to Appendices A, B, and C for more specific tagging information. 6.2 Tag Transaction Types Tag submissions contain several different attributes associated with the request. These attributes provide detailed information associated with each request. The attributes are Tag Transaction type, Interchange Schedule Type, Market Type, and Market Transaction Type. Each Interchange Transaction Schedule has type fields that must be filled in indicating the use of the tag. NOTE: SPP does not allow the use of all Tag Transaction Types. There are several Tag Transaction Types available through the NERC Electronic Tagging Process: Normal Tag for regular (normal) Energy Dynamic Tag with an estimated MW that is updated modified in real-time to comply with NERC requirements and updated to the telemetered reading or MW value After- The-Fact Emergency During an emergency of a BA, an emergency type tag can be created After- The-Fact. Loss Supply SPP supports Loss Supply tags only if the tag sources and sinks in WECC or if the tag is dropping losses for WAUW (i.e., sources in SWPP and sinks in WECC). Capacity SPP does not support Interchange Capacity Tags/Schedules. Recallable Tag with a recallable feature NOTE: The recallable feature is used for supplemental regulation transactions. Pseudo-tie Tag that allows inter-ba transmission visibility for Pseudo-tie facilities NOTE: SPP includes all pseudo-ties in the Marketplace congestion management process and therefore does not tag pseudo-ties. Interchange Scheduling Reference Manual V6 27

29 6.3 Interchange Schedule Types The Tag Transaction Types described above result in the following Interchange Schedule types for the SPP BA and Integrated Marketplace: Imports, Exports and Through. NOTE: SPP does not allow the use of all Interchange Schedule Types on tags. Physical paths that are internal to the SPP Integrated Marketplace and SPP BA are not tagged. REFERENCE: Market Protocols section Bilateral Settlement Schedules Import If the Source point is external to the SPP BAA and the Sink point is inside the SPP BA, the Interchange Schedule is an Import Schedule. The GCA and Source for all tags importing into the SPP BAA for settlement in the Integrated Marketplace must be external to the SPP BAA. The following requirements must be met: Confirmed transmission must have been acquired. The Source must match or be electrically equivalent to the Source on the TSR. POR and POD must match the TSR. NOTE: SPP registers POR and POD for members. MIS Transmission Service timing requirements apply. The LCA for all Imports into SPP BAA must be SWPP. SWPP is not used in the Sink field of an Import tag. The Sink used must match or be electrically equivalent to the Sink on the TSR. REFERENCE: Market Protocols section Import Interchange Transactions Offers NOTE: Refer to Appendix C for an example tag physical path for an Import into SPP BA Export If the Sink point is external to the SPP BAA and the Source point is internal, the Interchange Schedule is an Export Schedule. The LCA and Sink for all tags exporting out of the SPP BAA must be an external to the SPP BAA. Confirmed transmission must have been acquired. The GCA for all Exports out of the SPP BAA must be SWPP. POR and POD must match the transmission reservation. NOTE: SPP registers POR and POD for members. SWPP is not used in the Source field of an Export tag. REFERENCE: Market Protocols section Export Interchange Transactions Offers NOTE: Refer to Appendix C for an example tag physical path for an Export from SPP BA/Market. Interchange Scheduling Reference Manual V6 28

30 6.3.3 Through If the Source point and Sink point are external to the SPP BAA; the Interchange Schedule is a Through Schedule (wheels through the SPP BAA). The LCA, GCA, Source and Sink for all Through Schedules must be external to the SPP BAA. Confirmed transmission must have been acquired. Special rules apply for POR and POD when combining Transmission Service. REFERENCE: Business Practice # 2350 Combining SPP Transmission Service Requests NOTE: Refer to Appendix C for example tag physical paths for Through/Wheels into and out of the SPP BA (for HVDC tie and non-hvdc tie transactions). 6.4 Market Types The market types for Interchange Schedules (for Normal and Dynamic tag types) are Day- Ahead Market and Real-Time Market Day-Ahead Market The Day-Ahead Market provides Market Participants with the ability to submit Bids and Offers for exporting and importing Energy out of and into the SPP BAA. NOTES: If Day Ahead is not explicitly defined in the e-tag, the Market Type defaults to Real- Time. The Market Data section of the e-tag must be filled out in order to explicitly define the intention of bidding or offering into the SPP Day-Ahead Market. The market date in the Market Data section must match the start date on the physical tag. Inputs to the Day-Ahead process through tagged Interchange Transactions are: Bids and Offers for Exports and Imports Market Type designation Market Transaction Designation MW profile Outputs to the Day-Ahead process for tagged Interchange Transactions are cleared Import/Export Transactions which reflect adjusted Interchange Schedules that are not completely cleared. NOTE: Effective October 10, 2017, these adjustments are initiated by the MO. Prior to that time, the adjustments were initiated by the BA. Interchange Scheduling Reference Manual V6 29

31 Example of Day-Ahead Schedule Market Information Specific timing requirements apply to Day-Ahead tagged Interchange Transactions. These timing requirements are shown in the diagram below. NOTE: In 2016, SPP began allowing customers to utilize multi-day functionality to submit Day- Ahead transactions. Each Day-Ahead transaction is still evaluated by Operating Day. The Market Date must match the tag start/stop profile. PSEs are not allowed to adjust, correct, or extend Day-Ahead tags while the Day-Ahead Market processes. REFERENCE: Refer to Section for more information about Market Adjustments. Day-Ahead Activities Timeline REFERENCE: Market Protocols section 4.3 Day-Ahead Activities NOTE: All times are shown CPT Real Time Market (RTBM) Only Fixed transactions may be submitted for use in the RTBM. Fixed schedules that clear in the Day-Ahead Market automatically roll forward as Fixed schedules for use in the RTBM. Real Time Schedule Market Information SPP Market Information on an e-tag Market Date Market Type Transaction Type 9/27/2013 Real Time Fixed Day Ahead Dispatchable Up-to-TUC Bid/Offer MWS are specified in Tag Energy Profile REFERENCE: Market Protocols sections a (Import), a (Export), a (Through) Interchange Scheduling Reference Manual V6 30

32 The following table summarizes the valid combinations and associated Bid information for the SPP Integrated Marketplace: SOURCE Interface A SINK Market Transaction Bid/Offer Combinations WILLINGNESS TO PAY DISPATCHABLE SPP, internal PNode (load) Must be Yes Yes Interface A SPP NA Interface A SPP Yes SPP, internal PNode (generation) Interface A Must be Yes Yes SPP Interface A NA SPP Interface A Yes Interface A Interface B NA Interface A Interface B Must be Yes Yes TAG TRANSACTION TYPE NORMAL OR DYNAMIC INTERCHANGE SCHEDULE TYPES IMPORT OFFER PRICE LMP difference between Interface and Internal MARKET TYPE Up to TUC NORMAL OR DYNAMIC IMPORT Price Taker Fixed NORMAL OR DYNAMIC IMPORT Interface Dispatchable LMP difference between NORMAL OR Interface and DYNAMIC EXPORT Internal Up to TUC NORMAL OR DYNAMIC EXPORT Price Taker Fixed NORMAL OR DYNAMIC EXPORT Interface Dispatchable NORMAL OR DYNAMIC THROUGH Price Taker Fixed LMP difference between NORMAL OR Interface and DYNAMIC THROUGH Internal Up to TUC NOTE: If no market Bid information is submitted with the e-tag, the associated schedule is assumed to be Real-Time Fixed. 6.5 Integrated Marketplace Transaction Types There are three Marketplace Transaction Types supported for tagged Interchange Transactions. They are Fixed, Dispatchable, and Up-to-TUC. Each is discussed below. NOTE: If the Market Transaction type is not explicitly defined in the e-tag, the transaction defaults to Fixed Fixed Interchange Transactions Fixed Interchange Transactions are physical transactions that bring Energy into and/or out of the SPP BAA. Energy prices are settled at the LMP at the applicable External Interface Settlement Location. Submitters of this type of transaction in the Integrated Marketplace are price takers for that Energy. Fixed Interchange Schedules are supported in both the Day-Ahead Market and in the Real- Time Balancing Market. Interchange Scheduling Reference Manual V6 31

33 An e-tag for a Real-Time Fixed Interchange Schedule must be submitted no later than 20 minutes prior to the start of the schedule. The MP must ensure the transaction meets the applicable acknowledgement and transfer deadlines. Real Time Fixed Schedule Market Information choices in Yellow SPP Market Information on an e-tag Market Date Market Type Transaction Type 9/27/2013 Real Time Fixed Day Ahead Dispatchable Up-to-TUC Bid/Offer MWS are specified in Tag Energy Profile A Day-Ahead Fixed Interchange Schedule must be submitted via e-tag and approved by the MP and in the implemented state by the time the Day-Ahead Market closes. Day-Ahead Fixed Interchange Schedules automatically roll into the Real-Time Energy and Operating Reserve Market as a Fixed Interchange Schedule. NOTE: The Day-Ahead Market closes at 0930 CPD OD-1. Day-Ahead Fixed Schedule Market Information choices in Yellow SPP Market Information on an e-tag Market Date Market Type Transaction Type 9/27/2013 Real Time Fixed Day Ahead Dispatchable Up-to-TUC Bid/Offer MWS are specified in Tag Energy Profile If the submitter does not want the cleared Day-Ahead Fixed Interchange Schedule to roll into the Real-Time Balancing Market, the MP must zero out the e-tag no later than 30 minutes prior to the start of the schedule or the start of the operating hour. The MP is settled at the Day-Ahead Location Marginal Price (LMP) for the cleared MW amount and charged for any deviation in the Real-Time Balancing Market at real-time LMPs. NOTE: All Fixed Interchange Schedules Energy prices are settled at the LMP at the applicable External Interface Settlement Location Dispatchable Interchange Schedules Dispatchable Interchange Schedules are physical transactions that bring Energy into and/or out of the SPP BAA and specify a Bid or Offer (MWh). These schedules are supported in the Day-Ahead Market only and also must meet all market requirements. LMPs are determined in the Day-Ahead Market at the appropriate External Interface Settlement Location representing the interface between the SPP BA and the applicable External BA. A Dispatchable Offer specifies both a MW amount and a minimum price that the customer must pay if the transaction clears the Day-Ahead Market. Interchange Scheduling Reference Manual V6 32

34 REFERENCE: SPP Market Protocols section (3) (b) Import Interchange Transaction Offers The following business rules apply to Dispatchable Interchange Schedules: Dispatchable Interchange Schedules must adhere to the Day-Ahead Market timing deadlines. If the Dispatchable Interchange Schedule is cleared in the Day-Ahead Market, it rolls into the Real-Time Balancing Market and is treated as a Fixed Interchange Schedule at the MW level that was determined in the Day-Ahead Market. All Dispatchable Interchange Schedules, both Import Schedules and Export Schedules, are settled at LMPs determined in the Day-Ahead Market at the appropriate External Interface Settlement Location representing the interface between the SPP BA and the applicable external BA. Dispatchable Interchange Schedules cannot be used for Through Interchange Schedules. MPs may use the Market Import Service (MIS) product for Dispatchable Normal Interchange Schedules that are Imports. Dispatchable pricing Offers can be a minimum of $-1000 and a maximum of $1000. Only one price and MW pair per hour is allowed. Partial hour pricing is not permitted. See the example below for input to the Tag Market info section. Interchange Scheduling Reference Manual V6 33

35 Day-Ahead Dispatchable Schedule Market Information choices in Yellow SPP Market Information on an e-tag Market Date Market Type 9/27/2013 Real Time Fixed Day Ahead HE01 HE07 $25 HE13 $20 HE19 HE02 HE08 $20 HE14 $25 HE20 HE03 HE09 $25 HE15 $25 HE21 HE04 HE10 $25 HE16 $30 HE22 HE05 HE11 $20 HE17 HE23 HE06 HE12 $20 HE18 HE24 Transaction Type Dispatchable Up-to-TUC Up-to-TUC Interchange Schedules Up-to-TUC Interchange Schedules are physical transactions created via e-tag that specify a willingness to pay the Transmission Usage Charge (TUC) (in $/MWh) represented by a maximum amount beyond which the MP agrees to be curtailed. These schedules are relevant to the DA Energy and Operating Reserve Market only. An Up-to-TUC Offer on an Interchange Transaction specifies both a MW amount and the maximum amount of congestion cost and marginal loss cost the customer is willing to pay if the transaction is cleared in the Day-Ahead Market. REFERENCE: SPP Market Protocols section (3) (c) Import Interchange Transaction Offer The following business rules apply to Up-to-TUC Interchange Schedules: Up-to-TUC Interchange Schedules are supported in the Day-Ahead Market only and the cleared amount determined by the Day-Ahead Market is rolled into the Real-Time Balancing Market. The transaction must meet all e-tag and market requirements. An Up-to-TUC Interchange Schedule must adhere to the Day-Ahead Market timing deadlines. See example below for input to the Tag Market Info Section. Interchange Scheduling Reference Manual V6 34

36 Day-Ahead Up-to-TUC Schedule Market Information choices in Yellow SPP Market Information on an e-tag Market Date Market Type 9/27/2013 Real Time Fixed Day Ahead HE01 $ 25 HE07 HE13 HE19 HE02 $ 25 HE08 HE14 HE20 HE03 $ 25 HE09 HE15 HE21 HE04 $ 25 HE10 HE16 HE22 HE05 $ 25 HE11 HE17 HE23 HE06 $ 25 HE12 HE18 HE24 Transaction Type Dispatchable Up-to-TUC The TUC is calculated based on the differences in LMPs between the Source points and Sink points. Interchange Scheduling Reference Manual V6 35

37 6.6 Dynamic Interchange Schedules SPP BA and Integrated Marketplace allow Dynamic Schedules. Special business rules apply to the use of Dynamic Schedules. Dynamic Schedules are an estimate. The PSE or the LSE is expected to update the estimate in real time, 20 minutes prior to the new hour, with more accurate base values if the NERC accuracy requirements of dynamic tag are not met. REFERENCE: NERC Reliability Standards Dynamic Schedules are updated to the actual meter value after-the-fact. These dynamic updates to actual must be made prior to Market Settlement processing (OD + 7) External Dynamic Resources (EDR) External Dynamic Resources are resources (or fleets of resources) located in a Balancing Authority outside of the SPP BAA that are modeled as resources internal to the SPP BA. If a customer registers an EDR in the Integrated Marketplace, the EDR must be associated with a tagged Dynamic Schedule. Detailed Business Rules for Integrated Marketplace commitment and dispatch of EDRs are outlined in the Market Protocols. REFERENCE: Market Protocols section Resources External to the SPP BA Business rules specific to EDRs related to TSR and associated Dynamic Schedules are: EDRs must have a confirmed Firm TSR and an associated Dynamic Schedule that represents the total capacity of the EDR. EDR is considered a resource inside the SPP BA. The EDR resource (Source) is mapped to an EDR External Interface Settlement Location for purposes of the Integrated Marketplace settlements. The Transmission Customer must follow all NERC business rules for dynamic tags. EDR business rules are applicable to schedule over HVDC ties. REFERENCE: Market Protocols section Resources External to the SPP BA Pseudo- Tying In REFERENCE: Market Protocols section Resources Internal to the SPP BA Pseudo- Tying Out Interchange Scheduling Reference Manual V6 36

38 6.7 HVDC Ties Transactions that involve High-Voltage Direct Current (HVDC) transmission must indicate the DC tie in the Physical Path section of the e-tag in the SPP market footprint. Each applicable transaction requires confirmed Transmission Service. SWPP is the Transmission Service Provider for the ERCOT DC ties and the Miles City DC tie. The Transmission Provider and Balancing Authorities associated with the DC tie must be specified on the tag. The SPP BA evaluates each tag that delivers Energy over a DC tie to ensure that the Balancing Authority who operates the DC tie is included in the Physical Path section of the tag. The use of the Scheduling Entity field is shown in yellow below. DC tie Tag indicating necessary Scheduling Entities PHYSICAL PATH SECTION OF TAG Source PSE-ID MISO BA TSP MO PSE POR POD S/E MISO MISO PSE-ID IPL CSWS MISO SWPP PSE-ID AMRN ERCOTN SWPP ERCO PSE-ID ERCOT-N ERCOT ERCO ERCO Sink PSE-ID ERCOT SWPP AC Service must also be referenced on the e-tag in coordination with use of the HVDC system. For the above example of a Through transaction over the ERCOT North DC tie, the e- Tag must include three concurrent lines with SPP as Transmission Provider: The first leg, with service from the Source e-tag BA to the HVDC Source point. The second leg, with service on the HVDC transmission line. And the third leg, with service from the HVDC Sinks to the ultimate Sink. SPP is the Transmission Service Provider for the ERCOT DC ties and the Miles City DC tie. This means that SWPP is responsible for selling transmission over these ties and not just up to the tie. REFERENCE: Refer to the Transmission Service Reference Manual, Rules for DC Ties, for more information. Examples of various Physical Path Sections of e-tags for ERCOTE, ERCOTN and MCWEST are shown in Appendix C Tagging Examples. SPP is the Transmission Service Provider for service up to the tie for the other DC ties connected to the SWPP Transmission footprint. The DC ties for which SWPP only sells service to the tie are: Blackwater, Lamar, Eddy, Sydney, Rapid City East, Stegall, and Saskatchewan. Examples of various Physical Path sections of e-tags for these DC ties are shown in Appendix C- Tagging Examples. NOTE: It is not possible to visually view an e-tag to determine if SPP has sold Transmission Service over or to a particular DC tie. It is the responsibility of the Transmission Customer requesting service to know if the DC tie (for which SPP does not sell service over the tie) is in or out of service. Interchange Scheduling Reference Manual V6 37

39 For any DC tie, the PSE or LSE is required to send SPP, in real time, the actual flow of the DC tie. The DC tie tag is included in the RTBM solution; however any Inadvertent of the DC tie will be supplied from the market. The DC tie tag is not included in the NSI of the SPP AGC. The DC tie is not considered a tie line in the SPP AGC HVDC Tie Inadvertent The SPP BA does not include NSI or NAI for HVDC ties in the ACE calculation for AGC. The SPP BA NERC reportable Inadvertent is calculated for the Eastern Interconnection only. The SPP BA is also responsible for coordination of scheduling across HVDC ties. As such, SPP BA calculates and verifies DC tie Inadvertent with the WECC and ERCOT Interconnections. Interchange Scheduling Reference Manual V6 38

40 7 Scheduling Interchange Transactions 7.1 Interchange Schedules An Interchange Schedule is an agreed-upon Interchange Transaction size (megawatts), start and end time, beginning and ending ramp times and rate, and type required for delivery and receipt of power and Energy between Source and Sink Balancing Authorities involved in a transaction. Following is the process for changing a tagged Interchange Transaction into an Interchange Schedule for the SPP BA and Integrated Marketplace. CPSEs submit tagged Interchange Transactions as described in the previous sections of this document. Once the e-tag is submitted and approved, an electronic schedule is created within the SPP Scheduling System (webtrans). Only transactions that enter, exit, or wheel through the market footprint are tagged or scheduled. REFERENCE: Balancing Authority Operations version 1.0 section 6.4. Schedule Implementation 7.2 Electronic Scheduling System (webtrans) SPP uses webtrans for several purposes. SPP members are not required to use webtrans. Purposes of webtrans: Validation of e-tags to become Interchange Schedules Checkout of NSI Calculation of an SPP BA NSI Calculation of the SPP BA Inadvertent Utilize Ramp Reservation functionality There are several different validation processes: Validation of tags against TSR for compliance with the Tariff Validation of tags for compliance with NERC requirements for the SPP BA Validation of tags for compliance with Integrated Marketplace Protocols 7.3 Validation of Tags for SPP Tariff These validations verify that any market Bid/Offer information supplied within a new tag or tag adjustment is valid for the SPP Integrated Marketplace. The following is a brief description of each of the Tag Validation Criteria that supports the Integrated Marketplace Status This validation checks that the status of the OASIS reservation is Confirmed. If the status is not Confirmed, the tag will be denied. Interchange Scheduling Reference Manual V6 39

41 7.3.2 Energy MW This validation checks that the Transmission MWs on the tag do not exceed the TSR(s) Transmission MW. If the Transmission MW on the tag exceeds the reserved amount, the tag will be denied. EXAMPLE: EXPORT Transmission MW do not exceed the Reserved TSR MWH Energy and Transmission Profile Section of Tag SWPP Date Start Stop Gen MW Trans MW #TSR 123 MW Ramp Start Ramp Stop 8/12/ :00 18: NERC Priority This validation checks that the NERC Priority on the tag matches the NERC Priority of the TSR. If the NERC Priority does not match the TSR, the tag will be denied POR/POD This validation checks that the POR and POD on the tag match the TSR. If the POR and/or the POD do not match the TSR, the tag will be denied. NOTE: There are a few exceptions to this rule for WAUW. REFERENCE: Business Practice # 5100 Valid Tag POR/POD Network Service Market Import Service (MIS-NN6) If the tag is for MIS, this validation checks that the LCA on the tag is SWPP. If the LCA is not SWPP, the tag will be denied Source/Sink This validation checks that the Source and/or Sink on the tag match the TSR. If the Source and/or Sink do not match the TSR, the tag will be denied. There are two exceptions to this rule: The TSR has been properly combined with other Transmission Service and both are present on the tag, or The Source/Sink on the TSR is considered electrically equivalent with the Source/Sink on the tag. SPP uses an electrical equivalency mapping table that compares the Source and Sink on the TSR to all possible registered Sources or Sinks that would result in an identical ATC calculation for the SPP. This allows the Source and Sink on the tag to include any number of Sources and Sink that have been registered for use by a PSE as the more granular Settlement Location. The more granular Settlement Locations are needed for different impact on TCR in the Integrated Marketplace. EXAMPLE: The Source on the Transmission Service Reservation is: GRDA. Interchange Scheduling Reference Manual V6 40

42 The Source on the accompanying tagged transaction is: GRDA.GEN.NumB. These Sources are considered electrically equivalent. SPP has HUBs for use when tagging transactions for use in the Integrated Marketplace. There is a North HUB and a South HUB. The following is an itemized list of the Source/Sinks and POR/POD to be used with these tagging HUBs. SPPNORTH_HUB can be used as the Source (or Sink) on a tag when the Source (or Sink) on the TSR is: INDN - or any Source (or Sink) that uses a POR (or POD) of INDN KACY - or any Source (or Sink) that uses a POR(or POD)of KACY KCPL - or any Source (or Sink)that uses a POR(or POD) of KCPL LES - or any Source (or Sink) that uses a POR (or POD) of LES MPS - or any Source (or Sink) that uses a POR (or POD) of MPS NPPD - or any Source (or Sink) that uses a POR (or POD) of NPPD OPPD - or any Source (or Sink) that uses a POR (or POD) of OPPD SECI - or any Source (or Sink) that uses a POR(or POD) of SECI SPC - or any Source (or Sink) that uses a POR (or POD) of SPC WAUE - or any Source (or Sink) that uses a POR(or POD) of WAUE WPEK - or any Source (or Sink) that uses a POR (or POD) of WPEK WR - or any Source (or Sink) that uses a POR (or POD) of WR SPPSOUTH_HUB can be used as the Source (or Sink) on a tag when the Source (or Sink) on the TSR is: CSWS - or any Source (or Sink) that uses a POR (or POD) of CSWS EDE - or any Source (or Sink) that uses a POR (or POD) of EDE GRDA - or any Source (or Sink) that uses a POR (or POD)of GRDA OKGE - or any Source (or Sink) that uses a POR (or POD) of OKGE SPRM - or any Source (or Sink) that uses a POR (or POD)of SPRM SPS - or any Source (or Sink) that uses a POR (or POD) of SPS WFEC - or any Source (or Sink) that uses a POR (or POD) of WFEC EXAMPLE: If the Source on the TSR is: CSWS or CSWS.ONETA, the Source on the accompanying tagged transaction may be SPPSOUTH_HUB REFERENCE: Business Practice # 5150 Valid Tag Source/Sink REFERENCE: Business Practice # 5050 Schedule Timing Requirements REFERENCE: Business Practice #5200 Tag Denial Criteria REFERENCE: Business Practice #5250 Late Schedules Interchange Scheduling Reference Manual V6 41

43 REFERENCE: Business Practice #5300 Schedule Denial Criteria REFERENCE: Business Practice #5400 Tag Cancellation, Termination, Withdrawal or Correction REFERENCE: Business Practice #5450 Loss Provision Requirements for Network Integration Transmission Service 7.4 Validation of Tags for SPP Balancing Authority Following are validations performed on tagged transactions prior to confirmation and approval by the SPP BA Late Start/Late This validation checks that the tag s start time is not earlier than the current actual time and that the tag follows market timing rules. If the tag is late, it will be denied Energy Profile This validation checks that the Transmission MW is greater than or equal to the Generation MW on the tag. If the Generation MW on the tag is greater than the MW on the TSR, the tag will be denied Physical Path This validation checks the proper upstream and downstream adjacency of various entities identified within the physical path of the tagged transaction: The validation ensures that the GCA and LCA are properly associated. SWPP cannot be entered as both the GCA and the LCA on a tag. The validation checks that the appropriate Scheduling Entity has been included in the correct order for the Transmission Provider with the POR/POD. If any of the above validations fail, the tag will be denied SPP Ramp Validation Refer to Section 5.5 e-tag Ramp Validation for information on ramp validation. Interchange Scheduling Reference Manual V6 42

44 7.5 Validation of Tags for Integrated Marketplace SPP Market Bid/Offer SPP verifies that any market Bid/Offer information supplied within a tag or tag adjustment is valid for the SPP Integrated Marketplace. If no market Offer/Bid information is included in the Market Information Section of the tag, the tag will pass validation and become a Real-Time Fixed transaction for Integrated Marketplace. If any market Offer/Bid information has been supplied in the tag, the following validations are performed: Validation that there are not multiple instances of the same Market Data as recognized by SPP Integrated Marketplace on any tagged transaction. Validation that data included in the Market section of a Dispatchable/Wheel/Normal Energy tag transaction is a valid and acceptable combination of Bid attributes for the SPP Integrated Marketplace. Validation that no additional Bid/Offer data has been entered into the Market section of the tagged transaction for market transaction types that are not allowed to have associated Bid/Offer information SPP Market Timing For Day-Ahead SPP verifies that any tag or tag adjustment submitted with market Bid information meets defined timing requirements. For tags or tag adjustments specified as Day Ahead, the following additional timing validations are performed: If the tag start/stop profile does not correspond with the date as specified in the Market Date, the tag will fail validation and will be denied with the reason violates timing. If the Market Date is more than 7 days in advance of the tag submission timestamp (or, in the case of a monthly tag, more than 7 days in advance of the first day of the tag), the tag will fail validation and will be denied. If the tag submission timestamp is later than the Day-Ahead Market closing time for the Operating Day as specified in the Market Date, the tag will fail validation will be denied SPP Marketplace Settlement Location The Market Location validation verifies that valid SPP Integrated Marketplace Settlement Location names have been mapped to the e-tag Source/Sink and/or POR/POD service points. If a valid mapping between the e-tag points and a Settlement Location name cannot be resolved, the tag will be denied. Interchange Scheduling Reference Manual V6 43

45 For e-tags where SWPP is designated as the GCA, the SPP Source Market Location is based on a lookup of the e-tag Source and Source PSE against the corresponding market name mapped to that Source. If there is no corresponding mapping information for the e-tag Source and Source PSE or SWPP is not the GCA, the POR on the first Transmission Physical Segment listing SWPP as the TSP is used. For e-tags where SWPP is designated as the LCA, the SPP Sink Market Location is based on a lookup of the e-tag Sink and Sink PSE against the corresponding market name mapped to that Sink. If there is corresponding mapping information for the e-tag Sink or SWPP is not the LCA, the POD on the last Transmission Physical Segment listing SWPP as the TSP is used SPP Market Losses The Market Losses validation enforces the provision that all transmission loss compensation within the SPP Integrated Marketplace is handled financially. The Tag Transaction Type must be FIN. If the Energy profile of any tag has a MW value at the SPP POR that is different from the value at the SPP POD (i.e., in-kind loss delivery), the tag will be denied. Loss Accounting Section of tag with Financially Settled Losses Loss Accounting Section of Tag EXAMPLE: Financial Losses TSP Start Time Stop Time Type Contract Number PNM 7/31/ :00 7/31/ :00 FIN EPE 7/31/ :00 7/31/ :00 FIN SWPP 7/31/ :00 7/31/ :00 FIN ERCO 7/31/ :00 7/31/ :00 FIN 7.6 Curtailments and Adjustments NERC Transmission Loading Relief (TLR) SPP Operators take appropriate actions as GCA and/or LCA and verify that all other required schedule adjustments have been made. Per NERC requirements, curtailments can never be greater than a tag s Energy profile. Additionally, a PSE adjustment cannot be greater than the Energy profile during an implemented curtailment. Even if these excessive adjustments are implemented, the Energy profile of the e-tag always reflects the lower amount. SPP denies curtailments or PSE adjustments that violate the NERC Standards Market Adjustments Day-Ahead tagged transactions that are not cleared by the Day-Ahead Market for their full MW value will be adjusted automatically to the amount cleared. The results of the Market Clearing process appear on the tag via a Market Adjustment. If the Market process is delayed due to unforeseen circumstances, the Market Adjustment will be applied to the tag on the following quarter hour. Interchange Scheduling Reference Manual V6 44

46 If a Market Adjustment is denied by a non-spp entity, or is approved by an entity after the Reoffer period closes, the PSE is responsible to either provide the Energy in the Real-Time Balancing Market or adjust the schedule to the market adjusted value. PSEs are not allowed to adjust, correct, or extend Day-Ahead tags while the Day-Ahead Market processes. REFERENCE: Refer to Section for a timeline. Market Adjusts may also occur for reasons outside of Day-Ahead Market Clearing. These reasons include: If any electronic communication problems occur within the SPP Integrated Marketplace that result in inconsistencies between the Market Clearing result and any physical Day- Ahead Schedule profile, SPP issues manual Market Adjustments to correct the inconsistent schedules. The manual Market Adjustments may be issued at any time before or within the duration of the schedule. If the SPP Reliability Unit Commitment (RUC) system identifies a reliability-based need for a curtailment or adjustment, the SPP Balancing Authority issues a manual Market Adjustment to the scheduled transaction via the e-tag. SPP BA RUC adjusted schedules do not allow the TC/PSE approval/denial rights. Entities with approval rights must take approval actions. Interchange Scheduling Reference Manual V6 45

47 Appendix A: Special Tagging Helpful Information User Options: OATI Users/Non- OATI Users OATI Users For those entities using Open Access Technology, Inc. (OATI) as their tagging vendor, the SPP market information of the tag can be added as follows: After logging into OATI tagging software: 1. Click Options from the main toolbar. 2. Select Tagging Options. 3. Under Tag Display Options, click the box entitled Enable SPP market information. 4. Click Apply. SPP Market Information Specification for Non-OATI Users Market Participants should contact their tagging vendor to determine Market specification requirements. Market Information on Tags To view the SPP market information on the e-tagging software, the MP selects the checkbox for Enable display of SPP market information. User Access Admin for OATI Users Each authorized user in the webtrans Production environment is required to use an SSLsecured user login through the presentation of a valid OATI webcares issued x.509 certificate along with a recognized user name and password to provide for two-factor authentication. OATI certificates must be issued by the authorized Security Officers of each end entity that will be granted a user account in webtrans. Once granted access to webtrans, the menu options available to the user are governed by the specific user permissions granted to that user account. As each user is logged into webtrans, webtrans attempts to establish a remote login session to the websmarttag to facilitate the viewing of e-tag information directly from hyperlinks presented on the webtrans Scheduling and Tag Validation related displays. Remote login access to the websmarttag requires that the user s x.509 certificate has been associated with a valid, active user account in the websmarttag. OATI Help Desk facilitates the registration of all websmarttag user accounts for each individual webtrans user. Interchange Scheduling Reference Manual V6 46

48 Daylight Savings Time Options for Spring Forward (Change to CDT) As shown below, users may build one or two tags for transactions that will be scheduled across the spring time change. Regardless of how the tags are built across the time change, the time change to CDT will result in a 23-hour Operating Day for the first day. Two-Tag Option for Change to CDT Using a two-tag option will result in the first tag being created for the first one or two hours of the current CST and the second tag built in CDT for the remaining hours that will equal a 23 hour Operating Day. Depending on how the user elects to create the two tags for the Operating Day of the time change (see Option A and B examples), there will be either no HE 0200 or HE 0300 between the two tags. This is necessary in order to ensure that a 23 hour day has been scheduled for the Operating Day. Option A (no HE 3 shown between tags) 1. Create the first tag in CST for first two hours of the Operating Day: a. Start the tag at b. End the tag at Create the second tag in CDT: a. Start the tag at b. End the tag at 0000 (HE 24) for a total of 23 hours. Option B (no HE 2 shown between tags) 1. Create the first tag in CST for first hour of the Operating Day: a. Start the tag at b. End the tag at Create the second tag in CDT: a. Start the tag at b. End the tag at 0000 (HE 24) for a total of 23 hours. Interchange Scheduling Reference Manual V6 47

49 EXAMPLE: Change to CDT (Spring) Option A Change to CDT (Spring) Option B One Tag Option for Change to CDT Users may build just one tag, either in CST or CDT, to accommodate the time change. One Tag Created in CST 1. Start the tag at End the tag at 2300 for a total of 23 hours. One Tag Created in CDT 1. Start the tag at End the tag at 0000 (HE 24) for a total of 23 hours. Interchange Scheduling Reference Manual V6 48

50 Options for Fall Back (Change to CST) Users may build one or two tags for transactions that will be scheduled across the fall time change. Regardless of how the tags are built across the time change, the time change to CST will result in a 25 hour Operating Day for the first day. Two-Tag Option for Change to CST Using a two-tag option will result in the first tag being created for the first two hours of the current CDT and the second tag built in CST for the remaining hours that will equal a 25 hour Operating Day. This will result in HE 2 being repeated for the Operating Day. This is necessary in order to ensure that a 25 hour day has been scheduled for the Operating Day. 1. Create the first tag in CDT for first two hours of the Operating Day: a. Start the tag at b. End the tag at Create the second tag in CST: a. Start the tag at b. End the tag at 0000 (HE 24) for a total of 25 hours. One-Tag Option for Change to CST 1. Start the tag at End the tag at 0100 on the following Operating Day for a total of 25 hours. NOTE: Since Day-Ahead tags are validated by Operating Day, this one-tag option is not viable for Day-Ahead tags. EXAMPLE: Change to CST (Fall) Interchange Scheduling Reference Manual V6 49

51 Recognizing the Right Tag/Schedule The time zone settings are user specific and display all tags in the time zone selected. This means that time on the tag may not display correctly depending on the user s specific time zone settings. Changing Time Zone Settings (OATI Users) The Change Time Zone display allows the user to change the time zone for the data being displayed in websmarttag. This setting is user specific and determines the time zone in the main websmarttag display and determines the default time zone in the entry displays. 1. Within websmarttag, select Misc>Misc User Options, then select the appropriate time zone from the drop down list. 2. Click Submit to save the selection. Interchange Scheduling Reference Manual V6 50

52 Appendix B: Tagging Information SPP Specific for Market Participants submitting RFI to SPP Marketplace The following information is provided to assist customers who submit e-tags to the SPP Marketplace. SPP does not train customers on how to submit e-tags. Customers are expected to understand NAESB Industry e-tag Business Practices and Specifications. Customers have a choice of e-tag vendors. For general e-tag questions customers should contact their e-tag vendor. However, SPP does have specific requirements for certain data fields within the e-tag. This document outlines the specific Business Practices that SPP requires. The visuals are generalized mock up and do not represent any specific e-tag vendor displays or systems. When a customer submits and e-tag the e-tag data is submitted to the SPP Electronic Scheduling System. The SPP Tariff and Interchange Operators use the Scheduling System automated validations to evaluate specific data fields of the e-tag for compliance with SPP Business Practices. If the data does not comply with SPP Business Practices the SPP Operator will deny the tag. Tag Information Section Box 1 - SPP does not perform validations on data in Box GCA (Generating Control Area): Balancing Authority in which the Generation/Resource resides. This will be the same as the first CA in the Physical Path section. Resources can be electrically equivalent to loads and loads can be electrically equivalent to generators. An example is a wind farm that is out of service may need to take station service Energy from the grid and therefore could be a load. 2. PSE: The creating PSE does not have to be same as the PSE who owns transmission, therefore the CPSE does not have to be the same as the SPP Market Participant. 3. Tag Code: Most important part of the ID; must be unique and not repeated. 4. LCA (Load Control Area): Balancing Authority in which the load/resource resides. This will be the same as the last CA in the Physical Path section. Interchange Scheduling Reference Manual V6 51

53 Box 2 -SPP does not perform validations on data in Box Start Date: Date and time the Energy will begin to flow on the grid 2. Stop Date: Date and time the Energy will stop flowing on the grid 3. Time Zone: SPP operates in Central Prevailing Time. 4. Transaction Type: Currently, SPP only allows Normal, Emergency, and Dynamic types. 5. Tag MWH at generator (original/final): (e-tag specifications) Contact Information Section SPP only performs Scheduling validations on the Comment field. 1. PSE Code: Creating PSE code; same as in Tag Information section (e-tag specifications) 2. PSE Contact: SPP will use this contact if the TI Operator needs to communicate with the Creating PSE. 3. PSE Phone: SPP will use this contact if TI Operator needs to communicate the Creating PSE. 4. PSE Fax: (e-tag specifications) 5. Gen Contact: (e-tag specifications) 6. Gen Phone: (e-tag specifications) 7. Gen Fax: (e-tag specifications) 8. Load Contact: (e-tag specifications) 9. Load Phone: (e-tag specifications) 10. Load Fax: (e-tag specifications) 11. Comment: Customer uses this for special situations that need clarification. Specifically, for tags used to identify special contract information like Loss Repayment Schedules for WAUW. SPP does not allow the comment field to contain inadvertent or INAD. Interchange Scheduling Reference Manual V6 52

54 Requests Section SPP does not perform validations on data in this section. 1. Req: Shows the order in which various changes/modifications were made to the tag. First will be creation of the tag. (e-tag specifications) 2. Type: Modifications to a tag; can include adjustments, curtailments, market adjustments, etc. (e-tag specifications) 3. Author: PSE code that initiated the modification, not always the same as the Creating PSE (e-tag specifications) 4. Time: (e-tag specifications) 5. Status: Shows if e-tag has reached a final state (e-tag specifications) Market Path Section SPP does not perform validations on data in this section. 1. PSE: (e-tag specifications) 2. Product: (e-tag specifications) 3. Contract: (e-tag specifications) 4. Misc: Shows that data was sent via XML (e-tag specifications) Interchange Scheduling Reference Manual V6 53

55 Market Information Section SPP Scheduling System Automated Validations for this section are: Verification of SPP Market Bid/Offer Verification of SPP Market Timing Market Date 9/27/2013 SPP Market Information on an e-tag Market Type Real Time Day Ahead Transaction Type Fixed Dispatchable Up-to-TUC HE01 HE07 $25 HE07 $20 HE07 HE02 HE08 $20 HE08 $25 HE08 HE03 HE09 $25 HE09 $25 HE09 HE04 HE10 $25 HE10 $30 HE10 HE05 HE11 $20 HE11 HE11 HE06 HE12 $20 HE12 HE12 Refer to Section 6.4, Market Types, for information on filling out this section. NOTE: This is a confidential section that can only be seen by the creating PSE. Physical Path Section SPP verifications are performed for numerous items for this section of the tag. The verifications are done to ensure that the appropriate BAs and TSPs are shown in the correct order and with the correct adjacencies to all intermediate entities for delivery of the Energy and for BA checkout processes. Verifications are also performed to ensure required fields are populated (including the MO field). The verifications are: Verification of physical path ensures upstream and downstream physical path segments are adjacent. If they are not, the SPP Operator will deny the tag. Verification that the Source/Sink matches or is electrically equivalent to OASIS TSR specified for the transaction. If it is not, the SPP Operator will deny the tag. Verification that the POR/POD shown on the SWPP Transmission Segment line matches the OASIS TSR specified for the transaction. If they do not, the SPP Operator will deny the tag. NOTE: There are a few exceptions to this rule for WAUW. Verification that SWPP is listed as the MO on the tag if the SWPP is the LCA or GCA. Verification that an old SWPP Legacy BA has not been used as GCA/LCA or Scheduling Entity. If has, the SPP Operator will deny the tag. Interchange Scheduling Reference Manual V6 54

56 Verification that the Scheduling Entity field is populated correctly for the line where SWPP is the TSP. If it is not, the SPP Operator will deny the tag. NOTE: WAUW is not a legacy BA for SWPP and therefore this validation does not apply for WAUW. WAUW has its own rules for being included in the SE field. Verification that SWPP is not shown more than once in the SE Column. If it does, the SPP Operator may deny the tag. There are a few exceptions to this rule. Verification to ensure that the Source/Sink is registered and mapped to a valid SWPP Marketplace Settlement Location in the SWPP Centralized Modeling Tool. If the Source/Sink is not registered with SWPP, the SPP Operator will deny the tag. 1. BA (Balancing Authority): Starting point for the generation. The BA in which the generation resides. For a tag exporting Energy from the SWPP Marketplace, the Gen BA must be SWPP. For a tag importing to the SWPP Marketplace, the Load BA must be SWPP. 2. TSP (Transmission Service Provider): For any transaction including SWPP Marketplace, at least one line with a TSP of SWPP must be present. 3. PSE (Purchasing and Selling Entity): SPP does not validate the PSE column of the e-tag. (e-tag specifications) 4. MO (Market Operator): SWPP must be designated as MO on the line where SWPP is the Source or Sink (GCA or LCA). 5. POR (Point of Receipt): The electrical point at which the particular TSP receives or picks up the Energy and then sends it through the grid. POR does not indicate transfer of ownership of the Energy. POR is used in AFC and ATC calculations as well as transmission billing. SWPP validates that the POR for each leg of SWPP Transmission is valid and is correct for the OASIS TSR used for the transaction. 6. POD (Point of Delivery): The electrical point at which the particular TSP hands off the Energy to the next TSP. POD does not indicate transfer of ownership of the Energy. POD is used in AFC and ATC calculations as well as transmission billing. SWPP validates that the POD for each leg of SWPP Transmission is valid and is correct for the OASIS TSR used for the transaction. 7. Sched Entities: Used to indicate the BA through which the power flows, because the BA and the TSP are not always the same entity. The purpose is to ensure proper BA adjacency for NSI calculation and checkout processing. The BAs must be listed in the correct order. 8. Contract: SPP does not use this column. (e-tag specifications) 9. Misc (Token/Value): SPP does not use this column. (e-tag specifications) Interchange Scheduling Reference Manual V6 55

57 Energy and Transmission Profiles Section SPP Scheduling System Automated Validations for this section are: Verification of Energy MWs ensures enough scheduling rights remain to cover the Energy MW profile on the transaction. If the TSR does not have enough remaining MWs for the e-tag, the SPP Operator will deny the tag. Ramp is validated as outlined in section 5.5 e-tag Ramp Validation. SWPP will deny the tag if the tag does not pass ramp validation. Verification that the Generation MW and Load MW are equal. If they do not equal, the SPP Operator will deny the tag. Verification ensures that the tag profile does not change in the last or first 10 minutes of a tag. If it does, the SPP Operator will deny the tag. Verification that the Ramp Duration is identical for the duration at the start time and the duration at the stop time in minutes. If it is not, the SPP Operator will deny the tag. 1. Date: (e-tag specifications) 2. Start: SWPP allows intra-hour changes to MW profiles. However no changes are allowed within the top 10 minutes of the hourly profile. (e-tag specifications) 3. Stop: SWPP allows intra-hour changes to MW profiles. However, no changes are allowed within the last 10 minutes of the hourly profile. (e-tag specifications) 4. Gen MW: SWPP requires the Gen MWs to match the load MWs for the e-tag. (e-tag specifications) 5. Transmission Service by TSP: SWPP TSP must be included in the correct order based upon the Physical Path section of the e-tag. (e-tag specifications) 6. Trans, TSR, MW: MWs must not exceed the capacity of the TSR used for the leg of the transaction. (e-tag specifications) 7. Ramp Duration Start/ Stop: Eastern Interconnection default ramp duration is 10 minutes. Western Interconnection default is 20 minutes for tags that start at the top of the hour, or 10 minutes for start times other than the top of the hour. Default ramp time duration for tags that cross the Eastern and Western Interconnection are 20 minutes for tags that start at the top of the hour, and 10 minutes for tags that start at times other Interchange Scheduling Reference Manual V6 56

58 than the top of the hour. SPP allows the customer to determine the Ramp dependent upon Interconnection requirements. Transmission Allocation Section SPP Automated Validations for this section are: Verification that the TSR OASIS number is valid. If it is not, the SPP Operator will deny the tag. Verification that NERC Priority/Product on the tag matches the NERC priority on the OASIS TSR. If it does not, the SPP Operator will deny the tag. Verification that TSR OASIS number is confirmed in OASIS and ready to be used. If it is not, the SPP Operator will deny the tag. 1. TSP: Transmission Service Provider shown in the same order as in the Physical Path and Energy and Transmission Profile sections. Includes at least one entry for each TSP. Must include SWPP TSP for ALL transactions for SPP Marketplace and WAUW Transmission Service. 2. Owner: Customer that owns the Transmission. Should correspond to the Owner/Customer of the OASIS TSR number. NOTE: SWPP uses the Owner/Customer of the OASIS TSR to determine MP/TC/AO for SWPP Marketplace settlements regardless of what text is entered in this field of the tag. 3. Product: Transmission Service NERC Priority. Must match the NERC Priority on the OASIS TSR. 4. OASIS Transmission Service Request ID number. Must correspond to valid TSR number in OASIS. 5. NITS Resource: SWPP does not use this column. (e-tag specifications) 6. MISC: SWPP does not use this column. (e-tag specifications) Carbon Copy List Section FERC (PSE) is required on all tags. This section specifically allows FERC to see every tag in North America. It is a FERC requirement to be included on all tags. Interchange Scheduling Reference Manual V6 57

59 Loss Accounting Section SPP does not perform automated validations on data in this section. 1. TSP (Transmission Service Provider): Includes all TSPs listed in the other sections of the tag. (e-tag specifications) 2. Start Time: Must correspond to physical path start time. (e-tag specifications) 3. Stop Time: Must correspond to physical path stop time. (e-tag specifications) 4. Type: SPP Market Protocols (Attach AE of the Tariff) only allows financial settlement of losses which is Type=FIN. SPP Systems do not validate this section of the tag. It is the responsibility of the customer to enter the correct type for their own reporting purposes. (e-tag specifications) REFERENCE: Market Protocols section 4.5 Post Operating Day and Settlement Activities 5. Data: SPP does not use this column. (e-tag specifications) Interchange Scheduling Reference Manual V6 58