1 / 9

FERC TC: Information Technology for Reliability & Markets

This project aims to specify interfaces for Security Constrained Unit Commitment (SCUC) and create a standard input and output interface for ISO-RTOs to procure and run SCUC from any vendor. The project includes the development of tools for automating the creation of message schemas, using a model-driven architecture approach. The goal is to reduce integration costs and facilitate the integration of SCUC into Market Operations Systems.

tracyhall
Download Presentation

FERC TC: Information Technology for Reliability & Markets

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FERC TC: Information Technology for Reliability & Markets ISO-RTO Standards Collaborative July 14, 2004 J. Waight

  2. Security Constrained Unit Commitment • Objectives: • Specify Interfaces to Security Constrained Unit Commitment (SCUC) • Continuation of EPRI CME project • 1st Project to demonstrate methods of ISO-RTO Standards Collaborative • Desired Result is that SCUC may be considered as a black box with standard input and output interfaces • Desired Result is that ISO-RTOs can procure SCUC as a component, from any vendor, and run multiple SCUC in parallel • ISO-RTOs can integrate SCUC into a Market Operations System using a standard interface, at reduced cost

  3. Process for Creation of Standard Interfaces • Each Vendor contributed its SCUC requirements • Data Input Requirements and Descriptions • Data Output Provided by SCUC and Description • ISO-RTOs review Input/Output requirements • Create a profile of data required to support features of Market • Commonality due to SMD • Review of existing Common Information Model • IEC standard 61970 part 301 • Search for existing models that can be reused • Extension of CIM to add Market Features • Workshop approach • Development of a set of tools to automate creation of message schemas • Use of tools to create message schemas

  4. Tools for Creation of Standard Interfaces • Model Driven Architecture • Platform Independent Model maintained in UML • Rational Rose • Intermediate Model • RDF/Schema • Platform Specific Model • W3C XML Schema • XPETAL as tool for transformation • Public Domain

  5. Input Messages Market Input Message (Bids) Generation Bid Load Bid Transaction Bid Network Model Input NERC CPSM profile Standing Input Message RTO Product Definition Market Definition Market Participant Registration System Requirement Load Forecast Generation Initial Conditions Security Analysis Input Message Outages Contingencies Limits etc Output Message Schedules Prices Errors & Warnings Solution Notes Control Messages Schemas Fetch Execute Message Framework for SCUC

  6. Results to date • First Project to Demonstrate ISO-RTO Standards Collaborative • Three workshops attended by • ISO-RTOs, Vendors, and Consultants • Repeatable Process, Methodology, and Tools for Developing Interface Standards • Model Extensions to the Common Information Model (CIM) to support SCUC • Development of Message Sequence Diagram • Development of XML schemas to define messages • Planning for pilot project to validate schemas • Achieved in three month schedule

  7. Questions ???

  8. Backup: Message Sequence Diagram

  9. Backup: Model Driven Architecture Cascaded Pattern

More Related