Christopher Wright wrote:
>>"Clash or interference detection is a necessary task in 3D design and
>>one of its big values".
>
> That's marketing bullshit. You can have the same problems with
> interference using a CAD package if the operator doesn't know his job.
> The easiest thing in the world is for some CAD monkey to lay out
> something which can't be assembled because doesn't understand
> fabrication or the field circumstances.
>
> I bet the ad copy guy who wrote it probably hasn't the foggiest about
> how wretched as-builts of existing construction can be, even in nuke
> plants which are supposed to be so precisely engineered.
What, are you saying that accurate as-builts are routinely not done?! Quel surprise!
One of the problems with 3D piping software is that everyone has to religiously follow all the software-dictated procedures in order for it to work properly (because a computer only knows ones and zeros). Of course, anything short of dictator-like control over the operators' activities can possibly cause errors that make the whole system go crashy. Or maybe it was a Windows DLL conflict. Or a power spike. Or a random error generator built into the network (OK, now I'm stretching the concept a bit far).
Paul Received on Sun Apr 24 14:50:00 2005
This archive was generated by hypermail 2.1.8 : Mon Oct 27 2008 - 20:24:07 EDT