REVIT STANDARDS MANUAL€¦ · SEPTEMBER 2013 . REVIT STANDARDS MANUAL . Additional standards and protocols specifically for Autodesk Revit users . REVIT STANDARDS Page 1

SEPTEMBER 2013

REVIT STANDARDS MANUAL Additional standards and protocols specifically for Autodesk Revit users

REVIT STANDARDS Page 1

SEPTEMBER 2013

1. INTRODUCTION .............................................................................................................................. 4 1.1. Background .................................................................................................................................. 4 1.2. Scope ........................................................................................................................................... 4 1.3. Updates ........................................................................................................................................ 4 1.4. References ................................................................................................................................... 4 1.5. Definitions ..................................................................................................................................... 4 2. BEST PRACTICE ............................................................................................................................. 5 2.1. BIM ............................................................................................................................................... 5 2.2. Drawing Production ...................................................................................................................... 5 3. THE COMMON DATA ENVIRONMENT (CDE) ............................................................................... 6 3.1. Work in Progress (WIP)................................................................................................................ 6 3.2. Shared .......................................................................................................................................... 6 3.3. Published ...................................................................................................................................... 6 3.4. Archiving ....................................................................................................................................... 6 4. PREPARATION FOR PUBLICATION .............................................................................................. 7 4.1. Introduction ................................................................................................................................... 7 4.2. Data Security & Saving ................................................................................................................ 7 5. ROLES AND RESPONSIBILITIES .................................................................................................. 7 5.1. Introduction ................................................................................................................................... 7 5.2. Roles ............................................................................................................................................ 7 6. WORKING TOGETHER (INTEROPERABILITY) ............................................................................. 8 6.1. Introduction ................................................................................................................................... 8 6.2. Incoming CAD Data Management ............................................................................................... 8 6.3. Intended Use of Model ................................................................................................................. 8 7. DATA SEPARATION........................................................................................................................ 9 7.1. Introduction ................................................................................................................................... 9 7.2. Worksharing ................................................................................................................................. 9 7.3. Workset Division Naming ........................................................................................................... 10 7.4. Worksets not defined.................................................................................................................. 10 8. MODELING METHODOLOGY ....................................................................................................... 10 8.1. Model Development Methodology .............................................................................................. 10 8.2. Graded Component Creation ..................................................................................................... 10 8.3. Model/Draughting Detail ............................................................................................................. 11 8.4. Drawing Compilation .................................................................................................................. 11 8.5. Spatial Location & Coordination ................................................................................................. 12 8.6. Units and Measure ..................................................................................................................... 12 9. NAMING CONVENTIONS ............................................................................................................. 12 9.1. Introduction ................................................................................................................................. 12


SEPTEMBER 2013

9.2. Project Folder Structure ............................................................................................................. 12 9.3. Central Resources Folder Structure ........................................................................................... 12 9.4. Local Project Folder Structure .................................................................................................... 13 9.5. General Naming Conventions .................................................................................................... 13 9.6. Model File Naming ..................................................................................................................... 13 9.7. Division Naming ......................................................................................................................... 13 9.8. Library Object Naming................................................................................................................ 13 9.9. View Naming .............................................................................................................................. 14 9.10. View List Scheduling .............................................................................................................. 14 9.11. Browser Organisation ............................................................................................................. 15 9.12. Sheet Naming ......................................................................................................................... 15 10. PRESENTATION STYLES ........................................................................................................ 16 10.1. Introduction ............................................................................................................................. 16 10.2. Annotation .............................................................................................................................. 16 10.3. Text Assignment ..................................................................................................................... 16 10.4. Line Weights ........................................................................................................................... 16 10.5. Line Patterns .......................................................................................................................... 17 10.6. Line Styles .............................................................................................................................. 17 10.7. Hatching and Filled Regions .................................................................................................. 18 10.8. View Templates (UNDER REVIEW) ...................................................................................... 18 10.9. Dimensioning .......................................................................................................................... 18 10.10. Drawing Title Blocks ............................................................................................................... 18 10.11. Symbology .............................................................................................................................. 18 11. RESOURCES ............................................................................................................................. 19 11.1. Introduction ............................................................................................................................. 19 11.2. Software ................................................................................................................................. 19 11.3. Revit Family Libraries ............................................................................................................. 19 11.4. Keynotes ................................................................................................................................ 19 11.5. Shared Parameters ................................................................................................................ 19 12. PRINTING .................................................................................................................................. 20 12.1. Introduction ............................................................................................................................. 20 13. SOFTWARE ............................................................................................................................... 20 13.1. Introduction ............................................................................................................................. 20 14. APPENDIX A .............................................................................................................................. 21 14.1. Model Validation Checklist ..................................................................................................... 21 16. DOCUMENT REVISIONS .......................................................................................................... 22 16.1. Introduction ............................................................................................................................. 22


