View Type Names

For browser readability, set the view to an appropriate type and use a numeric prefix for visibility when sorting in ascending order. The view name can be anything, but for planes the name should include the associated level name. This section explains the naming conventions for type names and view template names for each view.

View Template Names

By prefixing the view template name with an alphabet, you can narrow down the target by keyboard type when selecting the view template. If you want to express the scale in the view template name, omit “1/” such as “Floor Plan 200” to avoid redundant names. As a reference, in addition to the naming conventions for each view in the next section, prefixes for view templates that are often prepared are shown.

Use distinction	view template name prefix
Area plan	aArea_
Schedule	_ (underscore)

Floor Plan

Adding a number to the view type name makes the browser layout easier to see. Also, since planes have many uses for views, it is recommended to group their uses by numbers. Since the number of view templates will be large as well, a naming convention will make the list of view templates easier to identify. If you combine the prefix that identifies the view family with the view template name and the character string that indicates its purpose, the list will be grouped, making it easier to see. In the case of a flat surface, by combining “p” representing “plan” with the purpose, you can narrow down the target by typing two letters on the keyboard. In the table below, the “View Template Name Prefix” column shows the recommended prefix. Create variations with underscores (e.g. “p_plan”).

Type Name Prefix	Use Distinction	View Template Name Prefix
00～10	Work Management	pWork
11～20	General Map Related (Including Application/Notification Map)	p
21～30	General Drawings (For Usage Such As Meetings)	p
31～40	Detail View	pDetail
41～50	Specification Range Diagram	pProp
51～70	Key Plans	pKey
71～80	For Coordination	coordinate
81～90	Structural Use (Excluding Floor Plans)	S
91～	Shop Drawing Specific	pShell(floor framing/foundation/pile plan) pDoc(detailed plan)

Structural plans have different view families and are grouped differently in the browser, so different rules apply. There is also a method to create a work view for each individual, but it is not recommended because the work history depends on the person. If there is a view setting that is necessary for work, creating it as a new view type will implicitly inform others as points to note in modeling, so this method is recommended. If you include types for modeling reference management, such as dimension management between reference surface elements and global parameter settings, in the work management group, the history and intentions of modeling will become easier to see.

Ceiling Plan

The view type prefix rule can be a rough rule, because unlike planes, there are not many types of views. Since there are only a few types of prefixes for view template names, rules can be sufficient to indicate that they are for ceiling recesses. The “view template name example” shown below uses the “c” of “ceil”. Structural plans are grouped into Structural plans families, so you don’t need to consider line-of-sight for view type names, but view templates are grouped into ceiling plans, so they should be grouped with a prefix. is recommended. In the example below, we use the ‘f’ prefix described below for the view template name for the skeleton view.

type name prefix	Use distinction	View template name example
00～10	Work management	c_Working
11～20	General arrangement drawings	c_Plan200
21～30	Detail view	c_DetailedPlan
91～	Shop Drawing Specific	cDoc_DetailedPlan fShell_StrLookup

Cross Section

Since cross-sectional views are often used to assist modeling and confirm shapes, it is easier to operate if you classify by part in addition to the type by result image. In the case of type by body part, the existence of the type itself will be known to others as a point to note in modeling. For this reason, it is recommended that the cross-sectional views included in the site-specific type be edited by many people and not included as deliverables. If artifacts are required, it is recommended to have a separate type for artifacts. Since cross-section views with different scales are expected to be created in the skeleton drawing, it is recommended to classify them by type, such as by floor, and manage them collectively. The fitting figure creation function of the Revit tool for Japan is generated as a section view. If you use this feature, use a fitting type that stores this to keep your browser clutter-free. As for the view template name, since there are not as many types of view templates as there are for plan views, the rules are sufficient to indicate that they are for section views. The “view template name example” shown below uses the “s” of “section”.

type name prefix	Use distinction	View template name example
00～10	Work management	s_WorkingSection
11～20	General arrangement drawings	s_Section200
21～40	Detail view	s_DetailedSection50
41～70	Part	(mixed)
81～90	For structure (including shaft diagram)	s_StrSection200
91～	Shop Drawing Specific	sShell_StrSection

Elevation

The view type prefix rule can be a rough rule, since there aren’t many types of views. Since there are only a few types of prefixes for view template names, it is OK to use a rule that makes it clear that they are for elevations. The “view template name example” shown below uses “e” in “elevation”. However, when creating interior elevations, they are grouped into elevation families, so having a clear separation between types can help with visibility. Since they may also be used for laying out tiles, panels, etc., sort them by type name. Please judge as appropriate whether to group the development plan type unique to the production design.

type name prefix	Use distinction	View template name example
00～10	Work management	e_WorkingElevation
11～20	General arrangement drawings	e_Elevation200
21～	(spare)	–
31～	Development diagram system (example: panel allocation study)	e_InteriorElevation100 e_LayoutPlan50
91～	Shop Drawing Specific	(appropriately)

Structural plan

The view type prefix rule can be a rough rule, since there aren’t many types of views. Since there are few types of prefixes for view template names, rules to the extent that it can be recognized as a structural plan are fine. The “view template name example” shown below uses “f” in “frames”. For structural plan, we have prepared view settings such as filters assuming the use of color checks such as levels, but if view setting management becomes complicated, there is also a method of performing color checks with a link file.

type name prefix	Use distinction	View template name example
00～10	job management	f_WorkingStr
11～20	General arrangement drawings	f_StrLookup200 f_StrLookdown200
21～	(for color check)	f_StrLookupCC200 (CC:ColorCheck)
31～	(spare)	–
91～	Production design specific	fShell_StrLookdown50

3D View

Since 3D views have orthogonal views and perspective views, it is recommended to manage the types so that they do not mix. By default, they are sorted into types named “Perspective” and “Orthogonal projection”. An additional orthogonal view named “{3D – username}” is automatically created. This is each user’s “default 3D view” and will be the view used by the selection box tool. Therefore, the view named “{3D – user name}” will automatically increase when a user is added, so it is efficient to leave the default type as the storage destination type. Type management other than these is optional, but in order to keep the work history in the view, it is recommended to classify by application or part rather than by user attributes of the view. The view template name can be any rule that indicates that it is for a 3D view. The “view template name example” shown below uses “t” of “three dimentional”.

View type name example	View template name example
Path (default)	(appropriately)
Interior Path Examination	t_PerspectiveReview
Orthographic (default)	(appropriately)
Orthogonal frame confirmation	t_CheckStr
Orthogonal atrium cross section	t_CheckSection

Schedules

Using category abbreviations as prefixes makes browsers easier to read. However, for schedules, category names are automatically assigned when views are created, so you can use them as prefixes. When adding a prefix to the member summary, use “P + category abbreviation”.