EIDE Architecture Overview

WECC DEWG

Soap Methods

EIDE provides a “Put” method for data– Sender transfers schedule data, meter data, text

message, power system data, etc. to receiverEIDE provides a “Get” method for data

– Sender requests data from the receiverThe protocol can be used for both

synchronous and asynchronous transfers

Transfer Methods

EIDE documents can be transported like any text file

http, https, e-mail, ftp, read/write, standard copy, etc.

http/https provide the highest functionality and will be discussed today

Transport can be mixed, http then ftp for example

Communications Pattern

HTTP/S transport employs send/reply pattern

EIDE Schema reflects this patternThe send/reply use the same session and

are synchronousSender send method awaits a reply or time

out

Anatomy of a “Put”

EMS Data

SchedulingData

Retrieve Dataand create XML

DocumentSend DocumentStore Document

Firewall FirewallInternet

EIDEDocuments

Receive andValidate

Document, Reply,Process

IIS or other Web Server

Firewall

EMS Data

SchedulingData

EIDEDocuments

Put

Event triggers xferProcess retrieves data from database, file,

method, otherAppropriate objects created and populatedObjects are translated to valid documentSoap wrapper is applied to documentDocument is sent to receiver

Put

EMS Data

SchedulingData

Retrieve Dataand create XML

DocumentSend DocumentStore Document

Firewall FirewallInternet

EIDEDocuments

Receive andValidate

Document, Reply,Process

IIS or other Web Server

Firewall

EMS Data

SchedulingData

EIDEDocuments

Put

Receiver evaluates document and sends reply in same http session

Receiver examines soap method and dispatches to appropriate receiver and method

EIDE document is validated against schema and converted to appropriate objects

Put

EMS Data

SchedulingData

Retrieve Dataand create XML

DocumentSend DocumentStore Document

Firewall FirewallInternet

EIDEDocuments

Receive andValidate

Document, Reply,Process

IIS or other Web Server

Firewall

EMS Data

SchedulingData

EIDEDocuments

Put

Receiver maps data to local structures for their EMS or scheduling system and stores data

Can also write to csv file for import or transfer

Can invoke storage methodsOptionally, entire EIDE document can be

stored in a database

Put with RequireAck set to TRUE

Sender may have requested an “ack”Receiver replies with appropriate codeCodes are enumerated in schema so

receiver can code what to send and sender knows how to handle response

Ack can be either sync or async

Put with Ack

IIS or other Web Server

EMS Data

SchedulingData

Retrieve Dataand create XML

DocumentSend DocumentStore Document

wait for ackreply

Firewall FirewallInternet

EIDEDocuments

Receive andValidate

Document, Reply,Process, send

ack

IIS or other Web Server

Firewall

EMS Data

SchedulingData

EIDEDocuments

Put Methods

EIDE schema put methodsQuestions on Put?

Anatomy of a “Get”

IIS or other Web Server

EMS Data

SchedulingData

Create Getdocument

wrap in soapmethod

send to receiverprocess reply,

wait for get returnFirewall Firewall

Internet

EIDEDocuments

Receive andValidate

Document, Reply,Process, Send

Data

IIS or other Web Server

Firewall

EMS Data

SchedulingData

EIDEDocuments

Get

Event triggers GetProcess creates Get objects and populates

themXML Object is constructedObject is translated to valid documentSoap wrapper is applied to documentDocument is sent to receiver

Anatomy of a “Get”

IIS or other Web Server

EMS Data

SchedulingData

Create Getdocument

wrap in soapmethod

send to receiverprocess reply,

wait for get returnFirewall Firewall

Internet

EIDEDocuments

Receive andValidate

Document, Reply,Process, Send

Data

IIS or other Web Server

Firewall

EMS Data

SchedulingData

EIDEDocuments

Get

Receiver evaluates document and sends reply in same http session

Receiver could examines soap method and dispatch to appropriate method, then generate either a synchronous immediate response, or a simple reply

Requestor can specify async reply If asynchronous reply is being sent, then receiver

becomes the sender and sends requested data.

Get

Similar to a “Put”, a replier could set the require ack flag, however this has no meaning within the schema and should be ignored by receiver

Let’s look at the schemaQuestions on “Get” methods?

Break!

Woo hoo!Oh, oh right, any one want to keep us here

with a question?