SEPTEMBER 2013

1. INTRODUCTION 1.1. Background This supplement manual provides specific application of the protocols for Autodesk Revit Architecture, Revit Structure and Revit MEP. This manual has been created to improve the process of design information production, management and exchange.

This manual has been based on the AEC (UK) BIM Protocol for Autodesk Revit supplementary document to the generic AEC (UK) BIM Protocol

1.2. Scope This standard is intended to support all BIM work undertaken using Autodesk Revit within Shankland Cox, unless otherwise dictated by project specific standards.

This manual builds on the procedures and protocols defined in the BIM & CAD Standards Manual and should be read in conjunction with that document.

1.3. Updates The BIM/CAD Standards Manual shall be regularly reviewed and updated as necessary to ensure that the required level of effectiveness is maintained. Individual staff members are encouraged to provide suggestions for the improvement of the standard but should adhere to the outlined procedures until such time changes are implemented.

Revisions to the BIM/CAD Standards Manual are carried out to reflect current methods and controls and will result in a revision of the standards manual.

1.4. References This standard is written with references to the following documents:

• BS1192:2007 • AEC (UK) BIM Standard for Autodesk Revit • AED (UK) CAD Standards for Layer Naming V3

1.5. Definitions The follow terms are common concepts used in Revit and this manual

BIM Building Information Modelling (BIM): the creation and use of coordinated, internally consistent, computable information about a project.

Component A component is an individual element such as a door, window, wall column etc. Components are typically inserted and moved and/or rotated into a position.

Assembly An Assembly is a collection of components and/or modelled elements to define part or all of a building model.

WIP Work in Progress; this is information that has not been approved or verified to share.

Shared Information that has been checked and approved to share with outside sources

Published Published information refers to documents and other printed data. These will include but not be limited to exported data, contract drawings, reports and specifications

Views A generated graphical display e.g. plan, section, elevation or other view


SEPTEMBER 2013

2. BEST PRACTICE To achieve a successful outcome to a project, it is essential that BIM working and data and drawing output is carefully planned. Attention to management, display and quality of data is important. The following best practice principles will aid in achieving that goal.

2.1. BIM • A project BIM Plan shall be put in place that identifies key project tasks, outputs and model

configuration. • Develop clear guidelines for internal and external collaborative working. • Sub divide models between disciplines to avoid large file sizes • Clearly understand what is to be modelled and to what level of detail. DO NOT OVER

MODEL

2.2. Drawing Production Where drawings are a product of the BIM, traditional drawing conventions still apply.

• A drawing shall contain design information solely for the purpose of the intended use of the drawing. Examples of drawings and the minimum required information can be found on the server at P:\00-Resources\SCL-Help Desk.

• A policy of minimum detailing without compromising quality and integrity shall be adopted,

avoid duplication of views and/or repetition of details.

This standard follows the AEC (UK) BIM Standard of Autodesk Revit and is aligned with BS1192:2007. Shankland Cox has adopted the Common Data Environment approach that allows information to be communicated, used and shared between project team members. There are five phases to CDE as shown below;

04 ARCHIVE

03 PUBLSHED

02 SHARED

01 WIP

05 INCOMING


SEPTEMBER 2013

3. THE COMMON DATA ENVIRONMENT (CDE) This approach allows information to be shared between all members of the project team.

