RE: Branch Connection.

This stuff works really well "IF" you use it right - your organization currently seems to be not using it right - no surprise really - that is the norm - that's why this stuff gets a bad rap.

Allowing designers to use whatever they want is not a good solution either - these days many piping designers initially get into the business because they know CAD and they learn about piping after. It's all about control - someone needs to control the specs - the "spec_compiler_guy" should be either a piping designer/engineer - the pipe specs are the heart of any piping system - if they are not right, big problems - no matter if you are talking drafting, 2D or 3D.

Internal procedures, processes and staffing are management issues - sounds like management doesn't know how to steer the ship - again no real surprise - usually takes a few years of using these tools to find out how to best use them UNLESS you decide to hire a few experienced guys, invest in training your own and attend conferences to learn how others are using these tools - do this and you can shave years off the learning curve.

Any mangers out there - here's my advice to you. Your IT infrastructure is a utility just like your light, heat and water - develop an IT staff that can provide you with bandwidth, backup, printing, e-mail, internet and system support. Application support belongs with the various departments. If it's a piping (accounting ...) application - it should be installed, configured and supported by the piping (accounting ...) department. Develop your experts within the department. IT staff typically have no background in piping (accounting ...), it is laughable to expect them to implement, customize and debug applications that they do not understand or use. Hire a few experienced people and carefully pick those you want to develop into experts. Train your staff, send them to user groups and conferences, pay them competitively - in the end it is so much cheaper to follow this philosophy than to struggle with these tools.

Not trying to blow myself up here just think my jobs go smoother because - When I get hired the company gets a plant design engineer with a lot of IT experience running the show - experience makes a difference. I also jump in where\when ever I am needed on the project as a designer, engineer or manager - this works well because I am often the only one who understands the whole project data management process.

It's all about the team - people are everything - software does nothing on its own.
Paul Hawco
Mechanical Engineer
Neill & Gunter (Nova Scotia) Limited
<a href="http://www.neillandgunter.com">http://www.neillandgunter.com</a> <<a href="http://www.neillandgunter.com/">http://www.neillandgunter.com/</a>>

130 Eileen Stubbs Ave, Suite 1 South
Dartmouth, NS, Canada B3B 2C4
Phone 902-434-7331 x1296
Fax 902-462-1660

From: <a href="/group/PipingDesign/post?postID=C4KIHWCPtYUhc9djkrVUHFrmtOCKUF9UDF2MHCdvpcyHEuwGO-qM4db9bYI_bm_rRPyifN4n1jb_eYWZX3hPauFyBKzh6Q">PipingDesign@yahoogroups.com</a> [mailto:<a href="/group/PipingDesign/post?postID=C4KIHWCPtYUhc9djkrVUHFrmtOCKUF9UDF2MHCdvpcyHEuwGO-qM4db9bYI_bm_rRPyifN4n1jb_eYWZX3hPauFyBKzh6Q">PipingDesign@yahoogroups.com</a>] On Behalf Of Paul Bowers
Sent: Thursday, September 15, 2005 1:31 PM To: <a href="/group/PipingDesign/post?postID=C4KIHWCPtYUhc9djkrVUHFrmtOCKUF9UDF2MHCdvpcyHEuwGO-qM4db9bYI_bm_rRPyifN4n1jb_eYWZX3hPauFyBKzh6Q">PipingDesign@yahoogroups.com</a> Subject: Re: [PipingDesign] Branch Connection.

Hawco, Paul R. wrote:

> 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.

I think it IS a software issue, since it stops/delays a designer from immediately correcting a problem (as compared to the pencil and paper alternative). A solution delayed is often a solution forgotten about as the project progresses.

Process formalization can be widely different from organization to organization and not all companies can afford to have a dedicated spec_compiler_guy for each project. spec_compiler_guys also tend to wait

for authorization from "upstairs" since they often don't know piping design.

It doesn't help that IT CAD guys tend to get shifted around after the bulk of the work is finished up front, destining the devilish dangling design details to be determined.

Paul

[Non-text portions of this message have been removed] Received on Fri Sep 16 10:15:00 2005