cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Best Practice for Pro/E Formats (.frm) in Windchill?

Highlighted

Best Practice for Pro/E Formats (.frm) in Windchill?

Gang,

SolidWorks is our primary CAD application, so sheet format management is very easy there.

However, we have quite a few engineers who are still using Pro/E (WF3) for maintaining legacy data, or converting active projects.

What is the best approach for administering the Pro/E sheet format (.frm) files? We've tried putting them in a central location, but people seem to repeatedly accidentally check them out, check them in, Release them, and...wait for it...Obsolete them (the last state in our LF).

Any way to "lock" these so they can't be accidentally checked out? Or am I missing a simpler solution?

Thanks!

Michael

3 REPLIES 3

RE: Best Practice for Pro/E Formats (.frm) in Windchill?

Have them in a different Library and create Drawing templates from them. Have thisLibrary onlymodifiablebyCAD admins and read only for the rest.Changeyour config.pro in you universal location to point to Windchill for the drawing templates and formats directory.

RE: Best Practice for Pro/E Formats (.frm) in Windchill?

Hi Michael

we have done exactly what Patrick explained

@ Patrick, I have seen a few thread written by Com dev and there are always the same attachments which are also not related to the subject.

Is that intentional ?

RE: Best Practice for Pro/E Formats (.frm) in Windchill?

If you read my attachments, the solution allows you to map the ProE PTC_COMMON_NAME and name directly to Windchill Name and Number. You can now map all the PTC_WGM_* attributes to the format. For drawings you have to make the decision if you want the &d..* for the ProE drawings. Thus, you don't have to create extra ProE parameters and Windchill IBAs for mapping. From the formats you have to create drawing templates to autopopulate the values from the ProE CAD objects. If these formats, symbols, templates, dtl, startfiles, etc are stored in windchill, you have to point your config.pro to the directories of Windchill. You have to do this while connected to windchill. To avoid the issue of working off-line, You can programattically, use a config.pro which is meant for local use and a config.pro that is meant for network connected to Windchill use. That can be run/called in the ProE.bat file. If connected to Windchill, the script will download all the new ProE stanadards from Windchill for a backukp for local. If the user, is disconnected from windchill/network and has a standalone license, The user just has to start up ProE again which will check if they can connect to windchilll. If not, the program will copy the config.pro_local to the config.pro in ProE/text to have the directories in the appropriate local paths. Sometimes, implementations have external Windchill's with https://... which alows the user to connect without the use networkshared drives. This allows uses to have the configuration/standards via web. Make sure when you register your server on ProE, that the name is the fully qualified host name of the windchill server. It avoids issues with the path locations in config.pro.