Energy Price+ProductEvaluation of Characteristics

William Cox

OASIS EMIX TC Meeting

2009-12-17

OASIS EMIX TC 2009-12-17 2

Some Sources

• Cox Presentation 2009-11-05

• Sun-Ipakchi Presentation 2009-10-26

• Meeting Minutes

OASIS EMIX TC 2009-12-17 3

Characteristics Discussed

• Price• Currency• Units of measure• Quantity (the number of units)• Counter Party (the one you’re trading with)• Kind of Energy (Natural Gas, Electricity?)• Schedule (time interval, past , present or future)• Location (viz. Carl Reed/OGC discussion)

– Delivery or settlement location

OASIS EMIX TC 2009-12-17 4

Characteristics Discussion (2)

• Source Description (how the energy was generated)– Hard coal, soft coal, soft coal with scrubber, natural

gas, wind, solar, hydro, etc

• Carbon characteristics• Specialized [Electrical+] Characteristics

– Reserve– Frequency Regulation– Voltage Support– Capacity

OASIS EMIX TC 2009-12-17 5

Characteristics Discussed (3)

• Green Content percentage

• Usage or Load– PAP 10 Requirements in process

OASIS EMIX TC 2009-12-17 6

Extensible (From 2009-11-05)

• We don’t know what characteristics will be important.

• May use a name-value pair approach for these and others– Note that XML is inherently

name/attribute/value

• Need to manage the names and value sets for base, energy, and extensions

OASIS EMIX TC 2009-12-17 7

A Proposal

• Structure with key information in the information model

• Carry additional information as message/larger artifact components

• More specifically…

OASIS EMIX TC 2009-12-17 8

A Proposal (2)

• In the EMIX Information Model– Price– Currency– Units of measure– Quantity– Schedule– Location– Source– Kind of Energy (electric+regulation, gas, ..)

OASIS EMIX TC 2009-12-17 9

A Proposal (3)

• Extended characteristics– Carbon

• Which kind(s)?

– Source percentages– Green content

• Definition? Relationship to Source? Political Definition?

– Usage or Load or Peak• May be core information model—discuss

OASIS EMIX TC 2009-12-17 10

A Proposal (4)

• Not in the model—carried with EMIX artifacts but not inside– Counterparty

• E.g. market transaction message would contain– EMIX artifact– Counterparty– Transaction Ids and tracking information– Other pFIX information

– Clearing location• Additional items for discussion

– Wholesale/retail flag– Contract identifier– Program

OASIS EMIX TC 2009-12-17 11

Next Steps

• Write up information model

• Work on definitions of the pieces

• Move into working draft

• Comments, change requests to text in working draft

OASIS EMIX TC 2009-12-17 12

References and Inputs

• NAESB Requirements and Use Cases– Including vocabulary

• EERP Business Quality of Service does some of these things– Extensible list– Common base includes price, units, currency

• ebXML, UBL deal with products, invoices, and transactions

• FIX (financial protocols) markets, including forward