Paul,
I feel your pain - I really do, BUT that is not a software issue - that is a procedural problem. You need to formalize the process. One that has worked for me is to setup a spec change request form - write down what you need - walk it over to your spec_compiler_guy and hand it to him. Again it comes down to management making sure that they have the right people in the rights places.
From: PipingDesign@yahoogroups.com [mailto:PipingDesign@yahoogroups.com]
On Behalf Of Paul Bowers
Sent: Wednesday, September 14, 2005 11:06 PM
To: PipingDesign@yahoogroups.com
Subject: Re: [PipingDesign] Branch Connection.
Sare, Ralph H. wrote:
> Normally the type of branch connection is defined by the branching
table.
> The branch table is part of the Piping Specification. Basically your
Piping
> Spec described wether u need a reinforced pad, a tee or simply a stub
> connection for a certain service or commodity.
Legacy branching tables are often used to create permissible pipe-to-pipe connections within 3D or 2D modelling software. It can be a
real pain in the you-know-what to get some standard connection overridden by system administrators.
Piper: "We need a threaded coupling here due to [valid reason]"
Spec Engineer: "That's obvious, just put one in."
Piper: "The software won't permit it, you'll need to get the spec_compiler_guy to addd it."
Spec Engineer: "OK." [Spec Engineer forgets, or spec_compiler_guy fails to add alternative choice to database for whatever reason]
Result: Incorrect drawing and BM due the detail-level guys being restricted by software.
Paul
YAHOO! GROUPS LINKS
[Non-text portions of this message have been removed] Received on Thu Sep 15 10:14:00 2005
This archive was generated by hypermail 2.1.8 : Mon Oct 27 2008 - 20:24:09 EDT