OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Recommendations and Actions: April 28, 2011 meeting.


I've submitted the document (text below) to the EI TC website for consideration: http://www.oasis-open.org/committees/download.php/42017/EI-Actions-Recommendations_20110428.docx


To: Energy Interoperation Technical Committee

From: Rish Ghatikar, Lawrence Berkeley National Laboratory

Date: May 03, 2011

 

As a result of Thursday, April 28, 2011 special EI TC call, I was asked to recommend specific action items for few issues identified during the regular EI TC call on Wednesday, April 27, 2011.  My brief recommendations are intended to expedite the EI v1.0 standards that are of World-class quality. Some of my recommendations may be interdependent. The TC voting can be carried out as appropriate.

1.     Scope and structural direction: As one of the people responsible for writing the EI Charter, I would like to see that the primary focus is on the scope within the charter. The TC members must determine the structure of EI TC activity and its direction. The EI structure/profile document that was submitted to the TC and discussed during the TC meeting (agreed as a course for EI) must be referenced: (see: http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/38965/Proposed-EI-DocumentStructure-20100809.doc)

2.     Procedural requirements (or processes): In my experience in software and energy field, I have seen that the success of the projects are not just because of good technical strengths, it is also due to clear procedural rules design and implementation governance. I suggest that all the TC members play a role to identify and make procedural decisions. These procedures must be kept simple (technical simplicity goes without a mention).

3.     The EI TC has the ability to extend and identify requirements: The EI requirements are unique from any other activity and the TC must be able to define its needs and able to extend from any contributions independently. This works best when stable versions of both normative and non-normative references are available. This is also important for sustainability, expediency, IPR, and maintenance.

The activities #1 and #2 above must be determined at the earliest convenience before proceeding further on any further issues. The activity #3 will be ongoing.

 

Thank you!
--
Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-3111, Berkeley, CA 94720
GGhatikar@lbl.gov | +1 510.486.6768 | +1 510.486.4089 [fax]

This email is intended for the addressee only and may contain confidential information and should not be copied without permission. If you are not the intended recipient, please contact the sender as soon as possible and delete the email from computer[s].


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]