well said.
i may add that the very 1st step in the design is establishing the design
conditions for the pressure/temperature together with the different loading
conditions (siesmic, wind, etc.). this is the easy part - the hard part is
ensuring compliance that all the requirements of applicable Code say B31.3
and Section IX has been meet. Any oversight on the part of the designer will
ahve a direct contribution leading to piping failures.
it seems to me that one should not only be conversant with the piping rules. having a good understanding of the piping failure or mode of piping failure is also important in achieveing a good and reliable design.
talking about checklist there is an article that appeared in June 1997 issue of CE - checklist for sources of piping failures.
> ----------
> From: Christopher Wright[SMTP:chrisw@skypoint.com]
> Reply To: <a href="/group/PipingDesign/post?postID=11BpEqW2jg83UKBkQ3e8jIOHyYu13qm7XxD-nMDT6wRo20uE4_rORz1_IsiccIvVAwnGvhl5PMys9VCXqxH7dqDYwg">PipingDesign@yahoogroups.com</a>
> Sent: 12 June, 2001 3:40 AM
> To: ?
> Subject: Re: [PipingDesign] Design checklist?
>
> >Read the part of the contract that concerns yu as a designer.
> I'll just add a little bit to this, starting with asking yourself what
> you intend to accomplish with a check list. Ask the question both
> ways--'What would happen if you _didn't_ have a check list? If you can't
> answer that question, find something else to do because you need to know
> what you expect to accomplish before you can know if you're finished. You
> may find out at this stage that your boss tasked you with this in order
> to appear more managerial, which isn't a very good reason to do a
> checklist.
>
> You might also want to think of instances where checklists are used and
> why. Generally, they end up as tools to formalize long routines to make
> sure things are always done the same way in the same sequence, so that
> something important isn't overlooked. This isn't usually the way
> engineering design works. Design cycles are ordinarily unique to an
> office and to a particular job. Trying to force a job to fit the mold of
> previous work usually isn't very productive. There are lots of fairly
> routine sub-tasks, but an entire design sequence is seldom repeated,
> except in the most general way.
>
> About the best you can do is sit down and plan out the job from finish to
> start. List the deliverables for the job, then back through each one the
> see what specific item is needed to complete each deliverable item, then
> the item next before and so on back. What you'll have is a work plan and
> with a little extra effort you can see which tasks are the milestones
> which need to form the checklist. Add dates and dollars and it'll look an
> awful lot like an organized approach--probably better than a checklist..
>
> Christopher Wright P.E. |"They couldn't hit an elephant from
> chrisw@skypoint.com | this distance" (last words of Gen.
> ___________________________| John Sedgwick, Spotsylvania 1864)
> <a href="http://www.skypoint.com/~chrisw">http://www.skypoint.com/~chrisw</a>
>
>
> _____________________
> Piping Design Central
> [ http://www.PipingDesign.com ]
> ________________________________________
> We hope you find this newsletter useful.
> If not, you can unsubscribe at:
> <a href="/group/PipingDesign/post?postID=MJ9vlTak9Unyva97w3TjrRtmvgIpTmeN4Uy6SJYYz98WPWv62q-hjPUSIViBLKcV02GVA4Ly9JRV1cdoT9EQf9orqtByRUchlfeodZweEA">PipingDesign-unsubscribe@yahoogroups.com</a>
> Post message: <a href="/group/PipingDesign/post?postID=11BpEqW2jg83UKBkQ3e8jIOHyYu13qm7XxD-nMDT6wRo20uE4_rORz1_IsiccIvVAwnGvhl5PMys9VCXqxH7dqDYwg">PipingDesign@yahoogroups.com</a>
> Subscribe: <a href="/group/PipingDesign/post?postID=VAq0qow-hlqIaUDliSkneRvLiw2UCCPZAa9_4A6tf5bJFPgk1J4NGVnDvNkpsSl7z_ghzPmWhL5tgeyQdUsDp4CLSsRiyodpGf2F98E">PipingDesign-subscribe@yahoogroups.com</a>
>
> Your use of Yahoo! Groups is subject to <a href="http://docs.yahoo.com/info/terms/">http://docs.yahoo.com/info/terms/</a>
>
>
Received on Tue Jun 12 04:26:00 2001
This archive was generated by hypermail 2.1.8 : Tue Mar 04 2008 - 11:40:12 EST