3.1. Work in Progress (WIP) Drawings described as Work in Progress is that which is currently being produced in-house and has not been verified for outside use with consultants etc.

These drawings shall be stored in and worked in the Drawing/WIP/A/BIM_Models section of the filing structure. These can be drafts, developed concepts, minor versions and will be active in each phase until such time you are instructed otherwise.

Exported data and 2d electronic drawings produced from the BIM shall be stored in the respective Drawing/WIP/A/Export_Data or Drawing/WIP/A/CAD_data areas.

3.2. Shared This section is to facilitate coordination of each party in exchanging of data for the project team. It shall be used to hold information which has been approved for sharing with other organizations to use as reference material for their own design development

Only BIM data or files that have been checked and approved shall be transferred to the Shared Area. The checks shall include but not be limited to;

• Model stability • Technical content check • Approval by the team manager

Sharing of models shall be carried out on a regular basis to ensure all disciplines are working on the latest version and should be issued with all necessary references and linked files. All data shall be communicated to the team through traditional drawing issues, change registers or other forms of communication such as email or Dropbox

3.3. Published Published documentation includes Project Outputs required at defined project stages, discrete deliverables including planning and regulatory submissions together with issues for construction. The Published section shall be used to hold all published information.

A record of all issued deliverable shall be maintained in both softcopy and hardcopy.

When working with BIM, information that changes in one view may affect other views. As such a BIM model shall be treated as WIP until such time as it leaves the BIM environment in a non-editable state.

3.4. Archiving Archiving of all approved output data from the BIM shall be stored in the Archive section of the project folder, including published, superseded and ‘As Built’ drawings and data.

Additionally, at key stages of the design process, a complete version of the model, exported data and associated drawing deliverables should be copied into an archive location.

Archived data shall reside in logical folder repositories that clearly identify the archive status e.g. 09-12-11 Stage D Design.


SEPTEMBER 2013

4. PREPARATION FOR PUBLICATION 4.1. Introduction Prior to transmitting of the Revit model, the contents and structure need to be agreed. Sheets from the BIM shall be published to PDF (preferred), DWF or other non-editable format, where they can be checked, approved, issued and archived as traditional documents.

APPENDIX A provides a validation Checklist as a guide for preparing the model for issue to outside sources.

• At a minimum the validated model should not contain any unnecessary views or sheets, • The model has been audited, purged and compressed • Model files are up to date • Any linked reference files have been removed

4.2. Data Security & Saving • All BIM projects shall reside on the network server P:/ never on local drives. • A maximum number of Revit backups shall be 3 per person working on the model (if 3 people are

working on the model with work-sharing then the it should be set to 9) • Revit save reminder interval shall be set to 30 min • Revit LOCAL files should be saved back to the CENTRAL file hourly

5. ROLES AND RESPONSIBILITIES 5.1. Introduction This section describes the roles and responsibilities of the different team members involved in Revit projects. The makeup of a traditional CAD project team is governed by the huge effort required to produce a construction document set, with roles corresponding to drawing types: plans, elevations, sections, details, etc. Revit Architecture significantly reduces the documentation effort - thus rendering this traditional project structure obsolete. Instead, a Revit Architecture BIM team should be organized around functions such as project management, content creation, building design, and documentation. 5.2. Roles BIM COORDINATOR

A BIM Coordinator is responsible for the following

• Management of other BIM users • Coordinate any BIM related issues • Audit all BIM content • Run clash detection • Project setup and management

BIM MODELLER

A BIM Modeller is responsible for the following

• Project Specific content creation • Creating Renders. 3d Views and walkthroughs • Export the model for inter-disciplinary use

BIM USER

A BIM User is responsible for the following

• Day to day work


SEPTEMBER 2013

6. WORKING TOGETHER (INTEROPERABILITY) 6.1. Introduction Interoperability (the ability to work together) between software products is of utmost importance for successful BIM working. Whether it is output to 2D CAD for later drawing production or output for 3D visualisation or analysis, the preparation and methods adopted to compose the BIM will eventually determine its successful application within other software packages.

