David's tiered approach
makes a lot of sense to me.
The TWIST (Transaction
Workflow Innovation Standards) work David mentions seems very relevant.
(see http://www.twiststandards.org/index.php?option=com_content&view=article&id=1&Itemid=57
0
The primary aim of TWIST
is XML standards that connect the financial and physical supply chain. Our physical supply chain is energy.
From the above link I
have extracted below their list of collaboration efforts which include FIX and
ebXML, which have been mentioned as collaboration targets for eMIX.
TWIST has a declared strategy of
collaborating with other standards organisations on a peer-to-peer basis. This
is from the unambiguous perspective that standard organisations by definition
are not aimed to be competitive when they serve the marketplace.
In the Payments area, TWIST has been
pro-actively involved in the harmonization of the ISO XML-payment standards
together with IFX, SWIFT and OAGi. Further active collaboration is being
pursued with these organisations.
In the area of Wholesale Financial
Markets, TWIST has established active relationships with MDDL, FpML and FIX.
In various parts of this website a
number of references are made to partner organisations and their websites.
Listed below are the links to the partner organizations and a brief description
of each.
The Financial Information eXchange
(FIX) protocol is a messaging standard developed specifically for the real-time
electronic exchange of securities transactions. In addition to defining
messages for communicating transactions, FIX also defines the session-level
interaction between two FIX applications.
FpML
www.fpml.org
Financial products Markup Language
(FpML) FpML is a protocol for complex financial products.
MDDL
www.mddl.org
Market Data Definition Language
(MDDL) is an XML-based interchange format and common data dictionary on the
fields needed to describe 1) financial instruments, 2) corporate events
affecting value and tradability and 3) market-related, economic and industrial
indicators.
The Open Applications Group is a
not-for-profit, open, and fully independent Open Standards Organization focused
on promoting interoperability among business applications and creating business
language standards to support this goal. TWIST and OAGi are working together
closely on the commercial payments core payment kernel.
SWIFT
www.swift.com
SWIFT is the industry-owned
cooperative supplying secure, standardised messaging services and interface
software to 7,600 financial institutions in 200 countries. The SWIFT community
includes banks, broker/dealers and investment managers, as well as their market
infrastructures in payments, securities, treasury and trade. TWIST and SWIFT
scopes are complementary - the graphical illustration of this as follows:
Control, Reliability and Security
FIXSP
www.fixprotocol.org
The FIX Session Protocol (FIXSP) is
specified in Version 4.4 (18 June 2003) of the FIX standard. The standard
includes both the FIXML application and the FIX Session Protocol. In
Application of FIX it is explained how the FIX Session protocol can be used for
the secure transport of TWIST messages.
ebXML
www.oasis-open.org/committees/ebxml-msg
The ebXML Message Service standard
is specified in "Message Service Specification Version 2.0, OASIS ebXML
Messaging Services Technical Committee, August 2002." or later editions.
The standard is intended to be implemented upon protocols such as HTTP and
SMTP. It can be used to carry non-ebXML XML applications (or non-XML for that
matter). It can also be separated from the rest of the ebXML architecture. In
Application of ebXML message service it is explained how ebXML can be applied
for the security of TWIST messages.
Edward G. Cazalet, Ph.D.
101 First Street, Suite 552
Los Altos, CA 94022
650-949-5274
cell: 408-621-2772
From: David RR Webber (XML) [mailto:david@drrw.info]
Sent: Tuesday, May 11, 2010 7:21 AM
To: Toby.Considine@gmail.com
Cc: emix@lists.oasis-open.org
Subject: RE: [emix] Block power purchases
Toby,
This is exactly the case
I've been making for separating the solution space into tiers. We cannot
boil the ocean here - and need to clearly delimit where the EMIX world begins
and ends - and how it plays into the bigger worlds around it.
By making three tiers -
you allow people to set their own granularity and marketplace focus.
How I'm envisioning this
all working is a tiered approach:
- eMarketplace -
bid/accept model and workflow
- contracts and
commitments to provide
- EMIX device level
delivery
I've included my
previous posting on eMarketplace world view and EMIX below.
Essentially we point to
existing work in tiers 1 and 2 - and show how to couple that into tier 3 - the
EMIX delivery world.
That allows us to
exploit existing marketplaces seamlessly without having to re-invent those
wheels! And also allows us to support future marketplaces that may emerge
with new financial tools and models in the future.
It also means we can
stop worrying about world views and just go build the basic EMIX
infrastructure...
Thanks, DW
===========================
Include from previous post =============================
OK - I remembered this
now:
Also - their submission
to ISO looks interesting.
So some derived
financial workflow pattern based on their ground work for EMIX seems sensible -
possibly just an adopters guidelines or how to. Notice they have
travelled over a lot of the same ground including safeguarding message
exchanges.
How I'm envisioning this
all working is a tiered approach:
- eMarketplace -
bid/accept model and workflow
- contracts and
commitments to provide
- EMIX device level
delivery
Leveraging existing work
in the top two tiers obviously dramatically simplifies what we actually have to
deliver on the ground level. Another possibility for large suppliers is
obviously to integrate eMarketplace model with existing marketplaces such as in
EU and USA.
Thanks, DW
-------- Original Message --------
Subject: [emix] Block power purchases
From: "Toby Considine" <Toby.Considine@gmail.com>
Date: Tue, May 11, 2010 8:44 am
To: <emix@lists.oasis-open.org>Block power purchases
We speak often as if all power infinitely granular. Many purchases have and will always have limits and rates.
If you do not buy at least 20 MWH for 5 straight hours, it’s not worth turning my small generator on.
My DR is limited to turning off the lights or turning off the building. I can offer you half a building. I cannot give you DR fore two buildings, even at twice the price I would offer one.
My offer of one MWH for 8 hours between 2PM and 10PM, is not an offer of 32 MWH between 2:45 3:00
Maxima, minima, and rates are not adequately dealt with in the last draft.
I welcome suggestions
tc
"Energy and persistence conquer all things." -- Benjamin Franklin
Toby Considine
TC9, IncOASIS Technical Advisory Board
TC Chair: oBIX & WS-CalendarTC Editor: EMIX, EnergyInterop
Email: Toby.Considine@gmail.com
Phone: (919)619-2104
blog: www.NewDaedalus.com
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php