March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Bonneville Team Brian Mathews, TK Tan, Bruce Kraemer, Harry Worstell, Stuart Kerry, Clint Chaplin, Lee Armstrong, Richard Paine, Al Petrick, Terry Cole

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Background Team objectives: - To list and prioritize the major problem areas which hinder progress. - To propose solutions to the Chair which will result in a streamlined process. Desired result: - Ultimately, to continue to get high quality standards out more quickly than we have in the past.

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Status ● Meetings began in Vancouver in January. Follow-on conference calls were held. Special CAC meeting 3/14/04. ● Team members interviewed knowledgeable sources and assembled a list of issues which cause delays. ● Team members then assigned a priority ranking to each issue ● Votes were totalled and the list was rearranged in priority order and then reviewed/refined ● Issues were then categorized into the following groupings: ArchitectureEducation PARStandardization Submissions ● Sub-teams will develop proposals

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Sub-teams & leaders ● ARCHITECTURE: Terry Cole ● EDUCATION: Harry Worstell ● PAR: TK Tan ● UNIFORM PROCESS:John ● SUBMISSIONS: Richard

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Plans ● Input/comments welcome, send to sub-team leader ● Sub-teams to study issues and develop proposals ● A two-hour time block will be devoted to this at the May meeting ● Goal is to have complete proposals/motions to be presented to the body at the July meeting

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Architecture ● Two main thought categories for speed-up: ● Short Term ● Provide architectural focus so PARs and TG activities can be made as focused and contained as possible ● Increase communication and coordination at architectural (interface) level between TGs ● Mid to Longer Term ● Decide where we are going so we proactively chart a course there ● Some discussion of addressing this by creating an 'Architectural' group within ● Some discussions of how to maintain our document for better/faster additions ● Architecture sub-team to consider these issues and make a proposal to the Chair and CAC

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Education Emphasis is on providing training to TG/SG/SC chairs Topics to include in Chairs training: ● Back-end logistics cited multiple times – a major topic ● Comment handling: not losing track of any comments, and proper use of the Standard Tool (database or spreadsheet) ● Available mechanisms for between-meeting work ● The unwritten “90% rule” and how to attain it ● Past cases of 'abuse of procedure' and how to avoid it ● How to avoid delays due to a single (or a few) new NO vote(s) right at the end ● Managing presenters and presentations (30 min. time limit?)

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Education ● Overall process scheduling and logistics ● Managing the work tasks (how to sub-divide into smaller groups for breakout working sessions, etc.) ● How to be a facilitator, giving everyone opportunity for input ● General group leadership skills ● Roberts Rules usage vs. TG Chair discretion ● How to handle attendee churn, new attendees raising already-resolved items, key attendees dropping out, etc.

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Education ● TG vs. SG vs. SC operational differences ● Starting text too soon causes removal of legacy stuff taking a huge amount of time. Text should not be adopted in advance of agreements over the big things. This just makes it impossible for the editor to create clean work.

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission PAR Issues ● Lack of well-defined, narrowly scoped PARs ● Scope not narrow enough ● Tried to do too much … much more limited scope PAR would have proven faster for both ● Tried to do maintenance as well as functional enhancements. Leads to too much editorializing along with amendment for financial reasons ● Argument about PAR and procedures ● Lack of early technological review (at PAR stages)

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission PAR One problem is that SGs tend to have the solution in mind as they prepare PAR paperwork Addressing lack of early technological review (at PAR stage) Develop a checklist to review: ● Define the problem scope first, do not provide solution first ● Assess impact on other areas of the standard ● Assess problem is not addressed by other organizations ● Identify interactions with external groups ● Identify interaction requirements with other 802 groups ● Can the problem space definition be above Layer 2? ● Segment problem to PHY MAC, or above, or across ● Assess market need and timeframe, quick fix or long term ● Assess Support of problem

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Uniform Process issues ● Need standards for: ● Comment processing procedure, format, and software tool ● Formats and procedures for requirements, architectures, and task group ballots (e.g. some groups getting through Procedure10 and others not able to), also standard forms for motions and area on server where people can get to them ● Rules, processes and procedures across TGs/SGs so people going from one to another can immediately be productive. ● Good quality information in TG/SG summary reports. ● Learning curve for new people will be addressed by a standardized approach. ● Down-select process, non-compromise resolution, late phase new NO votes handling ● TG/SG/SC Chairs training

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Submissions ● Make the submission formats easier Problems with present submission (complexity, obfuscation, not consistent): ● Word – convoluted standard header/footer format, must go to properties Powerpoint – view/master pdf – no header standard Excel – no header standard Access – no header standard

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Submissions Encourage submissions that can be worked on in teleconferences Encourage submissions that can be worked on in Change culture of only working on documents and submissions at physical meetings Letter ballot comment processing in teleconferences More use of Netmeeting or Webex

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Submissions ● Cultural change ideas: ● On server two weeks before the meeting ● Four hour rule is not workable if you are in meetings for the four hours

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Issues list

March 2004 Brian Mathews – AbsoluteValue Systems IEEE doc: IEEE / Submission Issues list – cont'd