Skip to main content
A
AM_92433471-Visitor
1-Visitor
January 13, 2022
Solved

managing standards

  • January 13, 2022
  • 1 reply
  • 4199 views

Hi;

I hope you all are doing fine.

In our company we defined a set of standard for start parts, formats, materials, .dtl, etc ... and as we need to keep updating these files time to time my question is that what is the best practices for managing these file centrally for all users and enforcing all users to these standards.

 

Sincerely yours.

 

Best answer by sacquarone

Hello @AM_9243347 

 

Suggestion of @kdirth is VERY GOOD, as long as number of Creo Parametric users is low-to-medium.

 

Nevertheless, if number of users is high, above approach, even though always working, is nevertheless challenging due to following constraints in lots of situations:

  • Not all users install Creo in the same path (so .... how to ensure that "latest config.sup" is being used and placed at the proper location?)
  • Several users are working in different projects, using different versions of Creo parametric (so ... how to ensure that "the good config.sup of the version in use" is the good one for the given version, and up to date, in other words latest?)

With pure Creo Parametric capabilities, those kind of challenges just cannot be handled. This is the reason why the administrators of most of our "big customers" (with lots of end users, working for lot of different projects, sometimes lnked to different windchill instances in different versions):

  1. Control exactly where the different versions of Creo Parametric are installed by forcing users to perform Silent Installations (refer to article 81760 for further technical details on this)
  2. Are configuring the "startup phase" of Creo Parametric with Windows scripts. Usually, those scripts:
    • Are batch files (*.bat extension)
    • copy config.pro and sup files:
      • from a network location ("read" access for most of users, "write" access ONLY for administrators)
      • to the startup directory (or Creo Parametric Common Files "text" folder)
    • ensure "protkdat" entries point to the "good location" of eventual toolkit being used
    • launch the "parametric.exe" at the end of the script

I'm sorry not being able to provide an "easier way" to achieve this, but above challenges cannot be covered from a technical standpoint without a good control of what happens "behind the scene" in the folders - working/startup directories and creo load points (requiring a setup therefore via an approach to be considered outside from PTC Application).

 

Regards,

 

Serge

1 reply

kdirth
21-Topaz I
kdirth21-Topaz I
21-Topaz I
January 13, 2022

I would suggest creating a config.sup file to place in the load point folder (e.g. C:\Program Files\PTC\Creo 7.0.5.0\Common Files\text/) to control the config settings that you want to control.  The config.pro settings cannot be overwritten by personal config.pro files.  This does not force the use of these files and settings, but does make users choose to not use the default to get away from them.

 

Some configs to consider for the .sup file:

tolerance_standard ansi

drawing_setup_file K:\std_draw.dtl

make_aux_view_notes yes

make_parameters_from_fmt_tables yes

pro_dtl_setup_dir K:\ptc_configs

pro_format_dir wtpub://Windchill/Libraries/Standards/Formats/

pro_symbol_dir wtpub://Windchill/Libraries/Standards/Symbols/

pro_table_dir wtpub://Windchill/Libraries/Standards/Drawing Tables/

symbol_instance_palette_file K:\symbols

todays_date_note_format %Mmm-%dd-%yy

pro_unit_length unit_mm

pro_unit_mass UNIT_KILOGRAM

pro_material_dir K:\Materials

search_path_file $CREO_COMMON_FILES\afx\parts\prolibrary\search.pro

template_designasm wtpub://Windchill/Libraries/Standards/Templates/start_assembly.asm

template_sheetmetalpart wtpub://Windchill/Libraries/Standards/Templates/start_sheetmetal.prt

template_solidpart wtpub://Windchill/Libraries/Standards/Templates/start_part.prt

layout_symbol_dir K:\symbols

pro_plot_config_dir K:\plot_configs

weld_ui_standard ansi

There is always more to learn.
    S
    sacquarone21-Topaz IAnswer
    21-Topaz I
    January 13, 2022

    Hello @AM_9243347 

     

    Suggestion of @kdirth is VERY GOOD, as long as number of Creo Parametric users is low-to-medium.

     

    Nevertheless, if number of users is high, above approach, even though always working, is nevertheless challenging due to following constraints in lots of situations:

    • Not all users install Creo in the same path (so .... how to ensure that "latest config.sup" is being used and placed at the proper location?)
    • Several users are working in different projects, using different versions of Creo parametric (so ... how to ensure that "the good config.sup of the version in use" is the good one for the given version, and up to date, in other words latest?)

    With pure Creo Parametric capabilities, those kind of challenges just cannot be handled. This is the reason why the administrators of most of our "big customers" (with lots of end users, working for lot of different projects, sometimes lnked to different windchill instances in different versions):

    1. Control exactly where the different versions of Creo Parametric are installed by forcing users to perform Silent Installations (refer to article 81760 for further technical details on this)
    2. Are configuring the "startup phase" of Creo Parametric with Windows scripts. Usually, those scripts:
      • Are batch files (*.bat extension)
      • copy config.pro and sup files:
        • from a network location ("read" access for most of users, "write" access ONLY for administrators)
        • to the startup directory (or Creo Parametric Common Files "text" folder)
      • ensure "protkdat" entries point to the "good location" of eventual toolkit being used
      • launch the "parametric.exe" at the end of the script

    I'm sorry not being able to provide an "easier way" to achieve this, but above challenges cannot be covered from a technical standpoint without a good control of what happens "behind the scene" in the folders - working/startup directories and creo load points (requiring a setup therefore via an approach to be considered outside from PTC Application).

     

    Regards,

     

    Serge

      B
      23-Emerald III
      BenLoosli23-Emerald III
      23-Emerald III
      January 13, 2022

      I use a network install of Creo so all users are using the same set of files. I have the config.sup and config,pro file in the <loadpoint>/text folder for the company settings. I use a launch script (batch file) for the users to start Creo that copies a config.pro file to their home folder every time they launch Creo. They also have a local config.pro file in their start-in directory that they can add custom mapkeys or other settings in. I do this because I have 2 groups of users with different requirements and drawing templates. One group is also still on Windchill 11.0 with Creo4 while the other group is on Windchill 11.1 and Creo 7. It is very easy to upgrade the launch batch file when that group gets upgraded. The launch file also controls which licenses the users are using.

        Terms & ConditionsCookie settingsAccessibility statement