What a view template controls, and what to review separately.
A view template helps maintain consistent representation. To make it useful, the team needs to know which properties it controls and which decisions belong elsewhere.
1. Review the included properties
A template can control properties of the view's representation. The specific configuration depends on its type and on the options included in the template.
Check the property list before treating a change as an individual view setting. A property controlled by the template should be edited according to the project's organization.
2. Decide where scale is managed
When the template controls scale, associated views follow that criterion. If several scales are required, define an explicit strategy: separate templates or a property managed outside them.
The choice should respond to how the views are used. A clear template name helps communicate the discipline, purpose and documentation type it has been prepared for.
3. Distinguish representation from annotation
Dimension types define properties specific to dimensions. Tag families and types determine the information that can be displayed and how it is represented.
A view template does not replace the preparation of those families or guarantee suitable geometric references. Review annotation elements separately.
4. Build a maintainable standard
Test the template on representative views before applying it more widely. Check categories, detail level, scale and annotations within the intended sheets.
Document the template's purpose and the criteria for modifying it. A useful standard distinguishes a project exception from a change that should apply throughout.
Checks for consistent representation
- The template matches the view type.
- Controlled properties have been identified.
- The scale strategy is shared.
- Dimension types and tags were reviewed independently.