6.2. Incoming CAD Data Management All ‘Incoming’ CAD/BIM data shall be received and logged by the Document Controller according to the company’s management procedures. A copy of the incoming data shall be stored in its original format within the ‘Incoming’ folder. Once the data has been verified the Document Controller will make this data available for the project team within the ‘Shared’ area.

6.3. Intended Use of Model Modelling shall be carried out to the level of detail required to produce and deliver to the client’s requirements. BIM data should only be provided for the agreed and confirmed purposes and should be clarified at the beginning of the project, including;

• Information and design development • Drawing production • Data Export • Clash detection


SEPTEMBER 2013

7. DATA SEPARATION 7.1. Introduction This section deals with the principles of subdividing a model for the purpose of;

• Multi-user access • Efficiency on large projects • Collaboration with other disciplines

The following procedures shall be followed

The methods for data separation shall be agreed by all involved in the modelling

• Models shall initially be created as an isolated, single user file. As the model becomes larger or additional members are introduced the model will be sub-divided

• There should be no more than one building model in a single file • A model should contain data from one discipline • Where multiple models make up a single project, an overall model or Project Information Model

(PIM) should be considered where the various models link together for coordination/clash detection

• A Site Model (SM) should be created for each Revit Project. This file holds the project coordinate system and controls the location, rotation and elevation of all Revit-based Models

7.2. Worksharing Worksets allow multiple users to simultaneously work on a model through the use of a CENTRAL file and synchronized LOCAL copies. When you turn on the Worksharing on in a project, use the SAVEAS command to save the central file and suffix _CENTRAL to the end of the file name.

Once a file is worksetted, you should always work in your local copy and not the central file. To make a local file;

• Select Open Project and browse to the CENTRAL file. Do not open the Central file from Windows Explorer

• On the dialogue box ensure ‘Make Local File’ is checked • Once open from the File menu, select SAVEAS • Browse to the project sub folder in your C:\_BIM_Projects Folder • Delete the _CENTRAL suffix from the file name and append your _”YourName”_LOCAL.RVT and

select save

All local files should be saved to a job folder under C:\Projects with your name appended to the end. i.e. C:\BIM_Projects\50021\50021_Your Name_LOCAL.rvt

Always use the SAVEAS command when changing the project folder location or filename.

To improve hardware performance, open only the required Worksets

At no point after creating the CENTRAL file shall it be opened or edited directly. All required operations can be, and therefore shall be, performed via the LOCAL files.


SEPTEMBER 2013

7.3. Workset Division Naming A project shall be broken into a sufficient number of Worksets to avoid break down in workflow. The model shall be split into the Worksets described in Table 1

Table 1

Workset Name Description Ceilings Ceilings and attached components Exterior Shell Exterior walls, door and windows Interior Partitions Interior walls, door and windows Furniture Furniture and equipment Flooring Non-structural floor slabs and flooring finishes Roof Roof slabs and attached components Circulation Stairs, ramps and landings, Lifts and escalators Structure Structural slabs and columns MEP Mechanical, Electrical and Plumbing components

Larger projects can be divided horizontally or vertically into zones/levels as needed and should be identified in the Workset name

7.4. Worksets not defined Some elements do not require defined workset definitions due to the standard allocation of Revit

• Grids These are included in the Shared Levels and Grids workset • Areas These are view specific and don’t require a workset • Annotation These are view specific and don’t require a workset

8. MODELING METHODOLOGY This section defines the methodologies for Revit modelling that enables efficient and rapid model creation.

8.1. Model Development Methodology A Model Development Methodology shall be used to develop projects in early stages as it enables fast model development and allows for large models to be created with low hardware requirements.

During conceptual design simple “place holder” components shall be used

As the design develops and the design requires precise materials and/or components these concept objects can be swapped out for higher more specific “place holders”

An exception would be for MEP system components or known structural components

8.2. Graded Component Creation As per the Model Development Methodology, all components created or otherwise obtained shall be graded, named and stored in the Shankland Cox Revit library (P:\Resources\Standards\Revit 2013).

The graphical appearance should be categorised as follows

