Could be, and I guess I can goof, but the formula for measuring the
volume of a cylinder has been around for a long time and as far as I
can tell works pretty well. I also know that without being able to
estimate a result I wouldn't know that I err far more often punching
buttons on a calculator than I do writing equations on a white board
or piece of paper. Who knows how many mistakes I make entering
multiple data points into a complex program where I'm unable to even
guess at what a likely result should look like? I have to be missing
something here. I know all the committee guys are too honest to put
something in a code that can only be accomplished with some expensive
proprietary do-dad.

On Wed, Jun 17, 2009 at 4:26 PM, Todd Williams<[email protected]> wrote:
> Could it have something to do with the fact that the multi-thousand
> dollar program is UL listed and your smelly feet aren't?
>
>
> At 07:19 PM 6/17/2009, you wrote:
>>As I read this it seems to say that the same rules apply as before but
>>to prove the system size I have to use an approved computer program.
>>Now I'm no math whiz but I can calculate the capacity of a bunch of
>>tubes (pie is square times length equals cubic X, convert X cubes to
>>cubic feet, convert the smelly feet to gallons, add up all the
>>different sized tubes and....). Time consuming but why do I need a
>>multi-thousand dollar program for a task that I can do with paper and
>>pencil?
>>
>>On Wed, Jun 17, 2009 at 3:57 PM, Roland
>>Huggins<[email protected]> wrote:
>> > nothing changed (except for dwelling units).  The 500 gal w/o QOD or
>> > 750 gal limits still apply.  The timed approach is just for exceeding
>> > them.   As for dwelling units, it is not 15 sec regardless of size.
>> >
>> > Roland
>> >
>> > On Jun 17, 2009, at 3:44 PM, Ron Greenman wrote:
>> >
>> >> So what drove the change from the old way of working trip times (under
>> >> 500 gal. all was good, 500-750 gals. and either 60 seconds or QOD,
>> >> over 750 gals. QOD and all is good)? was it due to systems failing due
>> >> to too long trip times or was it a way to sell an expensive computer
>> >> program? If due to failures did it happen in a cross section of
>> >> buildings or in certain types of buildings and if the latter is it
>> >> necessary to treat all systems equally? Certainly requirements to trip
>> >> test everything to 60 seconds in years past was based on local
>> >> requirements arrived at collectively by AHJs because they wanted it
>> >> and it was complied with enough to become the usual thing to do until
>> >> it became codified--first locally and then in 13. Where's the data
>> >> that supported this costly change at point in this migration from what
>> >> 13 said to what it says now? Enquiring minds want to know.
>> >>
>> > _______________________________________________
>> > Sprinklerforum mailing list
>> > http://lists.firesprinkler.org/mailman/listinfo/sprinklerforum
>> > For Technical Assistance, send an email to: [email protected]
>> >
>> > To Unsubscribe, send an email to:[email protected]
>> > (Put the word unsubscribe in the subject field)
>> >
>>
>>
>>
>>--
>>Ron Greenman
>>at home....
>>_______________________________________________
>>Sprinklerforum mailing list
>>http://lists.firesprinkler.org/mailman/listinfo/sprinklerforum
>>For Technical Assistance, send an email to: [email protected]
>>
>>To Unsubscribe, send an email to:[email protected]
>>(Put the word unsubscribe in the subject field)
>
> Todd G. Williams, PE
> Fire Protection Design/Consulting
> Stonington, Connecticut
> www.fpdc.com
> 860.535.2080
> _______________________________________________
> Sprinklerforum mailing list
> http://lists.firesprinkler.org/mailman/listinfo/sprinklerforum
> For Technical Assistance, send an email to: [email protected]
>
> To Unsubscribe, send an email to:[email protected]
> (Put the word unsubscribe in the subject field)
>



-- 
Ron Greenman
at home....
_______________________________________________
Sprinklerforum mailing list
http://lists.firesprinkler.org/mailman/listinfo/sprinklerforum
For Technical Assistance, send an email to: [email protected]

To Unsubscribe, send an email to:[email protected]
(Put the word unsubscribe in the subject field)

Reply via email to