collaboration and work-sharing with mep and structure consultants_mr
TRANSCRIPT
COLLABORATION AND WORK -SHARINGWITH STRUCTURE AND MEP CONSULTANTS
Presented by:
March 2014
Michel Ruehr, Project BIM Manager, Group Revit Application Specialist
BIM is a processAnd the process needs to be planned and documentedDon’t blame the software if you don’t
COLLABORATION NEEDS SMART PEOPLE
•Define your key people
•Make sure key roles have backup
•Exchange knowledge and ideas early
•Don’t make rules and procedures up as you go
•Have a set of documents defining them ready to share
BIM
We don’t work in Isolation
CollaborationCoordinationCommunication
•Systems integration
with the design
•Analysis
•Timely information
• Build-ability
• Procurement
• Coordinated
• Aesthetics
• Functional
• Design
•Quality
•Cost
•Delivered on time
•Functional
•Useful
Client Architect
ConsultantsContractor
Be clear who is responsible for what
DEFINE YOUR INFORMATION MANAGEMENT
BIM Project Brief
Communication with the ClientDefine Scope within the Project BIM BriefUnderstand BIM Environment and Data Connections
Questions: Does XXXXXX already use Software for the following Areas.
And does XXXXXX need BIM to connect or exchange data with them.
•Facility Management Software
•Building Management Systems and Software
•Asset Management Software
•Construction Project Managing Software
•Construction Document Control Software
•Construction Budgeting and Cost control Software
Project BIM Brief
Define Type of BIMDefine Use of BIMDefine Level of Information Define Level of Development
Educate, Discuss, Define with the Client
HOW WILL YOUR PROJECT TEAM WORK TOGETHER
BIM Management Plan
Communication with the Project TeamDefine Scope and responsibilities within the Project BIM Management Plan
Defining the manner we will work together
The Project Team
3 BIM Requirements
3.1 Model / Standards Management
3.2 Sub-Contractor Engagement
3.3 The Order of Modelling
3.4 Colours of BIM datasets in coordination software
3.5 Project Coordinates
4 Collaboration Procedures & Technology
4.1 Communication15
4.2 Document Management System15
4.3 BIM Briefing and Milestone Review meetings
4.4 Facilitating BIM Coordination and collaboration
5 File Sharing and Data Exchange
5.1 General
5.2 Level of Detail / Development
Deliverables : Defining what is expected and whenWork out the fine DetailsDefining the Level of Development in the ModelDefine Classification systems used on the project
Project Setup (Linking) Schematic Plan (PowerPoint or similar so its easy to amend)
If you are the model manager the makeup of your model linking
structure and coordinate propagation layout may be obvious.
What is happening when you are not in the office, how will your consultants know?
Create a schematic model structure to
reveal the linked project relationships.
Start early and update as changes
happen. Planning and
setup mistakes are the base of most
BIM project hardships.
SETUP WORK SHARING AVOID THE PITFALLS
The Schematic Model Structure
Document is also a good reference
for file naming and your work-set
naming .
Make sure your work-set naming is
aligned with all Consultants
Avoid too many work-sets they will
only create unproductive work.
But make sure all links are on a
separate Link_workset
WORKING WITH STRUCTURAL CONSULTANTS
Golden Rules:
ALL TEAMS SHOULD BE ON THE SAME VERSION AND BUILD OF REVIT.
•Filenames should remain always consistent
•As per Project Setup Schematic Plan
•RVT project files should be archived for each Major Model Revision providing a history of issued RVT files
•All Structural and MEP Models should be linked origin to origin
•All models should have the shared coordinate system applied but should not be used for linking.
WORKING WITH STRUCTURAL CONSULTANTS
Team Process:Basic
•The ARCH team creates a grid*, levels, columns, slabs and walls
•The STR team starts by linking the ARCH file origin to origin
•The STR team then pins the linked ARCH Project
•The STR team copy monitor levels from ARCH Model
•The STR team deletes any redundant remaining levels from the original file
•The STR team checks Project_ Level 00_ is 0,00 (Project/ Elevation Base) (or check with the ARCH team if an
exception is found). Level 00 is the Base level and should never be moved.
•The STR team sets Levels to Shared (Elevation Base)
•The STR team acquire coordinates from ARCH model
This Grid may not be based on the structural layout of the building, but has been positioned temporarily by the
architect to provide a starting point.
Experience on 40+ collaboration projects has shown that copy monitor of levels and grids with structural consultants
is sufficient. Copy Monitor of floors, walls and columns is generally fraught with problems.
See next page.
COPY-MONITOR STRUCTURE
There are various rules that must be
considered for the above categories
that determine whether the
monitor will flag a change or not
these are as follows:
Monitor Rules
Monitor flags change?
Description of change Levels Grids Columns Walls Floors
Moved Yes Yes Yes Yes YesRotated N/A Yes No Yes YesSketch changed N/A N/A Yes Yes YesSize adjusted N/A N/A No Yes* Yes**Assemblies changed N/A N/A No No NoNew family added No No No No NoDeleted Yes Yes Yes Yes Yes
Monitoring in Revit
Revit Structure is limited to monitoring 5 categories these are;
• Levels
• Grids
• Columns
• Walls
• Floors
*Yes for core component of the wall
** Yes for width of slab
WORKING WITH MEP CONSULTANTSTeam Process:Basic
•The MEP team starts by linking the ARCH file origin to origin
•The MEP team then pins the linked ARCH Project
•The MEP team copy monitor levels from ARCH Model
•The MEP team deletes any redundant remaining levels from the original file
•The MEP team checks Project_ Level 00_ is 0,00 (Project/ Elevation Base) (or check with the ARCH team if an
exception is found). Level 00 is the Base level and should never be moved.
•The MEP team sets Levels to Shared (Elevation Base)
•The MEP team acquires coordinates from the ARCH model
•Grids may or may not be transferred depending on workflow
•The ARC team has set up Linked Views as backgrounds for the MEP consultants
•Early communication on what views and what model information is needed is invaluable
Team Process:Advanced
•To align fixture positions with the architectural model and keep it up to date, the mechanical engineer can use
Copy/Monitor to copy fixtures to the MEP project. If the architect adds, removes, or changes fixtures, Revit
MEP notifies the mechanical engineers of the changes. They can then update the MEP project, as appropriate.
COORDINATING VIA COPY MONITOR WITH MEP CONSULTANTS
But this is not as easy as it looks
This is where
In a Revit MEP project,
you can copy and monitor the following types of MEP elements from an architectural project:
•Air terminals
•Communication Devices
•Data Devices
•Electrical Equipment
•Electrical Fixtures
•Fire Alarm Devices
•Lighting Devices
•Lighting fixtures
•Mechanical equipment
•Nurse Call Devices
•Plumbing fixtures
•Security Devices
•Sprinklers
•Telephone Devices
CollaborationCoordinationCommunication Is a must
For Architects •A GPO, Light Switch, Fire Alarm Button is all an Electrical Fixture (We kind of guess it is not Equipment)
Electrical Fixture
•HSL-Call Emergency-3D
•HSL-Call-Intercom WM-3D
•HSL-Data-Outlet-3D
•HSL-DCO_3D
•HSL-LightSwitch-3D
COMMUNICATION VIA COPY MONITOR
For Electrical Engineers Its more something like this
NURSE CALL DEVICES
•HSL-Detail-Nurse Call Light
•HSL-Call Emergency-3D
•HSL-Call-NurseAssist-3D
•HSL-Call-PatientHandset-3D
•HSL-Call-PatientStaff-3D
•HSL-Call-Intercom WM-3D
DATA DEVICES
•HSL-Data-Outlet-3D
•HSL-DCO_3D
LIGHTING FIXTURES
•HSL-LightSwitch-3D
COPY MONITOR WITH MEP CONSULTANTS
But this is not the end
See what we get when the consultant copy-monitors
On top of this some consultants work differently from others.
So we need to talk to our consultant how they divide their fixtures and devices into categories
Architects link before copy monitor
Consultants link after copy monitor
MEP COPY MONITOR
Don’t use level based or work plane based
families with an offset parameter for
monitored MEP fixtures
Use face based families with no offset
parameter