Audit Committee Report

1
Audit Committee Report For IEEE-SASB 25
September 2007
Glenn Parsons Chair
2
AudCom Recommendations

• Unanimous approval for the acceptance of each of
  the following PP documents
• Industry Applications Society
• Design Automation Standards Committee
• Computer Society LAN/MAN Standards Committee
  (until Dec 2008)
• These were approved by the SASB under the consent
  agenda

3
AudCom Sponsor Status

• Visibly under development(standards work
  authorized)
• Power Engineering Society Technical Council
  Operating Procedures
• Computer Society Portable Applications
  Standards Committee
• Under Review(standards work not authorized)
• Broadcast Technology
• SCC41 DySPAN

4
AudCom process

• The Committee approved a motion clarifying the 3
  external states of PP as
• Accepted
• Not accepted
• Visibly under development
• The Audit Committee then approved text for
  inclusion in the Operations Manual to describe
  these three terms, as well as two internal AudCom
  states and various cleanups.
• Forward to ProCom for review, and then approval
  by the Standards Board.

5
AudCom Flowchart

• The AudCom flowchart was revised at the AudCom
  meeting (based on the proposed OpsMan text) and
  unanimously approved by the committee.

6
AudCom Baseline PP revision

• An ad hoc committee was formed to modify the
  baseline PP document to include the SCC Type 2
  model PP.
• The goal is to develop a single common sponsor
  and SCC PP document.
• The ad hoc will be chaired by Ron Petersen, with
  Howard Wolfman, Gary Robinson and Matt Ceglia.

7
Model PP for Working Groups?

• Sponsor PP reviewed by AudCom often include WG
  PP
• Recommendation is to separate them out
• AudCom does not review these or provide a
  baseline
• But these are arguably the most important
• AudCom recommends developing a baseline WG PP
  document.
• Will require Bylaws/OpsMan changes.

8
Hierarchy of documents

• AudCom was unclear if we need to go deeper than
  the sponsor PP to mandate that a subordinate
  document cannot override it
• We have agreed on a baseline PP update to make
  this explicit
• But generally, can a group write a PP that
  impacts/conflicts the PP of a group above it?
• AudCom will forward issue to ProCom