What:
Views are where the model is edited. Views can also have annotation added to them (notes, dimensions, tags etc). Multiple views can appear on a sheet that contains a title block and is used to created printed drawings.
Why:
A project can end up with literally hundreds of views. If these are not structured it can be nearly impossible to find you way around the project.
How:
By using a mixture of naming protocols and shared view parameters. With standardisation the Project Browser can be sorted using view parameters.
Who:
All but TEMP views must only be created with agreement of the project Model Manager.
Description:
Views that are placed on sheets to create an issued document for the project.
Purpose:
Used to create the documentation set of current stage of the project.
Contents:
View and visibility settings must be set and maintained by a View Template (refer View Templates).
Only annotation that is part of documentation must be added.
Applies to View Categories:
All view categories.
Naming Convention:
The name must be same as what appears in the title on the sheet it is placed on (i.e. NEVER have a different Name on Sheet).
Structure so high level information is first, followed by lower level information.
Uppercase.
e.g. SECTION N-S AT GRID B
View Parameter Values:
Purpose.VW = DOCUMENT (optional if Drg Series.VW used)
Drg Series.VW = <sheet series number view appears on, e.g. 3000>
Subject.VW = <main content subject of view, e.g. Stairs> (optional)
Appears on Sheets:
Must appear on a sheet that is part of a sheet series.
NOT on a sheet that is a Presentation, Sketch or RFI.
(Note that in Revit a view can only appear on one sheet.)
Description:
Views that are used for presentation purposes.
Purpose:
Views created that are used to contribute to presentations.
For example; coloured plans; views for rendering; walkthrough views; views for controlling cameras.
Contents:
Anything.
Locking of 3D views and creating view templates might be considered.
Only annotation that is relevant to the presentation must be added.
Applies to View Categories:
All view categories.
Naming Convention:
The name must be same as what appears in the title on the sheet it is placed on (i.e. NEVER have a different Name on Sheet).
Uppercase.
e.g. VIEW FROM N-S
View Parameter Values:
Purpose.VW = PRESENTATION (optional if Drg Series.VW used)
Drg Series.VW = <sheet series number view appears on, e.g. 9000>
Subject.VW = <iso date of presentation with short description, e.g. 130830 Client Presentation> (optional)
Appears on Sheets:
Appear on sheets set up for the presentation.
NOT on a sheet that is a Document, Sketch or RFI.
(Note that in Revit a view can only appear on one sheet.)
Description:
Views that are used to create sketches for printing or issuing.
Purpose:
Views created that are used to describe parts of the project.
Typically for discussions with clients, consultants, project architects and directors.
Contents:
Anything.
Only annotation that is relevant to the presentation must be added.
Applies to View Categories:
All view categories.
Use view type labelled 'sketch' for elevations, sections and detail views (callouts).
Naming Convention:
Prefix the view with the drawing number the view appears on. (Use view parameter Name on Sheet to change what name is used on the sheet).
Uppercase.
e.g. SK80387-PLAN OF CLEAN ROOM
View Parameter Values:
Purpose.VW = SKETCH (optional if Drg Series.VW used)
Drg Series.VW = <empty unless there is a specific series you want to group, e.g. SK-900>
Subject.VW = <main content subject of view, e.g. Stairs> (optional)
Appears on Sheets:
Appear on sheets set up for sketches.
NOT on a sheet that is a Document, Presentation or RFI.
(Note that in Revit a view can only appear on one sheet.)
Description:
Views that are used to respond to a builder's RFI (Request For Information).
Purpose:
Views created of parts of the project relevant to answering an RFI..
Contents:
Anything.
Only annotation that is relevant to the RFI must be added.
Applies to View Categories:
All view categories.
Use view type labelled 'sketch' for elevations, sections and detail views (callouts).
Naming Convention:
Prefix the view with the drawing number the view appears on. (Use view parameter Name on Sheet to change what name is used on the sheet).
Uppercase.
e.g. RFI00803-PLAN OF CLEAN ROOM
View Parameter Values:
Purpose.VW = RFI
Drg Series.VW = <empty unless there is a specific set you want to group, e.g. person responding to RFI>
Subject.VW = <main content subject of view, e.g. Stairs> (optional)
Appears on Sheets:
Appear on sheets set up for RFIs.
NOT on a sheet that is a Document, Presentation or Sketch.
(Note that in Revit a view can only appear on one sheet.)
Description:
Views to assist working on the project that are shared by the team.
Purpose:
Views created to help navigate the model; show certain things; for exporting; for duplicating to create new views.
For example; Plan view of each level; 3D views of parts of the model; schedules for working in.
NOT used for managing the model (see MODEL MANAGEMENT below).
Contents:
Anything.
Applies to View Categories:
All view categories.
Use view type labelled 'working' for elevations, sections and detail views (callouts).
Naming Convention:
Must start with W_.
Lowercase. (can be sentence case, but never all uppercase)
e.g. W_Section
View Parameter Values:
Purpose.VW = working
Drg Series.VW = working
Subject.VW = <main content subject of view, e.g. Stairs> (optional)
Appears on Sheets:
Never appears on sheets.
Description:
Temporary or personal views.
Purpose:
Views created for a temporary reason, or views created by individuals to assist their work, but not required by any one else in the team.
These views must be periodically deleted to clean the project up.
Contents:
Anything. Note that there are standard references (e.g. section, elevation markers) for temporary views and levels.
These should be used when creating temporary views so that they are easily recognizable and will filter properly.
Applies to View Categories:
All view categories.
Use view type labelled 'working' for elevations, sections and detail views (callouts).
Naming Convention:
Must start with X_.
Lowercase. (can be sentence case, but never all uppercase)
e.g. X_Section
Personal views must contain creator's initials.
e.g. X-AMC_Section N-S facade
View Parameter Values:
Purpose.VW = <empty> (this is so new views will default to TEMP type)
Drg Series.VW = <empty> (this is so new views will default to TEMP type)
Appears on Sheets:
Never appears on sheets.
Description:
Views to that are a record that standards, codes and brief requirements have been met.
Purpose:
Views created for the purpose of adding annotation that shows requirements have been met. This may include dimensions, tags, text, filled regions. Also includes schedules that are structured to show compliance.
For example; views showing fire rated and smoke walls coloured; stair plans and sections showing dimensioned clearances; dimensioned plan views showing compliance with disabled standards.
Contents:
Anything.
Applies to View Categories:
All view categories.
Use view type labelled 'working' for elevations, sections and detail views (callouts).
Naming Convention:
Must start with V_.
Lowercase. (can be sentence case, but never all uppercase)
e.g. V_Section
View Parameter Values:
Purpose.VW = verification
Drg Series.VW = verification
Subject.VW = <main content subject of view, e.g. Stair Compliance> (optional)
Appears on Sheets:
Never appears on documentation sheets. May appear on sketch sheets.
Description:
Views created for other users (e.g. consultants) of our model file.
They would only be created upon request from a consultant, builder or client.
Purpose:
So that others linking our Revit file can use pre-made views from our file to set their own views up.
For example 3D views of each floor level for export to Navisworks and/or IFC, floor plan views set up to act as backgrounds for consultants, schedules for export, coloured plans for duplicating to use on presentations.
Contents:
Generally only major building elements without linked consultant files. MEP may require Rooms and room tags.
Applies to View Categories:
Generally floor plans and RCPs, but could be any view type.
Use view type labelled 'working' for elevations, sections and detail views (callouts).
Naming Convention:
Must start with Y_.
Lowercase. (can be sentence case, but never all uppercase)
e.g. Y_RCP Level 01
View Parameter Values:
Purpose.VW = Collaboration
Drg Series.VW = Collaboration
Appears on Sheets:
Never appears on sheets.
Description:
Views to assist managing the Revit model.
Purpose:
Views created to help keep the Revit model consistent and clean.
For example views showing; each workset; each linked consultant Revit file; schedules showing all parameters, not just documentation schedule parameters.
Also views that are exported, typically Schedules, but may include 3D views, e.g. for Navisworks issues.
NOT used for working on the project (see WORKING above).
Contents:
Anything.
Applies to View Categories:
All view categories.
Use view type labelled working for elevations, sections and detail views (callouts).
Naming Convention:
Must start with Z_.
Lowercase. (can be sentence case, but never all uppercase)
e.g. Z_Door Schedule; Z_Workset-Structure; Z_3D export-NWD
View Parameter Values:
Purpose.VW = Manage
Drg Series.VW = Manage
Appears on Sheets:
Never appears on sheets.