Future Of OASIS Conference March 29, 2005 Future of OASIS Conference Related Industry Initiatives...

Future Of OASIS Conference March 29, 2005

Future of OASIS Conference

Related Industry InitiativesNAESB - Robert Harshbarger

OASIS IA Task Force and ESS OASIS II Task Force•Origins and History•Visions and Scopes•OASIS IA Business Standards Development•OASIS II Functional Areas and System Requirements•OASIS II Staged Implementation


Future of OASIS ConferenceRelated Industry InitiativesNAESB

Ask the experts -Sharon Miller Paul Sorenson Jagjit SinghAndy Rodriquezand many others


WEQ EC created the ESS & ITSAugust 5, 2003 Meeting Minutes, Philadelphia, PA

Ms. McQuade clarified the Executive Committee has established two subcommittees, the Technical Subcommittee and the ESC Subcommittee, to serve as a home for any ESC/OSC deliverables found to be within NAESB’s business standards development scope, and also to address requests that would have been made to the ESC/OSC regarding business standards issues. The establishment of these subcommittees creates an opportunity for ESC/OSC participants to continue their work within the NAESB framework, where appropriate. Additionally, she noted a goal would be to maintain existing ESC/OSC leadership and participation. Ms. McQuade stated this information will be presented at the ESC/OSC meeting on August 25 in Vancouver.


ITSOctober 8, 2003 Kick-off Meeting, Tempe, AZWEQ Information Technology SubcommitteeMission StatementThe Information Technology Subcommittee is a technical subcommittee of the Wholesale Electric Quadrant Executive Committee assigned to develop standards and communication protocols for Open Access Same-Time Information Systems. The Information Technology Subcommittee will engage in, but is not limited to, the following activities:

Maintain the OASIS Phase IA S&CP document once adopted by NAESB as a standard

Actively develop standards and communication protocol [technical standards] for OASIS Phase II

Work with NERC’s TISWG to determine the future of the TSIN Registry

Coordinate with NERC’s PKI Task Force regarding the implementation of NERC’s e-MARC policy.


ESSDec 15-16, 2003 Kick-off Meeting, FERC Offices, Washington, D.C.WEQ Electronic Scheduling SubcommitteeMission StatementThe Electronic Scheduling Subcommittee is a subcommittee of the Wholesale Electric Quadrant Executive Committee assigned to develop business practice standards associated with Electronic Scheduling of power transactions as well as business practice standards associated with Open Access Same-Time Information Systems. The Electronic Scheduling Subcommittee will engage in, but is not limited to, the following activities:

Develop NAESB business practice standards that are consistent with FERC Orders 605, 638, and 889, 889-A, and 889-B.

Maintain business practices associated with OASIS Phase I-A by facilitating future additions, modifications, and enhancements to those business practices


ESSDec 15-16, 2003 Kick-off Meeting, FERC Offices, Washington, D.C.WEQ Electronic Scheduling SubcommitteeMission Statement (continued)Develop and maintain business practice standards associated with NERC’s efforts to convert Policy 3 into appropriate Reliability standards, including:

•Direct the efforts of the NAESB “Coordinate Interchange Business Practices Task Force” as they develop business practice standards related to NERC’s “Coordinate Interchange Standard Drafting Team”

•Coordinate with NERC’s TISWG regarding business practice issues associated with Etag implementation

Using the Use Cases and other deliverables of the Electronic Scheduling Collaborative as a model template,

•identify core functionality, design, and behavior of OASIS Phase II, and

•develop and maintain business practices necessary to implement OASIS Phase II.


WEQ EC

ITS ESS

OASISPhase 1A

OASIS IICoordinateInterchange

TechnicalBusiness Practices Standards

OASISPhase 1A

OASIS II

NERC Registry

PKI/eMARC

FERC Orders

NERC E-Tag


WEQ EC

ITS ESS

OASISPhase 1A

CoordinateInterchange

OASIS II

TechnicalBusiness Practices Standards

PKI/eMARC FERC OrdersAdopted

Joint InterchangeScheduling WG

NERC Registry

NERC E-Tag


OASIS Phase 1A

Combined effort from both ESS and ITS groups to address uniform OASIS business practices and supporting S&CP modifications. Wendy Weathers (SRP) and J.T. Woods (Southern) are current chairs.

