>we're not
>talking here of designing the process or the viability of the project
>because if that is the case then
That was my point, although I probably disguised it better than I
intended. The original post didn't really say what part of the design he
meant. If you're just talking about using the code, that's one thing, but
there are a lot more areas involved in design, starting with establishing
process parameters. TO make up any kind of checklist, you need to know
the work that's needed.
Christopher Wright P.E. |"They couldn't hit an elephant from <a href="/group/PipingDesign/post?postID=xhZQd_2AJQaRarmjJ1igiClMNe329roDCGUBD7IjVcOi18Z4In7GK7M0ziQVAsadDCoBbgDvCuAkmNg">chrisw@skypoint.com</a> | this distance" (last words of Gen.
___________________________| John Sedgwick, Spotsylvania 1864)<a href="http://www.skypoint.com/~chrisw">http://www.skypoint.com/~chrisw</a> Received on Wed Jun 13 10:51:00 2001
This archive was generated by hypermail 2.1.8 : Tue Mar 04 2008 - 11:40:12 EST