CODE DISCUSSION GROUP
------------------------------------------------------------------
Have a code question you want investigated by the Code
Discussion Group? Submit your idea here.
July 18, 2009
An IAPMO interpretation was discussed. This interpretation
requires that all restaurants, regardless of size, should meet
Table 4-1 for fixture units. This may be unnecessarily restrictive
because it may require separate bathrooms for both men’s and
women’s restrooms being provided with two fixtures (water
closets/urinals) for the men’s and two water closets for the
women’s for any restaurant over an occupant load of ten. A
unisex facility would be acceptable under footnote 16 which
allows unisex facility in a restaurant with 10 or less occupants
and the total number of employees in four or less. The IAPMO
interpretation seems to create a burden upon the small
restaurant with an occupant load from 11 to 49. The committee
will likely present its interpretation to the Chapter at the next
Chapter meeting.
Mike would like to have all interested members attend the next
committee meeting at 10:00 a.m. at the SOS Club immediately
preceding the next Chapter meeting for the continuing
development of Chapter-wide uniformity related to the
interpretation of codes.
____________________
For July 16th, 2009 agenda, see the Home Page.
The theme for this week is "Who can design what?"
____________________
Thursday May 21st, 2009
THEME – Changes In Use / Occupancy
The Yosemite Chapter of ICC encourages you to attend its Code
Discussion Group, starting at 10am and ending just before our
monthly ICC Chapter meeting, located in Modesto’s S.O.S Club
With uniformity, training, debate, and networking as points of
interest, the committee would love to see as many members
represented as possible; please encourage and support one of
your staff to attend.
Currently, we are discussing how various jurisdictions treat the
plan review of projects involving a change in use and/or
occupancy
Committee Minutes will be posted in the future. If you have any
questions, contact Mike Petersen by email.
|
|
|
