+ All Categories
Home > Documents > RBR-DOC-BIM-BMA-0020 BEPPostcontractTemplate public draft … · 2020. 9. 27. · 3# 3bjm "4 3fh /p...

RBR-DOC-BIM-BMA-0020 BEPPostcontractTemplate public draft … · 2020. 9. 27. · 3# 3bjm "4 3fh /p...

Date post: 03-Feb-2021
Category:
Upload: others
View: 0 times
Download: 0 times
Share this document with a friend
29
RB Rail AS Reg. No 40103845027 K. Valdemāra iela 8-7 Riga, LV-1010, Latvia PUBLIC RBR-DOC-BIM-BMN-0020 The sole responsibility of this publication lies with the author. The European Union is not responsible for any use that may be made of the information contained therein. Detailed BIM Strategy Post-contract BIM Execution Plan (BEP) Template Detailed BIM Strategy Guidelines Public draft v0.1 21/08/2018
Transcript
  • RB Rail AS Reg. No 40103845027 K. Valdemāra iela 8-7 Riga, LV-1010, Latvia PUBLIC

    RBR-DOC-BIM-BMN-0020

    The sole responsibility of this publication lies with the author. The European Union is not responsible for any use that may be made of the information contained therein.

    Detailed BIM Strategy

    Post-contract BIM Execution Plan

    (BEP) Template

    Detailed BIM Strategy Guidelines

    Public draft v0.1

    21/08/2018

  • BEP Post-Contract template

    Public draft v0.1

    Contents

    Use of this template ................................................................................................................................................................................................ 4

    1. Post-Contract BIM Execution Plan ......................................................................................................................................................... 5

    1.1. Preface .................................................................................................................................................................................................. 5

    1.2. Project Delivery Manager .............................................................................................................................................................. 5

    1.3. Project Team Contacts ................................................................................................................................................................... 5

    2. Project Information ..................................................................................................................................................................................... 6

    3. BIM Use Cases ................................................................................................................................................................................................ 7

    4. Matrix of Responsibility (Model & Analysis) ....................................................................................................................................... 8

    5. Software Versions...................................................................................................................................................................................... 13

    6. Exchange Formats .................................................................................................................................................................................... 14

    7. Levels of Definition ................................................................................................................................................................................... 15

    8. Company Resource for This Project ................................................................................................................................................... 16

    9. Roles & Responsibilities .......................................................................................................................................................................... 17

    9.1. Authorities ........................................................................................................................................................................................ 18

    10. Project Collaboration Systems, Common Data Environments & Electronic Data Management ............................... 19

    11. Security & Extranet Access, Distribution Authority ...................................................................................................................... 20

    12. Major Project Milestones ........................................................................................................................................................................ 21

    13. Survey Strategy .......................................................................................................................................................................................... 22

    14. Geo-location & Coordinates System .................................................................................................................................................. 23

    15. Dimensional Consistency ....................................................................................................................................................................... 24

    17. File Naming Convention......................................................................................................................................................................... 25

    18. Quantity Extraction and Tracking Strategy ..................................................................................................................................... 26

    19. Quality Assurance ..................................................................................................................................................................................... 27

    20. Annexes ........................................................................................................................................................................................................ 28

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    3

    20.1. Task Information Delivery Plan (TIDP) ................................................................................................................................... 28

    20.2. Model Information Delivery Plan (MIDP) ............................................................................................................................. 28

    20.3. Project Implementation Plan (PIP) .......................................................................................................................................... 28

    20.4. BIM Objects Attributes Matrix .................................................................................................................................................. 28

    20.5. Authoring tool XXX procedures & workflows .................................................................................................................... 28

    20.6. Authoring tool YYY procedures & workflows ..................................................................................................................... 29

    20.7. Authoring tool ZZZ procedures & workflows ..................................................................................................................... 29

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    4

    Use of this template This template has been elaborated to be used as the basis for the post-contract BEP. The Supplier shall fulfill all the

    required information in order to show their intention to comply with all the standards and procedures described in

    the BIM Manual. The Supplier is free to add extra information.

    Where standards deviate from the BIM Manual, this should be communicated to the wider design team and RB Rail.

    This document is composed by the main document (describing the overall information of the BEP) and a list of

    annexes including the TIDP, the MIDP and the different BIM Authoring tools – specific procedures and workflows

    (there must be at least one annex by BIM Authoring tool and there could be various if the Supplier considers it

    necessary, for instance due to the existence of various disciplines developing the project with the same BIM

    Authoring tool).

    All the text in italics in this document serves as description to fulfill each section and shall be removed before final

    delivery of the post-contract BEP.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    5

    1. Post-Contract BIM Execution Plan

    The following provides the general information and the roles on the project (if applicable) together with details of

    key personnel who are likely to be involved in information exchange.

    1.1. Preface

    The BEP shall list the agreed targets for responsibility, timely delivery, exchange, reuse and final handover to the

    clients. It will also list all of agreed elements as outlined in the Employers Information Requirements.

    1.2. Project Delivery Manager

    This document is owned and maintained by the current Project Delivery Manager listed below.

    Company Name Project Contract

    Contract No.

    Role Names of individuals

    Email

    XXXXX XXXXX XXXX XXXX XXXX XXXXX XXXX@XXXX

    XXXXX XXXXX XXXX XXXX XXXX XXXXX XXXX@XXXX

    XXXXX XXXXX XXXX XXXX XXXX XXXXX XXXX@XXXX

    1.3. Project Team Contacts

    The project team (as listed below and with agreement from their parent companies) have accepted to use this

    document for the stated project.

    Company Name Project Contract

    Contract No.

    Role Names of individuals

    Email

    XXXXX XXXXX XXXX XXXX XXXX XXXXX XXXX@XXXX

    XXXXX XXXXX XXXX XXXX XXXX XXXXX XXXX@XXXX

    XXXXX XXXXX XXXX XXXX XXXX XXXXX XXXX@XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    6

    2. Project Information Key project information is defined below:

    Key Information Description

    Project Name XXXXX

    Project Address XXXXX

    Project Number XXXXX

    Contract Form XXXXX

    Project Description (as defined in EIR) XXXXX

    Project Deliverables (as defined in EIR) XXXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    7

    3. BIM Use Cases The major goals and objectives for the BIM implementation must be considered and stated as a project strategy,

    and are explained in the BIM Manual section “3.3. BIM Use Cases”.

    The main BIM Use Cases that shall be implemented in this project for each stage are listed in the chart below.

    BIM use case Value Engineering completion

    Master design completion

    Detail technical design completion

    As built Handover

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    8

    4. Matrix of Responsibility (Model & Analysis)

    Plan of work

    Model authoring

    Software

    Native format

    Open format(s)

    Value Engineering completion

    Master design completion

    Detail technical design completion

    As built Handover

    Example

    model REVIT RVT IFC

    Model

    aggregation

    Space

    planning

    Site, urban

    design

    context

    Site and

    existing

    buildings

    Architectural

    model

    Structural

    design model

    HVAC design

    model

    Building

    services mep

    design models

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    9

    Lighting

    design model

    Electrical

    design model

    Hydraulics

    design model

    Interior

    layouts and

    design model

    HVAC

    fabrication

    model

    Structural

    steel

    fabrication

    model

    Curtain wall

    fabrication

    model

    Transportation

    design

    model(s)*

    Landscaping

    and external

    works

    Renovation &

    refurb

    Facility

    management

    Construction

    model

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    10

    Other

    Other

    Other

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    11

    Plan of work

    Model authoring Software Native format

    Open format(s)

    Value Engineering completion

    Master design completion

    Detail technical design completion

    As built Handover

    Brief development

    Alternative design

    options

    Design performance

    Sun and shadow

    Structural

    Thermal

    Sustainability

    Model clash

    detection

    Cost planning &

    control

    Construction

    scheduling (4D)

    Security

    Code checking &

    regulatory

    compliance

    Accoustic analysis &

    design

    Disabled access &

    egress

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    12

    Fire protection

    FM, operation &

    maintenance

    Automated/linked

    specifications

    Heritage

    documentation &

    assessment

    Solar envelopes

    Over-shading

    Daylight

    Solar

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    13

    5. Software Versions The CAD/BIM software, including Add-Ons, and versions that will be used by the design teams shall be agreed

    before starting the project.

    Company Name Discipline CAD/BIM software Version Format Comments

    XXXX Architecture XXXX XXXX XXXX XXXX

    XXXX Rail XXXX XXXX XXXX XXXX

    XXXX Structure XXXX XXXX XXXX XXXX

    XXXX Utilities XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    14

    6. Exchange Formats The agreed Open formats for model and drawing file exchange are:

    DWG DGN IFC RVT NWC/NWD I-MODEL PDF Other

    Models

    Aggregated

    Models

    Drawings

    Final drawing

    format

    Schedules or

    spreadsheets

    No party is authorised to alter the platform or the build/version without prior consent by the project BIM

    Manager/Design Manager and RB Rail.

    Any requirements to upgrade the platform or build/version will be communicated to all parties with a minimum of

    one month’s notice. This is to allow for a period of discussion and testing before implementation.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    15

    7. Levels of Definition It is important to define who models what (the BIM Author) and to what Level of Definition (LOD).

    The LOD should be defined at a regional level by phases and disciplines and shall align with the BIM Manual.

    To be described by the Supplier for all project stages.

    The BIM Objects Attributes Matrix shall be completed by the Supplier and annexed to this document. The Supplier

    shall use as template the file RBR-DAT-BIM-BMA-0005_BIM_Objects_Attributes_Matrix.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    16

    8. Company Resource for This Project This table shall be the one included in the « Resource Assesment Form » anex from the pre-contract BEP, updated.

    Company Name

    Primary BIM role

    Secondary BIM Role (If applicable)

    Levels of competency (qualifications)

    Years of experience (BIM)

    Names of individuals

    Resource reference

    Stakeholder

    ZZ

    BIM

    Information

    Manager

    BIM discipline YY

    coordinator

    YY XX Individual 1 ZZ.1

    Stakeholder

    YY

    BIM discipline

    XX coordinator

    BIM Specialist YY XX Individual 2 YY.1

    Stakeholder

    ZZ

    BIM CDE

    Manager

    ZZ YY XX Individual 3 ZZ.2

    … … … … … … …

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    17

    9. Roles & Responsibilities At the start of a project it is important to identify the roles and responsibilities of the design teams. The Supplier

    shall describe the main roles and their responsibilities, as well as their contact details. Examples of the roles required

    within a large project are:

    ROLE COMPANY NAME NAME EMAIL & TELEPHONE NUMBER

    Lead designer YYYY XXXX XXXX

    Project delivery manager YYYY XXXX XXXX

    Construction manager YYYY XXXX XXXX

    Project information manager YYYY XXXX XXXX

    Task team manager YYYY XXXX XXXX

    Task team information

    manager

    YYYY XXXX XXXX

    Task team interface manager YYYY XXXX XXXX

    Task team BIM authors YYYY XXXX XXXX

    XXXX YYYY XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    18

    9.1. Authorities

    Role Authority

    Project information manager Responsible for the project BIM standards and ensure delivery of the information

    management requirements in the EIR

    Lead designer Responsible for spatial coordination

    Task team manager Responsible for documentation standards

    Interface manager Responsible for overall project coordination and clash resolution

    Task team information manager Reject non-compliant models, drawings & documents

    Project CAD/BIM coordinator Responsible for cad related project BIM standards

    Task team CAD/BIM coordinator Responsible for discipline cad related project BIM standards

    XXX XXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    19

    10. Project Collaboration Systems, Common Data Environments & Electronic Data Management

    Company Name Solution Network Database Field based Comments

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    20

    11. Security & Extranet Access, Distribution Authority

    Company Name Authorised Manager Authority (upload, download, change, access/distribution)

    XXXX XXXX XXXX

    XXXX XXXX XXXX

    XXXX XXXX XXXX

    XXXX XXXX XXXX

    The Supplier shall demonstrate in this section how he will, on project completion, securely archive information

    within their WIP / Shared CDE environments and or destroy any sensitive information.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    21

    12. Major Project Milestones The following table summarizes the proposed major project milestones relating to information delivery during the

    project.

    If separate design teams are planned, BEP shall include separate schedules.

    Start Date Value Engineering completion

    Master Design Completion

    Detail Technical Design Completion

    As Built Handover

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

    XXXX XXXX XXXX XXXX XXXX XXXX

    Only the major milestones are listed. A more detailed and co-ordinated Project Plan must be developed with the

    stakeholders and agreed. This is included in the Master Information Delivery Plan.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    22

    13. Survey Strategy Survey method Delivery format Survey origin Comments

    Point cloud XXXX XXXX XXXX

    Light detecting & Randing (lidar) XXXX XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    23

    14. Geo-location & Coordinates System

    The Supplier must describe in this section which reference point(s) shall be used to define the location of each

    model (e.g. for a bridge, the intersection point between the first abutment axis and the railway alignment).

    Also include a statement or diagram of the project origin and orientation.

    Model name Coordinates system

    Easting (m) Northing (m) Elevation (z) Azimuth

    XXX XXXX XXXX XXXX XXXX XXXX

    XXX XXXX XXXX XXXX XXXX XXXX

    XXX XXXX XXXX XXXX XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    24

    15. Dimensional Consistency The project team should agree common units of measurement. These should include distance (e.g. metres and

    millimetres) and angles (e.g. degrees/radians measured clockwise or counter clockwise).

    Type of information Millimeters Meters Degrees Radians Clockwise Counter

    Survey XXXX XXXX XXXX XXXX XXXX XXXX

    Models discipline 1 XXXX XXXX XXXX XXXX XXXX XXXX

    Models discipline 2 XXXX XXXX XXXX XXXX XXXX XXXX

    Drawings discipline 1 XXXX XXXX XXXX XXXX XXXX XXXX

    Drawings discipline 2 XXXX XXXX XXXX XXXX XXXX XXXX

    XXX XXXX XXXX XXXX XXXX XXXX XXXX

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    25

    17. File Naming Convention Naming conventions of all models, drawing sheets and clash renditions will comply with the BIM Manual. Where

    standards deviate, this should be communicated to the wider design team and RB Rail, and further defined in this

    chapter.

    The Supplier shall also define the volume strategy.

    All production and handover information shall be allocated a unique file identifier.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    26

    18. Quantity Extraction and Tracking Strategy

    The Supplier shall describe in this section how they are going to proceed with the Quantity Extraction and its

    tracking, based on the standards and procedures defined in the BIM Manual.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    27

    19. Quality Assurance The Supplier shall describe in this section how they are going to proceed with the Quality Assurance for verification,

    both of geometry / data and validation against the EIR, based on the standards and procedures defined in the BIM

    Manual.

    The Supplier shall describe the periodicity for the BIM model and data checks that will be defined, discussed and

    agreed with the Rail Baltica BIM Manager.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    28

    20. Annexes 20.1. Task Information Delivery Plan (TIDP)

    A Task Information Delivery Plan (TIDP) for each task within the project is appended to this document.

    The TIDP shall be prepared using the template “TIDP-template-RB”. When completed by all team members the

    TIDPs should be published in this document appendix and on the project extranet.

    20.2. Model Information Delivery Plan (MIDP)

    The Master Information Delivery Plan (MIDP) is developed from the separate TIDPs produced for each task within

    the project and appended to this document.

    This more detailed, co-ordinated MIDP, prepared using the template “MIDP-template-RB”, must be developed and

    agreed with the stakeholders. When completed the MIDP should be published in this document appendix and on

    the project extranet as a project plan.

    20.3. Project Implementation Plan (PIP)

    Revised PIP confirming the capability of the supply chain.

    20.4. BIM Objects Attributes Matrix

    Completed by the supply chain, prepared using the template “RBR-DAT-BIM-BMA-

    0005_BIM_Objects_Attributes_Matrix”.

    20.5. Authoring tool XXX procedures & workflows

    Each different BIM Authoring tools will have a specific annex with procedures and workflows to be used by the

    Supplier teams. (There must be at least one annex by BIM Authoring tool and there could be various if the Supplier

    considers it necessary, for instance due to the existence of various disciplines developing the project with the same

    BIM Authoring tool).

    If the Supplier considers it necessary, there could be specific annexes for special workflows or BIM use case-related

    subjects, such as the Design Review, Design Coordination, … It is important to mention that if specific procedures

    are not created to define the BIM Use Cases approach, they will have to be defined in the BEP Post-contract main

    document or in the Authoring tool procedures.

  • BEP Post-Contract template

    Public draft v0.1

    Public draft v0.1

    29

    20.6. Authoring tool YYY procedures & workflows

    See previous description

    20.7. Authoring tool ZZZ procedures & workflows

    See previous description


Recommended