Participant Technical Reference Manual - IESO
Participant Technical Reference Manual - IESO
Participant Technical Reference Manual - IESO
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Participant</strong> <strong>Technical</strong> <strong>Reference</strong> <strong>Manual</strong><br />
3. Dispatch Information<br />
202 Interfaces (see figure below) shows the relationship that Message Exchange<br />
(ME) has with other parts of the system. Most of the functions are internal to<br />
<strong>IESO</strong> however on the right of the diagram is the interface with the market<br />
participants.<br />
Resource<br />
Dispatch<br />
Operator ME<br />
Overview<br />
P<br />
A<br />
Interchange<br />
Scheduler<br />
Message<br />
Exchange<br />
ICCP<br />
Interface<br />
R<br />
T<br />
I<br />
C<br />
Application X<br />
Compliance<br />
Monitor<br />
WEB interface<br />
I<br />
P<br />
A<br />
N<br />
T<br />
Figure 3-1: Message Exchange Interfaces<br />
203 Specifics of ICCP Block 4 are discussed in the ICCP guidelines, which can be<br />
ordered from EPRI – Report TR-107176 over the Internet.<br />
204 A WEB-Based Message Exchange user guide has been posted on the <strong>IESO</strong><br />
Web site. The user guide provides information on message displays, user<br />
actions and contract management message displays, etc. Market participants<br />
are encouraged to consult the Web site for further details and latest updates to<br />
the user guide.<br />
3.2.2 Functional Parts<br />
205 Message Exchange (ME) consists of several independent functional parts:<br />
a. An ICCP Server responsible for establishing and maintaining the communication between<br />
utilities using the ICCP protocol and maintains the communication parameters and status<br />
for each link.<br />
b. A Web Server (Servlet or Application Server) responsible for establishing and maintaining<br />
communication between market participants using the https protocol and managing user<br />
logins, client requests, publishing client response to SCADA (Supervisory Control and Data<br />
Acquisition), subscribing to & performing action requests from SCADA and publishing<br />
results of action requests to SCADA.<br />
Issue 21.1 – March 15, 2010 - estimated Public 59