OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17,...

25
OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

description

OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004. Stage 1 Components. Participant Registration Key Liaison - NERC User Registration Key Liaison - NERC Market Resource Registration Key Liaison – NERC & IRC Publish/Subscribe - PowerPoint PPT Presentation

Transcript of OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17,...

Page 1: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

OASIS IIStage 1 Requirements

Joint OASISII Implementation Task Force Paul R. Sorenson

November 17, 2004

Page 2: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Stage 1 Components Participant Registration

Key Liaison - NERC User Registration

Key Liaison - NERC Market Resource Registration

Key Liaison – NERC & IRC Publish/Subscribe

Key Liaison - none Operations Data Exchange

Key Liaison – NERC & IRC Auction Transmission Markets

Key Liaison - IRC

Page 3: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Participant Registration

Central Registry Requirements Identify Business Entity Identify Business Role(s) Identify Contact Information

Market Registry Requirements Identify Business Entity

• Key to Central Registry? Identify Market Access

• Markets (e.g., Transmission, Energy, etc.)• Market Resources Owned/Operated• Market Agreements/Contracts

Page 4: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Participant Registration Submit Participant Registration

Participant ID Participant State (e.g., Accepted, Denied) Activation date/time Deactivation date/time Legal business name of the Participant organization Industry recognized business identifier (e.g., DUNS number, etc.) Address Contact information (phone, FAX, etc.) Method(s) of establishing creditworthiness Roles played in the market:

• PSE LSE GPE

• Transmission Customer• Transmission Owner• Transmission Operator• Generation Owner• Generation Operator• Reliability entity

Reliability Authority Balancing Authority

Market services being requested; initial service agreement application. (May be inferred by market role, e.g., GPE must execute interconnection agreement(s), TCs must execute pro-forma service agreements, etc.).

Other market-dependent information requirements

Page 5: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Participant Registration

Modify Participant Registration Change/add/delete subset of registered data

Set Participant Registration State Acknowledge Acceptance or Denial of registration request

View Registration Generic query for registration information

Page 6: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

User Registration

Central Registry Requirements None?

Market Registry Requirements Identify Business Entity Identify User Identify User Roles Identify User Market Access (subset of Participant’s)

• Markets (e.g., Transmission, Energy, etc.)• Market Resources Owned/Operated

Page 7: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

User Registration Submit User Registration

User ID User State (e.g., Accepted, Denied) Activiation date/time Deactivation date/time Legal business name of the User's Participant organization (or Participant ID) User name Address Contact information (phone, FAX, etc.) e-MARC certificate information (one or more):

• user's distinguished name• certificate issuer's distinguished name

Roles played in the market (access rights/privileges):• User Administrator• Energy Market Participant• Transmission Rights Market Participant• Scheduler• Reliability operator• Etc.

Other market dependent user registration information

Page 8: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

User Registration

Modify User Registration Change/add/delete subset of registered data

Set User Registration State Acknowledge Acceptance or Denial of registration request

View Registration Generic query for registration information

Page 9: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Market Resource Registration Facilities

Physical• Generator• Station• Line• Etc.

Resources Commercial

• Source/Sink• POR/POD• Location

Hub Load Aggregate

• Etc. May Map to Facility(ies)

Others?

Page 10: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Market Resource Registration Central Registry Requirements

POR/PODs Source/Sinks Transmission Product (Attributes) Path Names? Location Names (e.g., p-nodes, hubs, load aggregates, etc.)? Commercial Mapping? Network Model Mapping? Key to Market Registry?

Market Registry Requirements Key to Central Registry? Identify Facilities Identify Resources

Page 11: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Market Resource Registration Submit Facility Registration

Facility ID Facility State (e.g., Accepted, Denied) Activation date/time Deactivation date/time Facility name Facility type (e.g., generator, station, meter, etc.) Facility sub-type, if applicable (e.g., coal fired, nuclear, etc.) Owner(s) Operator Operational status (e.g., construction, in-service, decommissioned, etc.) Ratings Other market dependent facility specific information Model data as required to support the market/network model

Page 12: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Market Resource Registration Submit Resource Registration

Resource ID Resource State (e.g., Accepted, Denied) Activation date/time Deactivation date/time Resource name Resource type (e.g., generation, load, transmission, pricing, etc.) Resource type specific sub-type, if applicable (e.g., POR, POD, Flowgate, etc., for

transmission; node, zone, hub, etc. for pricing) Associated Facility(ies) or other Resources, if applicable (e.g., generator facilities

and weighting factors for generation resources; price nodes and weighting factors for zone pricing resources)

Market Participant allowed to bid/offer the Resource (i.e., owner) Resource limits, default bid parameters, etc., if applicable Other market dependent Resource registration information

