Designing Process Guide Templates
Process guide templates are designed by an expert Creo Simulate user to guide a novice user through all the steps necessary to perform a design and analysis. Template designers should create separate templates to satisfy a range of simulation requirements of a model. The Process Guide provides a step by step guide to a user to set up and run an analysis. You can design separate templates according to the simulation requirements of your model. When designing a template, you must consider the following points:
the design requirements of your model and its components
the actual geometry of a model or component under consideration
the model's real world surroundings such as loads and constraints
type of analysis to perform such as static, modal, prestress, buckling, and vibration analyses
the way you want to evaluate the results
your design goal
The process guide template is an XML file with a predefined structure. You can create a process guide template using one of the following tools:
Process Guide Template dialog box—Provides an easy to use user interface to create or edit a process guide template.
A text or XML editor—In this case you need to understand the process guide template structure and use the correct tags as required.
A process guide template comprises the following elements:
Header Element
Process Elements
Language-Specific Limitations
Creo Simulate allows you to create process templates in any language. While defining a task in a process template, you can add a description and label for that task in any language that Creo Simulate supports. Creo Parametric supports only a limited number of language encoding types. If your template contains the task description or label in a language other than English, you need to specify the encoding in the file header. Valid values for encoding the Japanese language are SJIS (on Windows only) and UTF-8.
To set the encoding type in a process template file containing Japanese characters, add the following line at the top of the XML template file:
<?xml version="1.0" encoding="SHIFT_JIS"?>
or
<?xml version="1.0" encoding="UTF-8"?>
¿Fue esto útil?