Beruflich Dokumente
Kultur Dokumente
Subheading
Tertiary heading
Text text
Tertiary heading
Text text
Contenido
Subheading.............................................................................................................................................................................. 1
1.
INTRODUCTION............................................................................................................................................................ 3
1.1.
Purpose................................................................................................................................................................. 3
The purpose of this document is to ensure that all supply chain stakeholders working on this project have a clear
understanding of the Client Information Requirements and expectations. It is intended to form part of the appointment
and tender documentation to define the BIM requirements.................................................................................................3
1.2.
Goals..................................................................................................................................................................... 3
It is the Client intention to make use of Building Information Modelling tools and processes for this Hotel 4 Star Project to
support the Design, Construction, Handover and Operation stages of the project. The Client requires achieving a BIM
Level 2................................................................................................................................................................................. 4
1.3.
The deployment of this new work system requires the utilisation of new processes and technology, which brings with
them new terminology. Consideration is given here to some of these terms and their definition. The definitions here are
limited to those that are believed to give clarity to this system:...........................................................................................4
2.
TECHNICAL................................................................................................................................................................... 5
2.1.
Software Platforms.............................................................................................................................................. 5
The client does not require a specific software platforms, however, it is essential that native formats of models be shared
openly and any software platform selected to contribute to the Federated Project Information Model has the ability to
interface with other model suppliers systems and export to IFC(2x3) for information extraction and archiving purposes.
Any inherent object intelligence must be able to be extracted to a format readable in Microsoft Excel for information
exchange purposes.............................................................................................................................................................. 5
1. INTRODUCTION
This document outlines the required deliverables and standard requirements for the structure, coordination
and management of Building Information Modelling (BIM) for this Hotel project undertaken on behalf of the
Client.
This document does not diminish the requirement for a comprehensive project BIM Execution Plan to be
produced.
The EIR defines the basis for the project BIM Execution Plan to respond to. Both the EIR and the BEP will
ensure the project conforms to the Client organisational information strategy. Any exceptions or exclusions
must receive approval from the Client
1.1. Purpose
The purpose of this document is to ensure that all supply chain stakeholders working on this project have a
clear understanding of the Client Information Requirements and expectations. It is intended to form part of the
appointment and tender documentation to define the BIM requirements.
This document is structured into four sections, Technical, Management, Commercial and Competence
Assessment.
The information included within the Employers Information Requirements should form the basis of the project
BIM Execution Plan and as such detail the way in which the requirements herein are to be achieved.
1.2. Goals
It is the Client intention to make use of Building Information Modelling tools and processes for this Hotel 4 Star
Project to support the Design, Construction, Handover and Operation stages of the project. The Client
requires achieving a BIM Level 2.
The Client expects the implementation of BIM to drive efficiencies and de-risk the project throughout design
and construction stages and simplify procurement of operational services during the in-use stage .
TERM
DEFINITION
AIM
Asset Information Model, maintained information model used to procure, manage, maintain and operate
an asset.
Attribute
Non-geometric data attached or linked to an object relating to the performance, status and requirements
of a particular component.
BS 1192:2007,
Documents created by the BSi (British Standards Institute) providing guidance relating to the information
management on construction projects during the capital delivery phase of construction projects.
PAS 11922:2013
BEP
BIM Execution Plan (BEP) refers to a document incorporating protocols and procedures for all
stakeholders relating to project information; it is a response to the EIR.
BIM
Building Information Modelling is the process of designing, constructing and operating a building or
infrastructure asset using electronic object-orientated information.
CDE
A common data environment is a single source of information for any given project, used to collect,
manage and disseminate all relevant approved project documents for multi-disciplinary teams in a
managed process.
EIR
Employers Information Requirements document referred to in PAS 1192-2:2013 sets out the information
to be delivered by the supplier as part of the delivery process to the employer. This information will be
inclusive of standards and protocols to be used on the project, schedule of software formats to be used,
any changes from the competencies set out in PAS 1192-2:2013. This will also include: description of
information exchange, definition of coordinate origin/system, schedule of information to be included in the
information model and any additional constraints set by the employer on the model.
DIM
Design intent model, initial version of the project information model (PIM) developed by the design
suppliers.
MIDP
The primary plan for when project information is to be prepared, by whom and using what protocols and
procedures.
PIM
Project information model, developed during the design and construction phase of a project.
2. TECHNICAL
2.1. Software Platforms
The client does not require a specific software platforms, however, it is essential that native formats of models
be shared openly and any software platform selected to contribute to the Federated Project Information Model
has the ability to interface with other model suppliers systems and export to IFC for information extraction and
archiving purposes. Any inherent object intelligence must be able to be extracted to a format readable in
Microsoft Excel for information exchange purposes.
Prior to the commencement of each stage, available software versions will be reviewed for the on-going
design. No models will be updated to a later version of software without discussion and agreement with the
Project Team and the Project Information Manager.
All model information must be delivered via a project CDE (Common Data Environment) in line with PAS11922:2013 workflows and as detailed within the project BEP.
2.3. Co-ordinates
Base project reference points are to be defined by the design leader and recorded in the project BEP. To keep
coordinates consistent, set-out information shall be maintained throughout all models, and to eliminate
compatibility issues arising from discrepancies between coordinate systems, all project files shall share the
same survey point and coordinates.
The project team shall work on the models set up with identical locations and origin coordinates. The following
outlines the procedure for establishing model location and origin taking into account location and weather data
to enable energy analysis where required as a deliverable:
o
Building and/or site location on the architectural model shall be set at the correct longitude
and latitude or defined reference point.
True north of the building and/or site location on the architectural model shall also bet set
correctly. This is to be consistent with the existing site model
All the models produced shall use the Shared coordinates system
Project team members will share information in IFC format and 3D coordination exchange
formats to ensure that information is correctly and consistently aligned. The agreed process is
to be documented in the project BEP to provide consistency of methodology.
Further details regarding publishing and migrating location data is to be included in the project BEP.
DEFINITION
USES
LOD 100
CONCEPTUAL
Overall building massing, indicative of area, height, volume, location
and orientation
Conceptual, Energy
Simulation
GENERIC PLACEHOLDERS
LOD 200
Design Development,
System Selection, Early
Procurement.
SPECIFIC ASSEMBLIES
LOD 300
Coordination,
Procurement, Approvals.
DETAILED ASSEMBLIES
LOD 400
Manufacture and
Assembly.
AS BUILT
LOD 500
A model element ownership matrix will be developed by the Information Manager to be contained within the
MIDP (Master Information Delivery Plan) and will cover stages in the RIBA plan of work (POW). The matrix will
map out the required LOD for each system against the milestones listed in the RIBA POW. The project
Information Manager will manage the MIDP throughout the development of the PIM ensuring all parties are
aware of their CDE Status and Level of Development responsibilities relative to the construction programme or
milestones on the project master programme (RIBA POW).
3. MANAGEMENT
3.1.Standards
In order to establish a consistent approach to collaboration, the Client requires the
core project team and its associated supply chain to adopt the following standards in
addition to the EIR:
o PAS1192-2:2013
o PAS1192-3:2014
o BS1192:2007
o BS8541-1 to 4
o CIC BIM Protocol
3.2.Roles and Responsibilities
With the implementation of information modelling it is necessary to outline specific
roles and responsibilities. The roles below are not new positions, but can be
considered roles that are applied to named individuals working on the project to
assign task ownership. It is important to note that these roles may be transferred
and migrate to different individuals as the project progresses. The assignation of
roles should be defined within the project BEP. The below list of roles can be found in
PAS1192-2:2013 7.5 Table2.
LEAD DESIGNER
Responsible for coordinating delivery of all design information, managing
information development and approvals, confirming design deliverables and overall
lead for configuration management.
INFORMATION MANAGER
Responsible for enabling reliable information exchange though a CDE (Common
Data Environment). To maintain and receive information into the information model,
enabling integration and coordination of information between disciplines. To
configure information for project outputs, populating the information exchange
format for the information model.
TASK TEAM INFORMATION MANAGER
Responsible for directing the production of task information in compliance with
standards and methods, directing the production of task information using agreed
systems outlined in the project BEP. Responsible for meeting the information
exchange milestones outlined in the MIDP.
TASK TEAM MANAGER
Responsible for the production of design outputs related to discipline-specific,
package-based or time-based tasks.
INTERFACE MANAGER
Responsible for managing spatial coordination on behalf of a task team, proposing
resolutions for the coordination of clashes.
The project BIM Execution Plan will set out the compliance processes and the means
by which the compliance is monitored and managed.
3.5.Co-ordination and clash detection
As part of the projects de-risking objective, designated suppliers are required to
input to and attend regular model coordination workshops. All suppliers must ensure
attendance to virtual and in-person model coordination meetings by individuals who
are able to make decisions on behalf of their task team. The process of clash
avoidance and clash detection on the project will be fully described in the project
BEP (BIM Execution Plan). This will include a tolerance strategy and clash resolution
process.
This process will be undertaken by way of regular sharing of model data to the
schedule outlined in the BEP in the form of native files and other agreed exchange
formats. Prior to sharing, the data shall be checked, approved and validated as
Issued for coordination in line with the BS1197:2007 and PAS1192-2:2013 status
codes in the CDE.
The project Information Manager will federate all task teams model information and
share this model and associated coordination reports on the project CDE. It is each
suppliers responsibility to ensure their own information is coordinated with others
and all suppliers must resolve the issues communicated in the coordination meeting
prior to the next scheduled meeting.
3.6.Collaboration process
The process of collaboration on the project will be fully described in the project BEP
(BIM Execution Plan). All processes must follow BS1192:2007 & PAS 1192-2:2013
using the described four CDE phases; Work In Progress, Shared, Published and
Archive.
The project Information Manager will set up and manage the project Common Data
Environment. The CDE is a single source of truth, used to capture, manage and
distribute all data on the project to ensure all project stakeholders have access to
the latest approved information.
MEETING TYPE
PURPOSE
BIM Kick-off
BIM Strategy
Model
Coordination
Look Ahead
3.8.Systems Performance
To support access and use of information for all parties, the following guidelines
must be met:
o
o
o
3.9.Compliance Plan
The Client requires all team members to comply with the following documents:
o
o
3.10.
Delivery Strategy for Asset Information
The Client requires capturing the information generated across the design and build
phases of project. This information must be submitted as part of the projects
handover documentation.
An Asset Information Model and COBie data will be generated by the Information
Manager with support of the task teams.
4. COMMERCIAL
4.1.Employers strategic purposes
It is essential that the project team comply with the Clients requirements. The
following priorities have been identified:
o
10
o
o
o
o
5. COMPETENCE ASSESSMENT
5.1.BIM tender assessment details
11
LOD management
Data Property Sets
Software versions
Modelling standard compliancy
Object behaviour and system dynamics
12
APPENDIX A
Name
Asset
Code
ASSET CODING
Type
Description
Common
Asset
Common
Description
Asset
Number
Unique
13
14
APPENDIX C
BIM QUESTIONARIE
No.
Question
Answer /
Understanding
Who drives BIM on each project, what are their titles and
responsibilities?
10
11
12
13
What is your current status and future plan for BIM rollout?
15
Supporting
Evidence
14
15
16
17
18
19
20
21
22
Have tools been specified to you and have you / would you
use them?
23
24
25
26
27
28
16
Project 2
Title
Sector
Customer
Contractor
Contact
Tel No
Project Value
Fee Value
Contract Duration
Scope of BIM Services
Benefits realised by BIM
17
Project 3