Download
1 / 35

IT Breakout Session April 23, 2001 - PowerPoint PPT Presentation


  • 90 Views
  • Uploaded on

IT Breakout Session April 23, 2001. Kevin Perry Manager, IT. Portal Client System Requirements. User Interface : Personal computer Microsoft Internet Explorer 5.x Access to the Internet Client Digital Certificate issued by SPP. Server / Messaging System Requirements. Web Listener :

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' IT Breakout Session April 23, 2001' - felcia


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
It breakout session april 23 2001

IT Breakout SessionApril 23, 2001

Kevin Perry

Manager, IT


Portal client system requirements
Portal ClientSystem Requirements

  • User Interface:

  • Personal computer

  • Microsoft Internet Explorer 5.x

  • Access to the Internet

  • Client Digital Certificate issued by SPP


Server messaging system requirements
Server / MessagingSystem Requirements

  • Web Listener:

  • Server (or high-end personal computer)

  • Microsoft Windows 2000 Server

  • Internet Information Server (IIS)

  • Access to the Internet or SPPnet

  • Server Digital Certificate issued by SPP


Control area system requirements
Control AreaSystem Requirements

  • ICCP Server:

  • Redundant ICCP servers running OSI

  • and configured for automatic fail over

  • Configured for TASE.2 - Block 1 and 2 data transfers

  • Capable of 4-second periodic data exchange with SPP and local EMS

  • Access to SPPnet


Data requirements
Data Requirements

  • Registration:

  • Users must be registered with SPP and be issued a Digital Certificate

  • Required connectivity must be demonstrated (e.g. Web Portal, Web Listener, ICCP)

  • Assets must be registered with SPP via web portal


Data requirements1
Data Requirements

  • Ancillary Service Bids:

  • Submitted by Market Participants in the form of a supply curve

  • Can manually enter data via web pages

  • Can bulk upload via XML file transfer

  • All access via Web Portal


Data requirements2
Data Requirements

  • Resource Plans:

  • Submitted by Generation Providers

  • Can manually enter data via web pages

  • Can bulk upload via XML file transfer

  • All access via Web Portal


Data requirements3
Data Requirements

  • Reservations, Tags, and Schedules:

  • Customers must reserve transmission capacity using OASIS

  • Customers must submit NERC Tags for all schedules

  • RTO Scheduling system is required


Data requirements4
Data Requirements

  • Load Forecasts:

  • Submitted by Control Areas under SPP Criteria 5

  • Load forecast submitted daily via SPP web site or FTP upload


Data requirements5
Data Requirements

  • Scheduled Outages:

  • Transmission outage schedules submitted daily by Control Areas via SPP web site or FTP upload

  • Generation outage schedules submitted daily by Generation Providers via SPP web site or

  • FTP upload


Data requirements6
Data Requirements

  • Real-Time Data:

  • Control Areas will submit line flows (MW, Mvar, kV) for lines, loads, and transformers at 4 second periodicity

  • Control Areas will submit breaker status values by exception

  • All data submitted via ICCP


Data requirements7
Data Requirements

  • Real-Time Data (cont):

  • Generation unit operators will submit operating data (MW, Mvar, kV, Limits) at 4 second periodicity

  • Generation unit operators will submit unit status values by exception

  • All data submitted via ICCP


Data requirements8
Data Requirements

  • Real-Time Data (cont):

  • SPP will provide Net Scheduled Interchange for each Control Area via ICCP

  • Control Areas must be able to read the NSI every 4 seconds

  • NSI must be passed to Control Area EMS for ACE calculation at

  • 4-second periodicity


Data requirements9
Data Requirements

  • Actual Net Interchange:

  • Control Areas will continue to perform routine, daily tie-line checkout

  • Hourly actual net interchange (not individual tie MWH) by Settlement Areas will be sent to SPP via web portal (XML upload)

  • Data is revenue quality


Data requirements10
Data Requirements

  • Actual Generation:

  • Generation Providers will submit hourly actual generation MWH to SPP for each asset

  • Data will be submitted via web portal (XML upload)

  • Data is revenue quality


Data requirements11
Data Requirements

  • Meter Data:

  • Meter Agents/Distribution Companies will aggregate and submit usage data by Settlement Area and Load Entity

  • Data submitted as hourly MWH

  • (3 decimal positions)

  • Consumption/profile and interval meter data submitted to SPP via web portal (XML upload)


Data requirements12
Data Requirements

  • Notices and Emergency Messages:

  • SPP will issue emergency operational messages to Market Participants

  • Messages can be viewed on-line or downloaded via the XML interface (XML only applies to Market Operations System messages)