Page 13: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Market Resource Registration

Modify Facility Registration Change/add/delete subset of registered data

Set Facility Registration State Acknowledge Acceptance or Denial of registration request

Modify Resource Registration Change/add/delete subset of registered data

Set Resource Registration State Acknowledge Acceptance or Denial of registration request

View Registration Generic query for registration information

Page 14: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Publish/Subscribe Submit Subscription

Subscription ID Subscription State (e.g., normal, suspended) Activation date/time Deactivation date/time Delivery location/method

• Uniform Resource Identifier or Locator (URI/URL) of system to be notified• Protocol (e.g., HTTP(S); email, etc.)

Identification of data being subscribed to:• "Category", e.g., Transmission, Registration, etc.• "Type", e.g., Deals, Participant, etc.• “Event”, e.g., Set TR Auction Bid/Offer State

Optional data filter qualifiers (nature dependent on data subscribed to)• Market Participant(s)• Resource(s)

Optional Subscriber specific context information to be included in each notification message sent to Subscriber.

Page 15: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Publish/Subscribe

Modify Subscription Change/add/delete subset of registered data

Notify Subscribers On Data Event

• Identify Subscribers• Issue Notifications

View Registration Generic query for subscription information

Page 16: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Operations Data Exchange

Submit Outage Outage ID Outage State Activation date/time Deactivation date/time Facility name Outage type (e.g., planned, unplanned, etc.) Outage start date/time Outage stop date/time Updated facility ratings during outage General terms for deferring or accelerating outage including costs

Page 17: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Operations Data Exchange

Modify Outage Change/add/delete subset of outage data

Set Outage State Acknowledge Acceptance or Denial of outage request

View Operations Data Generic query for operations data

Page 18: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Operations Data Exchange

Submit Load Forecast Load Forecast ID Load Forecast State Load Identifier (e.g., name) Load Location (e.g., node, zone, etc.) Load Profile

• MW• Start date/time• Stop date/time

Page 19: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Operations Data Exchange

Modify Load Forecast Change/add/delete subset of load forecast data

Set Outage State Acknowledge Acceptance or Denial of load forecast

View Operations Data Generic query for operations data

Page 20: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Auction Transmission Market

Post TR Auction Announcement Free-form Data

• Network Model information• Assumptions regarding system conditions:

Total load forecasts Major facility outages Contingent elements

• Transfer Capability eligible for auction• Auction rules

Page 21: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Auction Transmission Market

Post TR Auction Announcement XML Data

• Auction ID• Auction State (e.g., Pending, Open, Closed)• Activation date/time• Deactivation date/time• Auction Name• Auction Round• Auction Timing

Open/Close Clearing

• Auctioned Rights Products (e.g., on-peak obligation, etc.) Start/Stop

Page 22: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Auction Transmission Market

Submit TR Auction Offer/Bid Offer/Bid ID Offer/Bid State (e.g., Accepted, Cleared) Customer Identifier (Seller/Buyer) Auction ID Auction Rights (e.g. on-peak option) Quantity Offer/Bid, MWs Price Receipt Point (Injection); for point-to-point products Delivery Point (Withdrawal); for point-to-point products Transmission Resource (i.e., Flowgate) for path type products Exchange TR Auction Bid/Offer ID

Page 23: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Auction Transmission Market

Modify TR Auction Offer/Bid Change/add/delete subset of offer/bid data

Set TR Auction Offer/Bid State Acknowledge Market Clearing Results

• Auction Offer/Bid ID• Auction Offer/Bid State (e.g., Cleared)• Auction Clearing Price• Auction Cleared Rights MWs

Page 24: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Auction Transmission Market View Transmission Rights

Generic query for transmission rights information• Customer Identifier (Owner)• Type of rights held (Product) (e.g. annual point-to-point CRR obligation, monthly

flowgate CRR option)• Purchase Price (if applicable)• Rights Profile

Quantity (MWs)* Start time of rights Stop time of rights

• Receipt Point (Injection); for point-to-point products• Delivery Point (Withdrawal); for point-to-point products• Transmission Resource (i.e., Flowgate or Path)• Information tracking how and from where rights acquired:

By Allocation At auction From TSP From secondary market resale From secondary market transfer

Page 25: OASIS II Stage 1 Requirements Joint OASISII Implementation Task Force Paul R. Sorenson November 17, 2004

Auction Transmission Market View Transmission Rights

* "Quantity" may be represented by multiple data elements to reflect:• Quantity purchased/sold – used for settlements• Quantity held – reflects current rights less any auction or bilateral secondary

market resales/reassignments• Quantity committed – reflects rights currently being used or otherwise not

available for resale (i.e., scheduled use in physical rights markets, offered into auction for financial rights markets, pending resale/reassignment, etc.)