• Grade 1 (G1) – Concept (1:200, 1:500) • Grade 2 (G2) – Schematic/Detailed Design (1:50, 1:100) • Grade 3 (G3) – Render Quality (Only used for visualization)


SEPTEMBER 2013

Adherence to the above grading categorization may result in multiple versions of the same component at differing grades. This is accommodated in the naming protocols defined in NAMING CONVENTIONS.

NOTE: When in doubt, users should opt for less 3D rather than more

8.3. Model/Draughting Detail Consideration shall be given to the maximum level of detail to be modelled. Too little and the information will not be suitable for its use, too much and the model may become unmanageable.

Intelligent 2D line work and detail components shall be utilized to enhance the required model views.

3D modelling should be carried out to an accuracy of 1:50 scale

8.4. Drawing Compilation When CAD data is linked into a project, the user must ensure that the latest version is being used and is located in the appropriate project folder. In house files should be located in 01WIP>CAD_Data and all outside sourced files will be linked from 02 Shared.

It is preferred that all fully assembled drawing sheets be compiled within the Revit environment. Exporting data in order to ‘finish off’ in CAD negates the advantages of the Revit data coordination purposes and should be avoided at all costs


SEPTEMBER 2013

8.5. Spatial Location & Coordination All Revit projects shall:

• Use real world co-ordinate systems • Be produced to true height above project datum • Use the Project Shared Coordinate system across all BIM files

CAD files that use real world co-ordinates where the data is more than 1km from 0,0,0 need to be modified prior to import into Revit and shifted to be as close to 0,0,0 as possible. Real world coordinates are then re-established in the Revit model. Data exported from Revit can then be either real-world or local.

8.6. Units and Measure • Default units for design shall be millimetres with two decimal places • Dimension styles have been created within the template and must not be altered • Switching between imperial / Metric units shall be avoided where possible • CAD data shall be scaled to the appropriate units prior to linking into Revit

9. NAMING CONVENTIONS 9.1. Introduction This section defines the storage of Revit files within the project filing system along with the naming conventions associated with Revit

9.2. Project Folder Structure All project data shall be held within the standard SCL folder structure located on the Projects (P:/) or Bids (T:/) server location and according to the BIM & CAD Standards Manual under Drawings>01 WIP>BIM_Models

During Worksharing ‘local’ files should be located as described in 7.2 Worksharing

9.3. Central Resources Folder Structure Standard templates, drawing borders and user created families are held within the server based Resource Library and is arranged by software version

All locations for the storage of Family components shall use the standard Revit family categories

Projects (\\SCLSERVER-02) (P:)

Resources

Standards – User Created Families

Templates – SCL rvt files

Title blocks – SCL Title blocks


SEPTEMBER 2013

9.4. Local Project Folder Structure Local copies of central project models do not need to be backed up on the server as changes are regularly synchronized with the central model. They can be stored on the user’s local hard drive –not in My Documents – according to the following folder structure

9.5. General Naming Conventions Refer to BIM & CAD Standards Manual Section 9.3

9.6. Model File Naming Refer to BIM & CAD Standards Manual Section 10.1

9.7. Division Naming Refer to Table 1

9.8. Library Object Naming Library Object Naming provides and unified approach to identify objects within the Shankland Cox resource library.

Each field should be separated by a hyphen “-“.

Field 1: Manufacturers name (Optional)

Field 2: Description – A description of the content based on the Uniclass system eg. ExternalFinishCladdingConcrete

Field 3: Size/Manufacturer Code (Optional) – Used to specify dimensions or the manufacturers code

Field 4: Grade/Level of Detail – Specifies the intended graphical scale and detail of the object

Name Description Dorma-ExteriorSteelDoor-2400x1000-G3 Exterior Steel door made by Dorma, 2400x1000,

fully detailed ExteriorAluminiumWindow-3x600x1000 Third floor enlarged plan of lift No. 1 FurnitureLounge3Seater-G0 North elevation Armstrong-GypsumPanelCeiling-600x600-G2 Level 2 reflected ceiling plan

C:\Users\jeremy\Documents\Project_BIM Files

<Project Name>

1

Manufacturer (Optional)

2

Description

3

Size/Code