Programmatic data exchange
ProgrammaticData Exchange

  • Web listener required for XML data exchange

  • Two types of messages:

    • Query/Response

    • Push/Acknowledgement

  • HTTPS and digital certificates required for data access and security


Xml messages
XML Messages

  • Any MOS data that can be entered or viewed via the web pages are also available via XML data exchange

  • XML messages are grouped and Multi-purpose Internet Mail Extensions (MIME) encapsulated

  • Message syntax is defined by Document Type Definition (DTD) schema files




DTD Specification (1 of 2)

<?xml version="1.0" encoding="UTF-8"?>

<!-- edited with XML Spy v3.5 NT (http://www.xmlspy.com) by Phillip E. Hystad (private) -->

<!--DTD generated by XML Spy v3.0.7 NT (http://www.xmlspy.com)-->

<!ELEMENT Bids (ASBid | EISBid)*>

<!ELEMENT ASBid (DAY, HOUR, BLOCKID, CAPACITY, RSRC_ID, RSRC_TY, URS_PRICE?, DRS_PRICE?, SPIN_PRICE?, SUPP_PRICE?)>

<!ELEMENT EISBid (DAY, HOUR, RSRC_ID, RSRC_TY, MW, PRICE)>

<!ELEMENT DAY (#PCDATA)>

<!ELEMENT HOUR (#PCDATA)>

<!ELEMENT BLOCKID (#PCDATA)>

<!ELEMENT CAPACITY (#PCDATA)>


DTD Specification (2 of 2)

<!ELEMENT RSRC_ID (#PCDATA)>

<!ELEMENT RSRC_TY (#PCDATA)>

<!ELEMENT URS_PRICE (#PCDATA)>

<!ELEMENT DRS_PRICE (#PCDATA)>

<!ELEMENT SPIN_PRICE (#PCDATA)>

<!ELEMENT SUPP_PRICE (#PCDATA)>

<!ELEMENT MW (#PCDATA)>

<!ELEMENT PRICE (#PCDATA)>


XML Message (1 of 3)

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE Bids SYSTEM "bids.dtd">

<Bids>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>0</MW>

<PRICE>0.00</PRICE>

</EISBid>

<EISBid>

<DAY>20010403</DAY>


XML Message (2 of 3)

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>100</MW>

<PRICE>30.00</PRICE>

</EISBid>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>200</MW>

<PRICE>40.00</PRICE>


XML Message (3 of 3)

</EISBid>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>300</MW>

<PRICE>40.00</PRICE>

</EISBid>

</Bids>


Message partition mime
Message Partition/MIME

  • All messages are constructed of one or more partitions where each partition is specified as an XML document

  • The partitions are separated using a boundary line

  • MIME is used to describe the boundaries and the message parts


Full message 1 of 5
Full Message (1 of 5)

  • MIME-Version: 1.0

  • Content-Type: multipart/Related;

  • Type="Application/X-SPP-Markets"; boundary="SPP-XML-DATA"

  • --SPP-XML-DATA

  • Content-Type: application/xml

  • <?xml version="1.0" encoding="ISO-8859-1"?>

  • <!DOCTYPE Header SYSTEM "header.dtd">

  • <Header>

  • <TransactionInfo>

  • <Action>Submit</Action>

  • <Subject>Bids</Subject>

  • <Version>1.0</Version>

  • <Environment>Production</Environment>

  • </TransactionInfo>

  • </Header>


Full Message (2 of 5)

--SPP-XML-DATA

Content-Type: application/xml

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE Bids SYSTEM "bids.dtd">

<Bids>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>0</MW>

<PRICE>0.00</PRICE>


Full Message (3 of 5)

</EISBid>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>100</MW>

<PRICE>30.00</PRICE>

</EISBid>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>


Full Message (4 of 5)

<RSRC_TY>GEN</RSRC_TY>

<MW>200</MW>

<PRICE>40.00</PRICE>

</EISBid>

<EISBid>

<DAY>20010403</DAY>

<HOUR>0100</HOUR>

<RSRC_ID>DPG1</RSRC_ID>

<RSRC_TY>GEN</RSRC_TY>

<MW>300</MW>

<PRICE>40.00</PRICE>

</EISBid>


Full Message (5 of 5)

</Bids>

--SPP-XML-DATA--


Next?

  • IT technical training on XML

  • Tuesday, May 22

    • Houston – Doubletree Hotel

      400 Dallas Street

  • Wednesday, May 23

    • Dallas – Hyatt Regency/DFW

      D/FW International Airport

  • 8:30 AM – 4:00 PM



ad