Company defualt CAD profile

[kevin_harms]

Hi I am an occasional use of Pro-E WF3. We have a company that designs products for us that uses the Pro-E default unit of inches. We would like them to use mm as the default. Aside from them remembering to change the default units each time to mm is there a way to set up Pro-E to default to mm each time they start a new model? Is there a way that this default could only be set for my company only? I seem to remember from my days with Pro-E 2001 that there is a way to set up specific company standards for modeling and drawing. It has been so long that I forgot what this is called or how to do it. Please provide me some insight into what this is called and how to get started. The reason I ask is that they model our parts in mm dimensions using the Pro-E default of inch units so the models always come to us 25.4 to 1 scale. Sometimes they remember to use mm and sometimes they forget to change the units and then have to redo the model. Setting up some kind of company default would seem to help solve this issue.

Kevin Harms

Mechanical Engineer

Tripp Lite

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[dgschaefer]

It is possible, but the ability to set client specific configurations is
not built into Pro|E per se. What they need is a config.pro file for
each client or a separate start part for each client. They would still
have to remember to load the config file or use your start part.

Frankly, I'm surprised that your vendor isn't pursuing this on your
behalf. It would seem in their best interest to give you what you
specify and to come up with a way to make sure that happens.

If I might do a little self promotion, for Design Central it's very
important to us that what we do matches the standards of our clients, so
we have developed an internal system using batch files that load company
specific config files at Pro|E start up. It prompts the user at Pro|E
launch to choose the client that they are working on and then loads the
specific config file for that client. It's not fool proof, but it
certainly makes it harder to build parts that aren't to the client's
standards.

Doug Schaefer

[acaldwell]

Start Up Tools from Inneo also does this. Simply creating "projects"
for each client or version of Pro/E. It then automates the config file
building and can even point you into different sets of folders for your
pro_stds.



Along with this you get some really good tools.



We used to do the batch file thing and it becomes a nightmare when you
are dealing with 5+ clients and enviroments at a time.



Thanks,

Allen



Allen Caldwell | PDC Team Manager | Project Engineer

952-435-5533 x 114 | EAC Product Development Solutions

acaldwell@eacpds.com | www.eacpds.com

[dgschaefer]

I thought Start Up tools was a Tri-Star product? I casually looked at
it in the past, but not in depth. Looks like I should give it another
look.

Thanks,

Doug Schaefer

[acaldwell]

No, Tri-Star is a reseller for it and so are we.



It was developed by Inneo and they continue to update it and provide
maintance builds. EAC has customized it to include some additional
mapkeys and files. Not sure what Tri-Star offers in the way of training
and customization but it is something EAC does with each seat.



Thanks,

Allen



Allen Caldwell | PDC Team Manager | Project Engineer

952-435-5533 x 114 | EAC Product Development Solutions

acaldwell@eacpds.com | www.eacpds.com

[dandersonjr]

What does it cost?



Thanks
Don A

[dgallup]

It is very simple to do this yourself. You just need config.pro files in each project directory that set the startparts, drawing formats, etc. Then either make separate desktop icons to start Pro/E in each project directory or simply change the working directory to the project directory & load the config.pro. I use the second approach since we have way to many different programs to have a startup icon for each one.