4

Grade/Level of Detail


SEPTEMBER 2013

9.9. View Naming This section is limited to draughting views and sheet views only.

View naming shall be consistent across all references to that view. Renaming of views shall be carried out with care as this will be reflected across all documentation.

Field 1: Level (Optional) - A description of the level or location

Field 2: Content – A description of the content and/or purpose of the view

Name Description 01-Plan First floor plan 03-EnlargedPlanLift1 Third floor enlarged plan of lift No. 1 North Elevation North elevation 02-Ceilingplan Level 2 reflected ceiling plan

The Revit functionality that allows for the Title on Sheet to be different to the view name should be avoided if possible.

Level names should be spelled out as they need to appear in a room schedule (as well as sections and elevations) Do not pad the level number with leading zeros.

Views shall not be named in order to make them sort more logically (i.e. the prefixing of names with sequential numbers) the grouping and filtering settings take care of that.

View names shall be written in UPPERCASE.

9.10. View List Scheduling There are 3 pre-defined schedules included in the template to manage views. They are Category View List, Publication View List and WIP View List as shown below. These are created in order to aid navigation

Category View List View Name Type Family View Category View Sub Category View Template Scale 1:

Publication View List View Name Title on Sheet Scale Value 1: Sheet Number Sheet Name

1

Level (Optional)

2

Content


SEPTEMBER 2013

WIP View List View Name Scale Value 1: Detail Level

9.11. Browser Organisation The Project Browser in Revit provides an organisational structure to the views and components within the BIM environment. The following rules are defined in the template to automatically sort as needed to aid navigation.

WIP and Published

View folders are grouped by View Category and then by View Sub Category and sorted by Family in Ascending order

The views are filtered by Sheet Name which should Equal to a value of None. View Section will now show only views not allocated to a drawing sheet

Sheet folders are grouped by Sheet Number using 1 Leader Character and sorted by Sheet Number in Ascending order

Drawing Type

View folders are grouped by Family and Type and then by Drawing Type and sorted by View Name in Ascending order.

9.12. Sheet Naming Sheet naming is based on the document and drawing numbering protocols outlined in the Shankland Cox BIM & CAD Standards Manual


SEPTEMBER 2013

10. PRESENTATION STYLES

10.1. Introduction This section defines the company standards to ensure the plotted appearance of drawing output from Revit is consistent and of the highest quality according to the Shankland Cox BIM & CAD Standards Manual

10.2. Annotation Where no pre-defined text exists, the Text Style shall be ARIAL.

• Annotation shall be legible, clear and concise • An opaque background should be considered as an aid to clarity • Text shall remain legible when drawings are plotted at reduced size • Leaders should be straight or 90° (not angled or curved)

10.3. Text Assignment All text shall be restricted to the following standard sizes:

Text Height (Plotted full size) Usage Test Style Name A3 Sheets

1.8mm General text, dimensions & notes General Text-A3 2.5mm Sub-headings Sub Headings-A3

A1 Sheets 2.5 General text, dimensions & notes General Text-A1 3.5 Sub-headings Sub Headings-A1 5.0 Normal titles, Drawing numbers Normal Titles-A1 7.0 Major text and titles Major Titles-A1

10.4. Line Weights There are 16 model line weights and each is given a plotted thickness across the range of drawing scales as defined below. It is recommended that Thin Lines (TL) mode not be used as this may promote over-modelling and over detailing.

