On Dec 30, 2005, at 11:48 AM, John Luf wrote:
> The bottom line is this...
> In order to establish whether a system will require a computerized
> numeric solution or not you need the following information:
> 1)Geometry how flexible is the layout?
> 2)Boundary conditions i.e. restraints, hanger locations etc. because
> they also impact flexibility.
> 3Displacement data... temperatures the system will operate at as
> well as imposed displacements at the P.O.C..
Let me add a couple of items in the form of questions to ask yourself--
Is the application of software productive? Will you spend more time and
effort monkeying with the computer than the program will save?
Do you understand the Code requirements?
Have you defined the problem and decided what engineering issues you
need to address?
Are you comfortable with the input process? Can you generate a model
that will address the engineering issues?
Are you familiar enough with the software to interpret the results in
terms of Code requirements?
All those questions need unequivocal 'yes' answers, backed up by facts you can put your fingers on
If you're using the software because you know it's the best tool to produce the results you need in the most economical way, go for it. OTOH, if you're using the software to do a problem because you don't understand how to do it any other way, you're in serious trouble. You won't have the knowledge to make the necessary engineering decisions to formulate the model, troubleshoot mistakes, and validate your results.
Christopher Wright P.E. |"They couldn't hit an elephant at <a href="/group/PipingDesign/post?postID=7pI8EiRqcPYSPo1l2NeJY1sUQqbGSHtTK3XmjwiFMP-N1J7qp7RQwSC8Sd5Pj7Qrt5pIcFnM_dE-tYp7">chrisw@skypoint.com</a> | this distance" (last words of Gen.
.......................................| John Sedgwick, Spotsylvania1864)
This archive was generated by hypermail 2.1.8 : Tue Mar 04 2008 - 11:40:45 EST