خطة تطبيق البيم بالشركة BIM Implementation
كيف ستتبنى البيم بالشركة
بدلاً من افتراض أنك بحاجة إلى أن تكون متوافقًا مع BIM Level 2 ، حاول أن تحدد ما الذي تريد أن تكون ولماذا وما الفائدة التي ستجلبها لك .
يجب أن تتماشى مع خطة العمل الخاصة بك من ثلاث إلى خمس سنوات. مع كل مشروع ، حاول البحث عن فوائد بيم جديدة ، أي عملية جديدة ، نظام ، إجراء ، شراء البرامج ، التدريب ، وما إلى ذلك والتي يمكن تقديمها لتحريكك على طول جدول BIM الزمني الخاص بك.
BIM Implementation Plan Details
- Define the Scope of BIM usages
- Developing 3D BIM Models.
- Coordination and Clash Detection.
- Quantities scheduling and takeoffs.
- Animations & Perspectives for presentation purposes.
- Time Scheduling simulation.
- Cost Estimation and simulation.
- Shop drawings / Fabrication.
- Facility managements.
- Selecting the Right BIM Software
- Choose the suitable authoring modeling software.
- Choose the coordination software. (Navisworks, etc…)
- Analysis software (Structure / Sustainability / etc..).
- BIM reviewing software. (Solibri, etc…)
- 4D / 5D software. (Vico, RIB, etc…)
- Documents Management System.
- Addressing IT Issues (Workstation / Network Infrastructure)
- Modeling Software Training Courses (Using Sample Project)
- Beginners and Advanced Training.
- Families creation training.
- BIM management training.
- Up-skilling managers to understand BIM processes.
- BIM management: Workow and technology transitioning. Tailor and customize the training to meet the specic project or business needs enabling BIM in existing projects with minimum disruption.
- BIM Standards Developing
- Review the Current Drafting Standard and Drafting Process.
- Implement AIA Standards.
- Template Creation and Customization. Templates are essential to streamline project development at an early design stage in order to accelerate the Modeling process.
- Naming Conventions. Standardizing the naming of all the components of BIM modeling process
- Content Creation. Setting up the rules for creation quality content families that meet needs and standards
- Efficiency Workflow. Collaboration plan and modeling workflow on medium to large-scale projects, carefully studied and considered
- Export to CAD. Cover the extent of 2D drawings and schedules that can and cannot be derived from the BIM model (according to the readiness of the BIM technology)
- Define M3 ( Minimum Modeling Matrix).
- Define BIM Quality Assurance Checks. Through Modeling Validation, Interference Validation, forms and checklist.
- Define BIM Execution Plan. BIM Execution Plan will define clearly the “what” and “how” to create a BIM model at a particular stage of a project. It should be clearly established at the beginning of a project, and then executed throughout until final delivery.
- Skill Assessment. To ensure that staff has the required skills to meet BIM modeling needs, and meet expectations.
- BIM Management Plan.
- Pilot Project
- Use BIM in none priority project, low to medium complexity.
- Revisit the standards and make changes after the trial, if needed.
- Execute BIM
- Go live with real project in BIM, along with our team onsite.
- Setup Roles and Responsibilities for the team members
- Setup a process chart with roles, responsibilities, modeling schedule.
- Continuously monitor efficiency using monitoring tools. Increase the complexity as the efciency benchmarks are met at each level.
- Define KPIs (Key Performance Indicator ) at project, organization and employee levels.
BIM Implementation Checklist0
نقط #تحقيق #CHECKLIST
1.0 o Program
2.0 o Develop Implementation Milestones and Schedule
3.0 o Core Team Selection
4.0 o Core Team Training
5.0 o Core Team Develops Office Project Template (Test Project)
5.1.0 o Non-template Related Items
5.1.1 o Export layer text file
5.1.2 o Import line weights text file
5.1.3 o Shared parameters file
2.0 o Develop Implementation Milestones and Schedule
3.0 o Core Team Selection
4.0 o Core Team Training
5.0 o Core Team Develops Office Project Template (Test Project)
5.1.0 o Non-template Related Items
5.1.1 o Export layer text file
5.1.2 o Import line weights text file
5.1.3 o Shared parameters file
5.2.0 o Line Weights
5.2.1.1 o Annotation line weights
5.2.1.2 o Model line weights
5.2.1.3 o Color delineations
5.2.1.4 o Revit grey scale vs. traditional acad screen
5.2.1.5 o Phasing
5.2.1.6 o Patterns
5.2.1.7.0 o Linked DWG Files ربط ملفات الاتوكاد
5.2.1.7.1 o Linked drawings files
5.2.1.7.2 o Linked with colors preserved vs. colors as black
5.2.2.0 o Plotters
5.2.2.1 o Large format, full size
5.2.2.2 o Large format, half size
5.2.2.3 o 11×17
5.2.2.4 o 8 ½ x 11
5.2.2.5 o Document printer settings
5.2.2.6 o Adjust line weights and grey scale as needed based on plots
5.2.2.7 o Plot to PDF and DWF send to plotter (identify any issues)
5.2.3.0 o Print Setups
5.2.3.1 o Create print setups in office template for all applicable plot styles
5.3.0 o Tags5.3.1 o Create all office standard tags and load into office template
5.4.0 o Patterns
5.4.1 o Base set of patterns
5.4.2 o Office process for creating new patterns
5.5.0 o View Markers5.5.1 o Elevation markers
5.5.2 o Section (building, and wall section markers, if different)
5.5.3 o Detail bubbles
5.5.4 o Callouts
5.5.5 o Match line callouts
5.6.0 o Leader Arrows
5.6.1 o Text leaders
5.6.2 o Tag leaders arrows
5.7.0 o Dimension types
5.8.0 o Text الكتابات
5.8.1 o Create types in the office template
5.8.2 o Create text types in the families
(detail components, generic annotations, all tag families, etc.)
5.9.0 o Schedules الجداول
5.9.1 o Create working schedules
5.9.2 o Create plotting schedules for all schedules
5.10.0 o Views and Sheets
5.10.1 o Create typical levels
5.10.2 o Create standard views
5.10.3 o Create office title blocks (include all variety sizes used)
5.10.4 o Create typical sheets
5.11.0 o Family creation (in template or in library?)
5.10.2 o Create standard views
5.10.3 o Create office title blocks (include all variety sizes used)
5.10.4 o Create typical sheets
5.11.0 o Family creation (in template or in library?)
5.11.1 o Establish minimal set of working families
5.11.2 o Establish a routine for migration of families from project to office library (See 6.3)
5.11.3 o Determine which families are to be pre-loaded into template and which families are to be loaded as needed from the libraries
6.0 o Establish Office Revit Protocols (Test Project)
5.11.2 o Establish a routine for migration of families from project to office library (See 6.3)
5.11.3 o Determine which families are to be pre-loaded into template and which families are to be loaded as needed from the libraries
6.0 o Establish Office Revit Protocols (Test Project)
6.1 o File structure for projects (i.e. correspondence, consultant files, and reference files; usually mimics traditional project file structures)
6.2 o Work sharing protocol
6.3 o Family creation, storage and protocols
6.4 o Family transition from project to office library
6.5 o System family protocols (walls, floors, roofs, etc.)
6.6 o Material and Plant Library protocol
6.7 o Keyboard shortcuts
6.8 o File support paths (paths to Revit standards file)
6.9 o Software upgrading
6.10 o Project phases
6.11 o Project archiving
7.0 o Revisit Item 1.0 – Program
8.0 o Pilot Project Selection
9.0 o Pilot Project Team and Training
10.0 o Pilot Project Development
11.0 o Revisit Item 7.0 – Program
12.0 o Train Rest of Office on Project by Project Basis
1.0 Program
Define the end product. What are we trying to accomplish with BIM? Record existing process flows through the office. Also, identify problematic areas where the software process may conflict with the office processes. At this time, a test project and a pilot project will be selected and the scopes and schedules of these projects will be determined.2.0 Develop Implementation Milestones
Use outline above as a starting point; identify key areas/milestones that need to be achieved that can be measured quantitatively and qualitatively along with a schedule of estimated completion of each milestone.3.0 Core Team Selection
This team will ultimately be responsible for the success of the implementation. This group will also be responsible for finalizing the office standards and implementation. This group should consist of a diverse staff base as possible to ensure different perspectives are seen (i.e. principles, project architects, drafting technicians, etc.).
4.0 Core Team Training
Formal software training of the Core Team.
5.0 Core Team Develops Office Project Template (Test Model)
Use the outline above (section 5) to begin sorting out and creating the project template. The project template should be created in conjunction with the test model.
Test Model
A set of typical drawings, small 15-20% reproduced in Revit. Include an area that has both interior and exterior walls, stairs, restrooms and roof area. Recreate each sheet that it appears in the final set of drawings.
This process will get the majority of the bugs out of the template and protocols before they are put into production as well as assist in developing the office template and protocols.
6.0 Establish Office Revit Protocols
The office Revit protocols and libraries should be created in conjunction with the test model (see section 5).
7.0 Revisit Item 1.0 – Program
Revisit the problematic areas identified in the initial programming phase and identify the solutions to these issues. Also, identify any new areas that need to be addressed. Re-evaluate and if necessary, redefine your “end product statement,” or what solutions can help to get back on track towards achieving our end result?
8.0 Pilot Project Selection
Select a project that will produce billable hours to be produced in the software as a pilot project.
9.0 Pilot Project Team and Training
This project can be produced by either the Core Team or a new Pilot Project Team.
Having the Core Team produce the pilot project allows for an already trained team to create a working model that can be used as an example in training future users.
Selecting a new Pilot Project Team allows for new users the get trained and familiarized with the software, the template and Revit office procedures on billable hours, but lacks an example model for them to reference and also can be subject to more billable hours due to the learning curve.
If elected, formal training will begin for the new Pilot Project Team. Also, they will be given basic training by the Core Team on the office template, libraries and protocols.
10.0 Pilot Project Development
Pilot project is developed to put the templates, libraries and protocols fully to the test.
11.0 Revisit Item 7.0 – Program
Another look must be given to the programming phase prior to moving into full production of Revit.
· Was my “end product statement” achieved?
· Were any issues that conflicted with current office procedures addressed and resolved?
If any issues have not yet been resolved, they should be addressed and dealt with before rolling out the software to the rest of the office. This is the time to deal with these issues so new users can focus solely on learning the software rather than dealing with loop holes in office protocols.
12.0 Train Rest of Office on Project by Project BasisNow formal software training can begin on other staff members. Treat the first project for each team as a pilot project. Give them basic training on the office template, and Revit protocols. Also, give them time to learn from the experiences gained by the pilot project/team and to share their views on what is working/not working with the office template, libraries and protocols.
6.2 o Work sharing protocol
6.3 o Family creation, storage and protocols
6.4 o Family transition from project to office library
6.5 o System family protocols (walls, floors, roofs, etc.)
6.6 o Material and Plant Library protocol
6.7 o Keyboard shortcuts
6.8 o File support paths (paths to Revit standards file)
6.9 o Software upgrading
6.10 o Project phases
6.11 o Project archiving
7.0 o Revisit Item 1.0 – Program
8.0 o Pilot Project Selection
9.0 o Pilot Project Team and Training
10.0 o Pilot Project Development
11.0 o Revisit Item 7.0 – Program
12.0 o Train Rest of Office on Project by Project Basis
1.0 Program
Define the end product. What are we trying to accomplish with BIM? Record existing process flows through the office. Also, identify problematic areas where the software process may conflict with the office processes. At this time, a test project and a pilot project will be selected and the scopes and schedules of these projects will be determined.2.0 Develop Implementation Milestones
Use outline above as a starting point; identify key areas/milestones that need to be achieved that can be measured quantitatively and qualitatively along with a schedule of estimated completion of each milestone.3.0 Core Team Selection
This team will ultimately be responsible for the success of the implementation. This group will also be responsible for finalizing the office standards and implementation. This group should consist of a diverse staff base as possible to ensure different perspectives are seen (i.e. principles, project architects, drafting technicians, etc.).
4.0 Core Team Training
Formal software training of the Core Team.
5.0 Core Team Develops Office Project Template (Test Model)
Use the outline above (section 5) to begin sorting out and creating the project template. The project template should be created in conjunction with the test model.
Test Model
A set of typical drawings, small 15-20% reproduced in Revit. Include an area that has both interior and exterior walls, stairs, restrooms and roof area. Recreate each sheet that it appears in the final set of drawings.
This process will get the majority of the bugs out of the template and protocols before they are put into production as well as assist in developing the office template and protocols.
6.0 Establish Office Revit Protocols
The office Revit protocols and libraries should be created in conjunction with the test model (see section 5).
7.0 Revisit Item 1.0 – Program
Revisit the problematic areas identified in the initial programming phase and identify the solutions to these issues. Also, identify any new areas that need to be addressed. Re-evaluate and if necessary, redefine your “end product statement,” or what solutions can help to get back on track towards achieving our end result?
8.0 Pilot Project Selection
Select a project that will produce billable hours to be produced in the software as a pilot project.
9.0 Pilot Project Team and Training
This project can be produced by either the Core Team or a new Pilot Project Team.
Having the Core Team produce the pilot project allows for an already trained team to create a working model that can be used as an example in training future users.
Selecting a new Pilot Project Team allows for new users the get trained and familiarized with the software, the template and Revit office procedures on billable hours, but lacks an example model for them to reference and also can be subject to more billable hours due to the learning curve.
If elected, formal training will begin for the new Pilot Project Team. Also, they will be given basic training by the Core Team on the office template, libraries and protocols.
10.0 Pilot Project Development
Pilot project is developed to put the templates, libraries and protocols fully to the test.
11.0 Revisit Item 7.0 – Program
Another look must be given to the programming phase prior to moving into full production of Revit.
· Was my “end product statement” achieved?
· Were any issues that conflicted with current office procedures addressed and resolved?
If any issues have not yet been resolved, they should be addressed and dealt with before rolling out the software to the rest of the office. This is the time to deal with these issues so new users can focus solely on learning the software rather than dealing with loop holes in office protocols.
12.0 Train Rest of Office on Project by Project BasisNow formal software training can begin on other staff members. Treat the first project for each team as a pilot project. Give them basic training on the office template, and Revit protocols. Also, give them time to learn from the experiences gained by the pilot project/team and to share their views on what is working/not working with the office template, libraries and protocols.