Pen 1:2 1:5 1:10 1:20 1:50 1:100 1:200 1:500 Perspective Annotation 1 0.25 0.25 0.18 0.18 0.18 0.13 0.10 0.10 0.13 0.13 2 0.35 0.35 0.25 0.25 0.25 0.18 0.10 0.10 0.15 0.25 3 0.50 0.50 0.35 0.35 0.36 0.25 0.18 0.10 0.18 0.35 4 0.70 0.70 0.50 0.40 0.40 0.35 0.25 0.18 0.25 0.50 5 1.00 1.00 0.70 0.50 0.50 0.40 0.35 0.25 0.35 0.70 6 1.40 1.40 1.00 0.70 0.70 0.50 0.40 0.35 0.50 1.00 7 2.00 2.00 1.40 1.00 1.00 0.70 0.50 0.40 0.70 1.40 8 2.80 2.80 2.00 1.40 1.40 1.00 0.70 0.50 1.00 2.00 9 4.00 4.00 2.80 2.00 2.00 1.40 1.00 0.70 1.40 2.80 10 5.00 5.00 4.00 2.80 2.80 2.00 1.40 1.00 2.00 4.00 11 6.00 6.00 5.00 4.00 4.00 2.80 2.00 1.40 2.80 5.00 12 7.00 7.00 6.00 5.00 5.00 4.00 2.80 2.00 4.00 6.00 13 8.00 8.00 7.00 6.00 6.00 5.00 4.00 2.80 5.00 7.00 14 9.00 9.00 8.00 7.00 7.00 6.00 5.00 4.00 6.00 8.00 15 9.00 9.00 9.00 8.00 8.00 7.00 6.00 5.00 7.00 9.00 16 9.00 9.00 9.00 9.00 9.00 8.00 7.00 6.00 8.00 10.00

Shaded values indicate the common line weights and Pen No. used in documentation.


SEPTEMBER 2013

10.5. Line Patterns The supplied template contains 23 defined Line Patterns for use in all draughting production work. These Line Patterns are defined below and any additional Line Patterns shall be created by the BIM Manager or Coordinator.

10.6. Line Styles The supplied template contains 21 defined Line Styles for use in all draughting production work. These Line Styles are defined below and any additional Line Styles shall be created by the BIM Manager or Coordinator.


SEPTEMBER 2013

10.7. Hatching and Filled Regions Default Fill patterns for model and draughting are loaded in to the template and should be used and any alternative Fill Pattern shall be used after approval of the BIM Manager or Coordinator.

There are 36 Model Fill Patterns and 32 Drafting Fill Patterns available for use.

10.8. View Templates (UNDER REVIEW) The default template SCL_Architectural contains a number of pre-defined View Templates and associated View Filters as described below. View Templates should be used to maintain consistency across published drawings. Adjustments to the settings must be carried out only with the agreement of the BIM Manager or Coordinator.

Name Description SCL_General Layout Plan General arrangement layout at 1:100; medium detail SCL_Setting Out Plan Dimension setting out plans at 1:100; medium detail SCL_Fire Plan Fire plans for Civil Defence at 1:100; medium detail SCL_Site Plan Site set out and coordination plans at 1:250; coarse detail SCL_Presentation Layout Shaded layout plan with shadows SCL_Exterior Elevation Exterior elevations at 1:100; medium detail SCL_Interior Elevation Enlarged interior elevations at 1:20; fine detail SCL_ Cross Section Cross sections at 1:50; medium detail SCL_Presentation Elevation Shaded elevations with colour and shadow at 1:100; medium detail SCL_Site Section Cross section through site at 1:250; coarse detail SCL_3D Presentation Shaded elevations with colour and shadow SCL_Reflected Ceiling Plan Reflected ceiling plans @ 1:100; medium detail SCL_Detailing View Detailing view at 1:10; fine detail

10.9. Dimensioning Refer to Section 12.4 – Dimensioning of the BIM & CAD Standards Manual

In general there is one dimension style (2.5mm Arial) for each type of dimension and these are defined in the template.

10.10. Drawing Title Blocks Shankland Cox company title blocks are available from the title blocks folder on the Projects (P:\) location. Any client specific or Project specific title blocks will also be located from this location.

10.11. Symbology Standard symbols such as north point, section and elevation references and window, door tags are available within the template file and follow the Shankland Cox Drawing Symbols in Section 17of the BIM & CAD Standards Manual

• All Sections shall be numerically labelled • All Details shall be alphabetically labelled • Where practical sections should be listed from left to right and from top to bottom


SEPTEMBER 2013

11. RESOURCES

11.1. Introduction To increase efficiency of BIM working all resources and content shall be shared across the practice

11.2. Software Refer to BIM & CAD Standards Manual

