Invitation to Participate in Revision of Model Operating Procedures
If anyone would like to contribute here, let me know. I think the effort
will be small, but could affect the P&P of all standards committees.
Jim Carlo(firstname.lastname@example.org) Cellular:1-214-693-1776 Voice&Fax:1-214-853-5274
TI Fellow, Networking Standards at Texas Instruments
Vice Chair, IEEE-SA Standards Board
Chair, IEEE802 LAN/MAN Standards Committee
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Tuesday, November 21, 2000 8:47 AM
To: email@example.com; firstname.lastname@example.org; email@example.com;
firstname.lastname@example.org; email@example.com; firstname.lastname@example.org
Cc: email@example.com; firstname.lastname@example.org;
email@example.com; firstname.lastname@example.org; email@example.com
Subject: Invitation to Participate in Revision of Model Operating
The IEEE-SA Standards Board Audit Committee (AudCom) is revising its "Model
Operating Procedures for Sponsor Committees for Standards Development".
This document is a guide for Standards Sponsors in developing their
specific operating procedures as required by IEEE-SA. To create a useful
document that meets the needs of Standards Sponsors, AudCom wishes to
involve Standards Sponsors in the revision of the Model Operating
Procedures. We are asking for your support in forming a small ad-hoc
committee of Society liaisons (or appropriate designees) to assist with
this process. The work would involve reviewing the current document and
submitting changes and comments to the AudCom Administrator. The ad-hoc
committee would then discuss the changes via one or two conference calls.
Please respond to this invitation by 1 December 2000. If you will not be
able to participate personally, we encourage you to appoint a designee.
Please reply to Jodi Haasz, AudCom Administrator, at firstname.lastname@example.org.
Your involvement in finalizing the model operating procedures is greatly
appreciated and will help to ensure that we create a useful document that
reflects the needs of IEEE standards developers.
J.H. (Jim) Gurney