• Multiple Requests and Special Queue Handling • Redirecting Point-to-Point Service Standards• Order 2003 LGIP OASIS Postings

• Resale and Transfer Standards• Release Mechanism

• Network Service on OASIS• Service Point Naming Standards


OASIS II

Where to begin…..

Started with the ESC’s Use Cases. • Recognition that multiple markets exist and will

continue to exist for some time • Don’t make it market specific• But ensure communication between entities• Provide for the acquisition of rights • Provide for that elusive concept “electronic scheduling” • Use the latest and greatest technology• Make it transparent where necessary


OASIS II

ESC Use Case Specification (280 pages)

These Use Cases, along with the OASIS Phase II System Requirements, are envisioned to be used by the Industry as a foundation for specifying the data communications protocols and standards to be adhered to in developing the specific information systems required by OASIS Phase II (OASIS II). Unlike the situation with OASIS Phase I where the term OASIS has been synonymous both with a standardized programmatic interface (i.e., templates) and the computer system implementing that standard interface, this document makes no assumption that OASIS II will be one or multiple computer systems or databases. In the context of this document, the term OASIS is meant only to refer to a single, common, standardized Market Participant interface for the exchange of information with the market.


OASIS II

ESC Use Case Categories• Registration

Participants, Users, Facilities, Resources, Subscriptions

• OperationsOutages, Load Forecasts, (Operating) Schedules

• Transmission Rights MarketsAuctions, Bilateral and Secondary Markets

• Energy MarketsDay-ahead Energy, Real-time Energy

• Bilateral and Self SchedulesPhysical Schedules, Financial Schedules, Self Schedules

• CoordinationCoordinate Interchange


OASIS IIESC Use Case Example

OASIS

Login

Modify ParticipantRegistration

RegistrationUse Case Diagram

Market Operator

Registration

August 27, 2003v 0.2.0

Submit ParticipantRegistration

Set ParticipantRegistration State

Market Participant

Transmission Owner

TSP can do anything that theMarket Operator can do.

Modify ResourceRegistration

Modify UserRegistration

Set FacilityRegistration State

Submit ResourceRegistration

Submit UserRegistration

Set UserRegistration State

Modify FacilityRegistration

Submit FacilityRegistration

Set ResourceRegistration State

View Registration

Post MarketServices

Generation Owner

Transmission Service Provider

Public

Submit Subcription

Modify Subscription Notify Subcribers

Request UserCredentials

«uses»

«uses»

«uses»

«uses»


OASIS II

OASIS II Vision Statement (circa July 2004)

OASIS II will facilitate the timely scheduling of physical energy transfers, and the tracking of both energy and transmission rights usage with regard to those transfers. Given the range of market structures and regional practices among potential users, OASIS II will provide flexibility for the scheduling and tracking of transmission, energy and ancillary service transactions to meet both NERC reliability standards and NAESB business practice standards. All OASIS II systems will support real-time status updates for current schedules/transactions, permit audits and analysis of historical transactions and comply with FERC requirements for information postings as well.


OASIS II

OASIS II Vision document, ver. 1, published July 13, 2004

OASIS II will:• Facilitate Procurement of Energy and Ancillary Services• Facilitate Procurement of both Physical and Financial Transmission

Rights• Facilitate Electronic Scheduling of Physical Transactions• Accommodate Financial Only Contracts• Accommodate Regional Diversity• Support Reliable System Operations• Accommodate Market Operations for Centralized Markets• Accommodate Data Publishing to Industry• Support Market Monitoring• Provide Standards for Electronic Data Communication and User

Interfaces• Function Consistently and Reliably • Implement in a Cost-Effective Manner


OASIS II

OASIS II Scope document, ver. 1, published July 13, 2004

• The interaction between market participants and various power markets, including both existing 888-style Transmission and Ancillary Service markets as well as more centralized transmission and energy markets.

• The submission of Market data to the Interchange Authority (IA) as described within the NERC functional model; in other words, the manner in which the IA receives “transactions.”

• The exchange of Operational data as described within the NERC Reliability Functional Model; in other words, communications involving the Balancing Authority (BA), Reliability Authority (RA), Transmission Service Providers (TSP), Interchange Authority (IA) or other Functional Model entities. The scope of OASIS II would not include the development of any reliability policies or standards directly, but would include supporting the reliability goals established by NERC (or other reliability organizations).


OASIS II

OASIS II Scope document, ver. 1(continued)