11.3. Revit Family Libraries Revit default family libraries are available on each user’s local library location and are read-only. Any modifications shall be copied to the company resources library before utilising. When content is updated for use in a newer Revit version the updated version of the content shall be created in the appropriate location for that version. This avoids ‘forwards incompatibility’.

For user created families locations refer to 9.3 Central Resources Folder Structure.

If you cannot find a particular component in the Revit Family Library or Central Resources Library you can browse for components on the Revit City website www.revitcity.com

Username: sclauh Password: sclauh

11.4. Keynotes A default Shankland Cox Keynote file (SCX Keynote.txt) is included in P:\Resources\Standards\Revit 2013.

This file shall be copied to the projects WIP> Families_ Blocks folder for each new project and modified to suit the specific requirements of the project.

A third party application called Keynote Manager is available to aid in the creation of keynotes and is to be used exclusively by the BIM Manager or Co-ordinator.

11.5. Shared Parameters The company Shared Parameter file (SCL Shared Parameters.txt) is held in P:\Resources\Standards\Revit 2013. This is maintained by the BIM Manager

If project specific families require shared definitions a separate file shall be created in the WIP> Families_ Blocks folder. Once this has been assessed and approved the BIM Manager will append the central Shared Parameters file.


http://www.revitcity.com/

SEPTEMBER 2013

12. PRINTING

12.1. Introduction Shankland Cox has the ability to print in A0, A1, A2, A3 & A4. Shankland Cox currently has 2 printers available for plotting of documents.

• HP Design jet T1100ps • Sharp MX-3114N PCL6

Always ensure the ‘ZOOM’ box is ticked and the scale is set correctly (e.g. 100%, 50%) and Paper Placement is set to Centre. Never print ‘Fit to Page’

It is recommended to use the printer setups defined in the template for consistency of documentation output.

13. SOFTWARE

13.1. Introduction The production of computer generated drawings undertaken by Shankland Cox is predominately produced in AutoCAD 2013 & 2014, Revit 2013 & 2104 and 3S Max 2013 & 2014. These are all stand-alone packages.

It is discouraged to load on software or modify software without the approval of the BIM CAD Manager. Shankland Cox is making every effort to remove illegal software and replace with legitimate versions of CAD or BIM software.

If at any time updates or patches or third party software is required, it is individual staff member’s responsibility to inform the BIM/CAD Manager of the requirements or errors incurred. The BIM/CAD Manager will perform necessary audits, fixes and updates as required.

Shankland Cox has adopted Autodesk Revit as it’s standard BIM software. The Autodesk Revit Products currently in use are:

• Autodesk Revit Architecture • Autodesk Revit MEP • Autodesk Revit Structure

In addition to the Revit based applications, Shankland Cox has adopted, as well, the following applications to assist in BIM:

• Autodesk NavisWorks • Autodesk SketchBook Designer • Autodesk 3D Max Design


SEPTEMBER 2013

14. APPENDIX A

14.1. Model Validation Checklist Model Preparation provides a guide for preparing the model prior to validating

Model Preparation Does the model file name conform to Standards Have all users “Saved to Central” and relinquished all editing rights Have all warning messages been reviewed and fixed Do the families conform to standard naming conventions Lines Styles Worksets Phasing and/or Design Options Modelled accurately

Model Validation provides a guide for ensuring the model is ready for issue

Model Validation Open Central file with “Detach from Central” and “Audit” selected Remove linked in files not for transmitting Remove all non-required Views/Legends/Sheets/Images Remove unwanted Design Options Purge model Update “Save to Central View” Save file to Shared folder dated and given a description


SEPTEMBER 2013

16. DOCUMENT REVISIONS

16.1. Introduction All revisions shall be recorded within the table below. A revision number shall be assigned to the document with date of revision and a small description of what was revised. The revision shall be digitally signed by the editor or CAD Manager accordingly.

The issuance of each CAD Standards Manual shall be recorded on the BIM & CAD Standards Register located at M:\Administration\Section 11 HR Documents\CAD Standards Manual\BIM & CAD Standards Register.docx

Rev No. Date Description Revised By 07/10/2013 1st Edition JR
