BIM Execution Plan for SPHproof2rtf
.rtf
School
ESOFT Regional Campus - Galle Branch**We aren't endorsed by this school
Course
COMPUTER BTEC
Subject
Information Systems
Date
Dec 20, 2024
Pages
26
Uploaded by AgentDiscovery19000
Job number: Project name: BIM execution planDate: Revision: [] []Prepared by: [Name][Job function]Small Projects HandbookPage 1
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]As a minimum this document should be reviewed by the project team at the end of each work stage and re-issued if necessary. If there are any changes to the agreed protocols for the project at any other stage of the design process, these should be reflected in this document and again it should be re-issued if necessary.Revision No.Author Role Date of Issue Strategic Definition, Preparation & Brief (RIBA Stages 0-1)Concept Design (RIBA Stage 2)Developed Design (RIBA Stage 3)Technical Design (RIBA Stage 4) Construction (RIBA Stage 5)Handover & Closeout (RIBA Stage 6)In Use (RIBA Stage 7)Small Projects HandbookPage 2
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]PART 0 - INTRODUCTIONThis document forms part of [Practice name] BIM protocols. It should be completed by the Project Architect and the Information Manager before the creation of any BIM data relating to the project is produced.This document should be read in conjunction with the BIMsection of the practice CAD manual which defines the BIM standards to be used across all projects. The BIM Execution Plan should be used as a reference source for all members of [Practice name] project team and should clearly state and explain any deviations from agreed practice standards. It should also clearly explain the project specific protocols, data exchange strategy, expected level of detail, etc. that has been agreed for this project.The use of BIM will be implemented to varying extents across different projects and this plan outlines exactly how BIM principles should be applied to this project and at which workstage they should be used. The project team should aim to implement BIM at the level needed to maximise value while minimising the cost and impact of the modelling implementation. This requires the team to selectively identify appropriate areas for BIM implementation and plan these in detail. This plan should be reviewed at regular intervals by the Project Architect and the Information Manager to ensure that it always remains consistent with agreed principles for the project and a valid reference for team members.Before commencing work, key members of the project team should also discuss the strategy for building the model itself and record in this document which template (if any) is to be used, which worksets will initially be created and how the model will be broken down into smaller segments to allow for more efficient modelling and smaller file sizes.This BIM Project Execution Plan should be referred to in all appointment agreements related to the project and where any conflicts exist between the requirements of this document and any other agreement, then the requirements of this document shall take precedence.Small Projects HandbookPage 3
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]PART 1 - THE PROJECT1.1Project SummaryEnter a brief outline description of the project background, location, client, history1.2Project CharacteristicsGive a brief description about the nature of the project, number of buildings, size, any particular challenges that relate specifically to the projectSmall Projects HandbookPage 4
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]1.3Primary Project BIM ContactsThis page is to be reviewed and updated at each job stage as a minimumName Primary BIM ContactRole Email Address Contact No. Client Architect Information Manager Structural Engineer Mechanical Engineer Offsite Construction Consultants Principal Contractor Cost Consultant Other Small Projects HandbookPage 5
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]1.4Project BIM StandardsThis project is to be modelled based upon the following standards and protocols. Please note that this is not an exhaustive list and does not include standards that the actual building should comply with, for example the Building Regulations. Where there is a conflict between named standards [Practice name] CAD standards take precedence unless outlined in Section 1.5 of this Execution Plan.[practice name] CAD StandardsAEC BIM Standards[other]List all appropriate [Practice name] or generic industry standards that are to be applied1.5Deviations from established BIM StandardsPlease outline here anything that affects or overrides the established [Practice name] CAD & BIM ProtocolsIn some situations an agreement may be reached where client standards are only partially applied, please also outline in this section any additional agreements made as to the extent of use of client standards.Small Projects HandbookPage 6
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]PART 2 – PROJECT AIMS2.1Project BIM GoalsDefine any specific objectives of the use of BIM for this project, from simply aiming to achieve a fully-coordinated design to minimise errors andre-working to aiming to use a Design for Manufacture & Assembly Process (DFMA) or extending the use of BIM to the post-occupancy stage for use in Facilities Management (FM) operations.2.2Project BIM UsesThe table below contains typical uses for BIM within projects, please add or delete items as appropriate. Please refer to Appendix1 of ‘Preparing a BIM Execution Plan’ for a more comprehensive list of suggested BIM uses. Replace text for agreed uses.Work StageRIBA Stage 1RIBA Stage 2RIBA Stage 3RIBA Stage 4RIBA Stage 5RIBA Stage 6RIBA Stage 7Relevant 'Data Drop'Preparation &BriefConceptDesignDetailed DesignTechnicalDesignConstructionHandover &Close OutIn UseBIM UsesModel existing siteDesign modellingConstruction detailsAs-built modelBuildingmaintenanceConceptmodellingCost estimationSchedulingDigital fabricationCost estimationStructural DesignCost estimationPhase PlanningMechanical DesignClash detectionSmall Projects HandbookPage 7
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]PART 3 – PROJECT DELIVERABLES FORMATEnter full name and file path of the agreed list of deliverables for the project in the box below, any referenced documents should be added to this document as an appendix when printed or exported to PDF format.Deliverables list location: 3.1DrawingsWhat is the primary form of delivery for drawings listed on the agreed list of deliverables?Please tick as appropriateHard copy PDF DWF Other3.2CAD InformationDoes the client require drawings to be also issued in a CAD format as part of the agreed deliverables? NOTE: this does not include CAD information exchanged with other consultants as part of the collaborative working process.DWG Other3.3BIM InformationComplete this section if the building model is to be issued to the client as an agreed deliverable? Small Projects HandbookPage 8
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]RVT 3D DWF Navisworks 3.4 Use of BIM InformationIf the building model is to be issued as a deliverable in its own right, state below the key target dates for when it will be issued. The key BIM uses outlined in2.2should be considered when creating the model with regard to the amount and type of information that should be included. Please state below key dates/milestones at which the model is to be issued as a deliverable:Project Stage/Data DropModel Issued asDeliverable?Date for IssueDefinition & Brief (Stages 0-1)Non/aConcept Design (Stage 2)yes noDeveloped Design (Stage 3)yes noTechnical Design (Stage 4)yes noConstruction (Stage 5)yes noHandover & Close Out (Stage 6)yes noIn Use (FM) (Stage 7)yes noAre the component parts of the model prepared by each consultant to be issued individually by each party or is the responsibility of a model manager to issue a combined/complete model? Please state the details of how the model is to be issued below.Small Projects HandbookPage 9
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]PART 4 - DATA EXCHANGE STRATEGY4.1Primary Software Use and Exchange FormatPrimary Software PackageSoftware NameVersionExchange FormatsSecondary Software UsedArchitectStructural EngineerMechanical EngineerElectrical EngineerPlumbing EngineerLandscape ArchitectSmall Projects HandbookPage 10
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]Civil EngineerOther consultantSmall Projects HandbookPage 11
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]4.2Data Exchange MethodOutline in this section how information is to be shared between all parties working together on this project. If information is to be shared ‘live’ through an extranet or cloud environment please outline who is hosting the model, requirements for accessing the data, login details, etc.If data exchange is to be based on the issuing of the building model at regular intervals please provide details of where it is to be uploaded to, login details, any specific instructions, etc. Please also state whether the model is to be issued on a regular basis, i.e. every Friday or if it is to be issued on agreed dates for example at the end of each workstage. PART 5 – COLLABORATION5.1 Collaboration StrategyTo avoid confusion and disputes later in the project, responsibility of each element of the project should be assigned to a specific consultant in the responsibility Matrix which should be attached to this document as an appendix for reference.In addition to this, outline below how the collaboration is to be carried out. For example if live cloud working is to be utilised, please outline whatthe appropriate communication channels will be and how the process involving several consultants working together in one live model will work.Small Projects HandbookPage 12
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]If collaboration is to be managed through a series of meetings or regular telephone calls, etc. please also outline how the process will work. Please outline in the following Section 5.2 any agreed key dates in the collaboration process such as coordination meetings, clash-detection sessions, etc. 5.2Collaboration ActivitiesPlease state all agreed collaboration activities here, including dates and required attendees.Small Projects HandbookPage 13
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]5.3Responsibility for model managementPrior to the commencement of any modelling for the project, it should be agreed who has responsibility for the management of the building model at each project phase. This management of the model may change throughout the project as different stages are reached. While it is quite common that we will be managing the building model in a role as lead consultant, depending on the project this responsibility may equally lie with the client or principal contractor. The general duties relating to this management role are outlined below and will usually be carried out by the managing party’s nominated BIM Coordinator. The BIM Coordinator will be responsible for the following:Manage access rightsCollect and log incoming modelsCheck that received models are complete, usable and comply with the protocolsSmall Projects HandbookPage 14
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]Maintain a record copy of each received modelAggregate models and enable viewing by the other relevant partiesPerform clash detection in accordance with the protocols and issue Clash Detection Reports at the defined intervalsMaintain model archives and backups.Where any party identifies conflicts in the Model, during any phase of the project, they should promptly inform the Model Element Author. The Model Element Author should then act promptly to mitigate the conflict. Project Stage/Data DropManaging partyBIM coordinatorDefinition & Brief (Stages 0-1)Concept Design (Stage 2)Developed Design (Stage 3)Technical Design (Stage 4)Construction (Stage 5)Handover & Close Out (Stage 6)Facilities Management (Stage 7)Model Ownership: It is confirmed that Model Element Authors do not convey any ownership right in the Model Element or in the software used to generate the content. Unless specifically agreed elsewhere, the right of any subsequent Model Element Author or Model User to use, modify or further distribute any Model is limited to the design and construction of the project, and nothing here conveys any right to use the Model for any other purpose.PART 6 – FILE NAMING & MODEL SUBDIVISIONSSmall Projects HandbookPage 15
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]6.1File Naming ConventionFile naming should be carried out as outlined in [Practice name] CAD Standards. These standards are based upon the industry standard AEC CAD & BIM Guidelines and PAS1192. The files should be named to the following convention:Field 1Field 2Field 3Field 4Field 5Field 6Field 7ProjectOriginator CodeZone/ SystemLevelTypeRoleDescription requiredRequiredreq’dreq’dreq’dreq’drequiredXXXXXXXXXXXXXXXXText definition6 digits3 digits2-3 digits2 digits2 digits1 digitn/aField 1: Project No. Originators unique project number/code to be used. Where possible a shared project number should be agreed and certain clients may supply the project number to be used on all files.Field 2: Originator Code. 3 letter code to represent the originator.Field 3: Zone/System. Appropriate for separate buildings/systems on large projects or phased projects. On a simple project use XXNon Specific. On more complex projects use a 2/3 digit code that refers to a specific area or building within a proposed site i.e. BD5 for Building 5.Field 4: Building Level. For a multi-storey model this will generally be XX, however if any models are level-specific, this should be reflected in the file name i.e. GF or 25 depending on the convention for naming floors within a project.Field 5: Type. Depending on information exported from the model or created to be imported into it (for example 2D CAD drawings), the following codes may be used: DRDrawing, M22D Model, MRModel rendering, VSVisualisation, STSchedule/Table, SPSpecification, BQBill of Quantity.Field 6: Role. AArchitect, CCivil Engineer, EElectrical Engineer, KClient, MMech Eng, PPublic Health Eng, QQuantity Surveyor, SStructural Eng.Field 7: Description. Model Name or drawing sequential number.Small Projects HandbookPage 16
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]6.2Model PhasesFor projects where a single building model is to be split into development phases, please outline the phase order and titles to be used in the model in the table below.Phase No.Phase Title1Existing2New Construction34…6.3Model Break UpFor ease of use, model files should not typically be allowed to exceed 100mb. For projects for files likely to exceed this value, please outline below a proposed strategy for splitting the model into smaller component parts.Outline description of the strategy for model break-upSmall Projects HandbookPage 17
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]6.4Model File NamesGive details of model files that will be created to form the complete building model for the project and add to this register any new models that are created.Model descriptionLocal Project No.Originator codeZoneLevelTypeRoleDescriptionComments 6.5Project DatumAn agreed reference point should be agreed by all parties so that all information can be easily referenced and linked when required. A shared Levels and Grids file should be created in Revit with the Project Datum clearly marked and the file should be distributed to all parties to make collaborative work much easier. Details of the Project Datum should also be stated in the table below.Small Projects HandbookPage 18
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]6.6Shared WorksetsTo allow for ease of graphic control, all members of the project team should agree a list of standard worksets to be used by all consultants. These should be stated in the table below and reviewed and updated as necessary.6.7Naming SheetsAs with the file names, drawing sheets should be name to AEC/BS1192 standards and these again are reflected in [Practice name] CAD standards. Any deviation from these naming standards should be noted in Section 1.5 above and outlined in detail in the box at the end of Section 6.6.Field 1Field 2Field 3Field 4Field 5Field 6Field 7ProjectOriginator CodeZone/ SystemLevelTypeRoleDescription requiredrequiredreq’dreq’dreq’dreq’dRequiredXXXXXXXXXXXXXXXXText definition6 digits3 digits2/3 digits2 digits2 digits1 digitn/aField 1: Project No. This should match the Project number as included in the file name.Field 2: Originator Code. 3 letter code to represent the originator. Small Projects HandbookPage 19
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]Field 3: Zone/System. Appropriate for separate buildings / systems on large projects or phased projects. On a simple project use XXNon Specific, on more complex projects use a 2/3 digit code that refers to a specific area or building within a proposed site i.e. BD5 for Building 5.Field 4: Building Level. For a multi-storey Revit model this will generally be XX, however if any models are level-specific, this should be reflected in the file name i.e. GF or 25 depending on the convention for naming floors within a project.Field 5: Type. This may simply be M2for 2D drawing. Field 6: Role. AArchitect, CCivil Engineer, EElectrical Engineer, KClient, MMech Eng, PPublic Health Eng, QQuantity Surveyor, SStructural Eng. NOTE: Some clients use a non-role-specific numbering system. If such a system is to be used then all relevant codes for this field should be outlined in the box below. Field 7: Description. Model Name or drawing sequential number. Again, if a specific system is to be used for numbering the drawing sheets, please outline this system in the box below.6.8Naming Sheets Cont.Small Projects HandbookPage 20
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]6.9Naming ViewsOutline in the box below the project convention for naming views within the model. Note that this may differ for the titles that are visible in the project browser and the title that appears once the view has been placed on a drawing sheet. If the project browser is to be sorted in a particular manner to allow for easier navigation this should also be outlined below.Small Projects HandbookPage 21
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]6.10Archived Work Stage ModelsOnce a stage of the project has been completed an archive copy of all BIM data produced should be created. It is the responsibility of the party acting as Model Manager to ensure that all information is collated and archived together, including all models that form the overall project model. It is essential that all models to be archived as a record of each job stage are detached from the live Work In Progress central files so that they remain a true and accurate record of information that was issued. Outline in the box below any information regarding specific requirements for archiving the model.PART 7 – LEVEL OF DEVELOPMENTSmall Projects HandbookPage 22
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]7.1Project Deliverables LODLOD or Level of Detail/Development is based on applying a standard approach to the development of content/detail in BIM models. There are differing systems used to define these levels. It may be perceived that each level roughly ties in with the key stages of a project but depending on specific project requirements it is commonly the case that different elements of a BIM project are developed to different levels of detail.The standard definitions for the LOD system generally used by [Practice name] are outlined in the BIM section of the Practice CAD Standards. Some clients may operate their own LOD definition system and where this is the case this should be noted in Section 1.5 above and should replace the definitions in Section 7.2 below.A Level of Development agreement form should be completed and agreed by the relevant parties and added to this document as an appendix.7.2LOD DefinitionsTo be replaced with project-specific definitions where appropriate.LOD 100: Overall building massing indicative of area, height, volume, location and orientation.Potential deliverables/output:Area analysis studies based on net/gross areas, basic environmental analysis, basic cost estimates based on floor areasLOD 200: Information modelled as generalised systems or assemblies with approximate quantities, size, shape, location and orientation. Other non-geometric information may be attached to the model elements.Potential deliverables/output:Basic output of GA Plans, Elevations, GA Sections, etc., improvement of accuracy of cost estimates from LOD 100, increased cost certainty, basic door/window schedules – quantities & approximate sizes, more detailed environmental analysis from LOD 100, initial estimates of material quantities, increased accuracy of area analysisSmall Projects HandbookPage 23
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]LOD 300: Information modelled as specific assemblies, accurate in terms of quantity, size, shape, location and orientation. Other non-geometric information may be attached to the model elements.LOD 400: Information modelled as specific assemblies that are accurate in terms of quantity, size, shape, location and orientation with complete fabrication, assembly and detailing information. Other non-geometric information may be attached to the model elements.LOD 500: Model Elements modelled as constructed assemblies, accurate in terms of quantity, size, shape, location and orientation. Other non-geometric information may be attached to the model elements.PART 8 – QUALITY CONTROL CHECKSChecksDefinitionResponsible PartySoftware Programme(s) FrequencyDocumentationVisual Check Ensure there are no unintended model components and the design intent has been followed BIM Authors:Design ConsultantsDailyInterferenceCheck Detect problems in the model where two building components areclashing including soft and hard Information manager:Design ConsultantsWeeklyClash detection report: Summary document –PDF formatSmall Projects HandbookPage 24
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]Standards Check Ensure that the BIM and AEC CADD Standard have been followed (fonts, dimensions, line styles, levels/layers, etc) Information manager: DailyModel Integrity Checks Describe QC validation process used to ensure that Project Facility Data set has no undefined, incorrectly defined or duplicated elements and reporting process on non-compliant elements and corrective action plans At end of each design /project stage PART 9 – MODEL/EXECUTION PLAN REVIEWSThe [Practice name] model and information from consultants and engineers should be reviewed at regular intervals by the project team. This should be done in conjunction with a review of this Execution Plan, with any necessary changes made to this document by the project BIM Coordinator. Please state any agreed review dates below for reference.Small Projects HandbookPage 25
BIM execution plan[JOB NUMBER] – [PROJECT NAME]revision [X]PART 10 – LESSONS LEARNEDThe use of BIM is a continually evolving process, if any key lessons were learned or new skills developed please give a description in the box below so that the information may be shared with other BIM users within [Practice name].Small Projects HandbookPage 26