• The data exchanged between marketers when writing a transaction; in other words, the process through which marketers build “source to sink” transactions and request their implementation (i.e. “scheduling”). This means defining standards that could be used to exchange information between the parties involved in the transaction.

• The process through which both market and operation entities exchange reliability information, such as outages, system topology, and other significant data.

• The coordination of the implementation of Industry cyber-security standards with regard to securing these systems.

• The provision of a mechanism through which the confidentiality of any data is preserved.

• The exchange of settlements and billing data. This is not considered a high priority, but rather a strategic direction and goal for later development.


OASIS II

Joint OASIS II Implementation Task Force (circa July 2004)

Develop the following documents:

• OASIS II Use Cases, which will describe all in-scope business processes, business objects, and their associated logic;

• OASIS II Requirements, which will support the Use Cases by detailing specific requirements and metrics;

• OASIS II Structural Design, which will describe the technical architecture and how functionality will be staged for deployment; and

• OASIS II Implementation Plan, which will indicate the order and timeline of how the stages will be specified, developed, and deployed.


OASIS II

Joint OASIS II Implementation Task Force

Spring/Summer 2004 – Develop Functional Design Documents• Detailed Scope• ESC Use Cases

Summer/Fall 2004 – Develop Strategic Architecture Plan• Modules• Compatibility plans and requirements

Winter 2004 – Identify Implementation Plan

2005 – Design Stage I Components2006 – Implement Stage I Components, Design Stage II Components2007 – Implement Stage II Components, Design Stage III Components2008 – Implement Stage III Components


OASIS II

Joint OASIS II Implementation Task Force

Stage I• OASIS Phase I Legacy Bridge• E-Tag Legacy Bridge (replace Authority with limited IA

functionality)• IDC Architectural Split (Impact Calculator vs. TLR Process)

Stage II• OASIS Phase II Functions• Legacy Bridge Upgrades• Operations Scheduling Tools (Functional Model)• Enhanced IA to Reliability Interface• IDC Next Generation

Stage III• Electronic Scheduling• Market to IA Interface


OASIS II

For Staged Implementation, recommended the Use Cases• Re-categorize Use Cases by Functionality• Make Groupings as Autonomous as Possible

• Company/User Registration

• Publish/Subscribe

• Bilateral Transmission Markets

• Physical Bilateral Schedules

• Self Schedules

• Market Resource Registration

• Auction Transmission Markets

• Financial Bilateral Schedules

• Energy Markets


MarketScheduling

Node

MarketScheduling

Node

MarketScheduling

Node

TP A (Legacy TP) RTO B RTO C

OASIS 1ANODE(TSP)

E-TagApproval

Market System

Energy, TX, AS(TSP)

LMPCongestion

Management

TLRInterface

NERC ReliefAnalyzer

InterchangeAuthority

GPE PSE LSE

Legacy Bridge

Market System

Energy, TX, AS(TSP)

OtherCongestion

Management

OperationsScheduling

Node


Node


Node

CA A RTO B RTO C

OP2Connector

OP2Connector

OP2Connector

OP2Connector

NERC

NAESB

RTO/FERC

BA RA TO RA TO BA RA TO

Proposed OASIS II Concept Future Of OASIS Conference March 29, 2005


OASIS II

This past January the Joint OASIS II Implementation Task Force formed a Publish/Subscribe Group to continue development of the Publish/Subscribe Use Case. The new groups’ vision statement:

The Publish and Subscribe initiative will provide a flexible infrastructure through which electric utility industry participants can request and receive information on an event-driven or scheduled basis. It will utilize the OASIS II "Foundation Technologies," i.e., HTTP, XML, SOAP, PKI etc... and will be an upgrade that can apply to both future and current uses of the system. Although it is being developed as a part of OASIS II, it is intended to structure this initiative such that it can be implemented as a part of OASIS I or even as an independent standalone system


OASIS II

Where is OASIS II?


OASIS II

Where is OASIS II?

What has been accomplished is posted on the NAESB web site.

Many of the OASIS II Task Force is here, taking notes, and standing at the ready.

OASIS II

Where is OASIS II?

Future Of OASIS Conference March 29, 2005 Future of OASIS Conference Related Industry Initiatives...

Documents

Transcript of Future Of OASIS Conference March 29, 2005 Future of OASIS Conference Related Industry Initiatives...