Looking at their 4.0 package, the Introduction, General Guidelines and Message Process Flow have Use Case and Sequence information, Purchase through settlement process flow, Unit values, Code LIsts, and data rules that might be helpful to us. Would these requirements not have aleardy been vetted and incorporated into the NAESB requirements?
Regards,
-Anne
--- On Thu, 1/28/10, Considine, Toby (Campus Services IT) <Toby.Considine@unc.edu> wrote:
From: Considine, Toby (Campus Services IT) <Toby.Considine@unc.edu>
Subject: [emix] Standards for Natural Gas Metering
To: "emix@lists.oasis-open.org" <emix@lists.oasis-open.org>
Date: Thursday, January 28, 2010, 3:25 AM
Some other standards we should compare and contrast to what we do in EMIX http://www.edigas.org/edigas/ tc From: Pim van der Eijk [mailto:pim.vandereijk@oasis-open.org]
Sent: Thursday, January 28, 2010 3:19 AM
To: 'William Cox'; 'Carol Geyer'
Cc: 'Laurent Liscia'; Considine, Toby (Campus Services IT); 'Robin Cover'
Subject: RE: Smart metering for water utilities Hello, I worked in this industry years ago. Gas is a much more complex product than electricity, in that the energy that can be obtained from a given quantity of gas varies. For domestic users, gas utilities mix inputs with different caloric values into a consistent result (for safe and economic operation of your gas-operated heating and cooking equipment etc.). Industrial users can tune their systems and can buy nonstandard caloric value gas at better prices. So the commercial B2B transactions and messages are also more complex. The established standard (at least in my part of the world) is EDIGAS, B2B messaging using the AS2 message protocol. Gas contracts are typically set at fixed rates for long periods.
Pim
|