POST-APPOINTMENT AWARD

BIM EXECUTION PLAN TEMPLATE

(WORK ACCORDING TO ISO 19650)

PREFACE

BEP DOCUMENT CODE

PROJECT

ORIGINATOR

VOLUME/ SYSTEM

LEVELS &LOCATION

TYPE

FUNCTION

NUMBER

XXXXXX

-

XXXXXX

-

XX

-

XX

-

XXX

-

XX

-

000XXX

Table 0‑1: BEP Document Code

PROJECT DELIVERY MANAGER

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

Project Delivery Manager Name	Company Name	Project Contract	Contract No	Function	e-mail	BEP Version
						R-1.0
						R-1.1
						R-2.0
						R-..

Table 0‑2: Project Delivery Manager

DOCUMENT AUTHORITY

? This project plan has been agreed by the representatives of the project team as listed below with the authority of their parent companies to accept this document as the Agreed BIM Execution Plan. By signature below, this BIM Execution Plan is herewith adopted and incorporated into the Agreement, dated ..../../.., for .......................... between ....................................and ...............................................

PARTY/DISCIPLINE	REPRESENTATIVE NAME/SURNAME	SIGN	DATE
APPOINTING PARTY
ARCHITECT
GENERAL CONTRACTOR
STRUCTURAL ENGINEER
MECHANICAL ENGINEER
PLUMBING ENGINEER
ELECTRICAL ENGINEER
LANDSCAPE ARCHITECT

Table 0‑3:Document Authority

DOCUMENT CONTROL / DOCUMENT REVISION TRACKING

DOCUMENT DEVELOPMENT

? The information contained in this document has been prepared with the understanding that this is a live document and will require periodic updates throughout the duration of the project to reflect the progress of the project (major revisions before each major phase) and incorporate newly agreed procedures and workflows. Initial authorship by .......................... in 2019.

VERSION DEFINITION

þ "Rev 1.0" is the first major release of the document.

þ Following major releases will be "2.0", "3.0" etc.

þ "Rev. 0.1" is the first iteration of the document.

þ For each minor change to the document, the decimal revision numbers to indicate the status of the current update process (1.1, 1.2, 2.1 etc.).) will be used,

þ Revisions starting with 0 (e.g. 0.1, 0.2) are draft issues for comment. Documents with a "0" revision number have not formally been issued.

CONFIDENTIAL INFORMATION

? This document is made available to the ................ on the express understanding that the information obtained in it will be regarded and treated by the .............., their contractors and their sub-contractors on their BIM projects as strictly confidential. The contents of this document are intended only for the sole purpose and use of ..........., their contractors and their sub-contractors on their BIM projects and not to be distributed to any other person outside the scope of this document.

REVISION	DATE	PREPARED BY	REVIEWED BY	APPROVED BY	ISSUED TO
R-0.1	..../../..
R-1.0	..../../..
R-1.1	..../../..
R-2.0	..../../..

Table 0‑4: Document Revision Tracking

DOCUMENT CHANGE LOG
REVISION	SECTION	DESCRIPTION

Table 0‑5: Document Change Log

TABLE OF CONTENTS

PREFACE. i

BEP DOCUMENT CODE. i

PROJECT DELIVERY MANAGER. i

DOCUMENT AUTHORITY. i

DOCUMENT CONTROL / DOCUMENT REVISION TRACKING.. ii

DOCUMENT DEVELOPMENT. ii

VERSION DEFINITION.. ii

CONFIDENTIAL INFORMATION.. ii

TABLE OF CONTENTS. iii

LIST OF APPENDICES. ix

LIST OF TABLES. xi

LIST OF FIGURES. xiii

1 OVERVIEW & INTRODUCTION.. 1

1.1 INTRODUCTION.. 1

1.2 LIST OF ABBREVIATIONS. 1

1.3 PROJECT INFORMATION (PIT_2). 1

1.4 MAJOR PHASES OR MILESTONES / BRIEF SCHEDULE. 2

1.5 BEP USE. 3

1.6 EXECUTIVE SUMMARY. 3

2 INFORMATION MANAGEMENT INDIVIDUALS. 4

2.1 FUNCTIONS RESPONSIBILITIES & AUTHORITIES (INDIVIDUALS LIST)-FRA_2. 4

2.2 INFORMATION MANAGEMENT ASSIGNMENT MATRIX (REM-A_3). 4

3 UPDATED REQUESTS & INFORMATION FROM INVITATION TO TENDER & TENDER RESPONSE PACKAGES. 5

3.1 APPOINTING PARTY'S EXCHANGE INFORMATION REQUIREMENTS. 5

3.1.1 APPOINTING PARTY'S INFORMATION REQUIREMENTS (INCL. UPDATES). 5

3.1.1.1 THE PROJECT SCOPE. 6

3.1.1.1.1 BIM GOALS (CONDITIONS of STATISFACTION-CoS) / BIM OBJECTIVES. 6

3.1.1.2 THE INTENDED PURPOSE. 6

3.1.1.2.1 PROJECT'S BIM USES. 6

3.1.1.3 THE INTENDED PROCUREMENT ROUTE (PRS_2). 9

3.1.1.4 PLAIN/PRE-QUALIFICATION QUESTIONS (PLQ_1). 9

3.1.2 LEVEL OF INFORMATION NEED MANUAL (LOIN_2). 9

3.1.3 SUPPORTING INFORMATION FOR LEAP(SUP-LEAP_1). 10

3.1.4 MILESTONES SCHEDULE (MIS_2-INCLUDING DETAILED DESCRIPTION OF THE INFORMATION AT EACH KEY DECISION POINT). 11

3.2 REFERENCE INFORMATION & SHARED RESOURCES (REF_2). 15

3.2.1 LIBRARY GUIDE & LIBRARY STRUCTURE IN DATA ENVIRONMENT (LIB_2). 15

3.2.2 SHARED RESOURCES GUIDE & SHARED RESOURCES IN DATA ENVIRONMENT (SHR_2). 15

3.2.3 PROJECT’S REFERENCE INFORMATION AND SHARED RESOURCES (REF_2). 16

3.3 PROJECT'S INFORMATION PROTOCOL RELATED REQUIREMENTS. 16

3.3.1 PROJECT'S COMMON DATA ENVIRONMENT STANDARDS, METHODS & PROCEDURES (CDE_2). 16

3.3.2 TRAINING REQUIREMENTS (TRA_1). 19

4 INFORMATION STANDARD (ıns_2). 20

4.1 INFORMATION CONTAINER NAMING REQUIREMENTS (ICN_2). 20

4.1.1 PROJECT DESIGNATORS. 21

4.1.2 ORIGINATOR (DESIGN PHASES) DESIGNATORS. 21

4.1.3 ZONE & SUB-ZONE. 21

4.1.4 LEVELS. 22

4.1.5 FILE TYPE DESIGNATORS. 22

4.1.6 DISCIPLINE DESIGNATORS. 23

4.1.7 SHEET/SUBMITTAL DESCRIPTION-VIEW-WORKSET NAMINGS. 24

4.1.8 NUMBER DESIGNATORS. 25

4.2 MEANS OF STRUCTURING & CLASSIFYING INFORMATION.. 25

4.2.1 PROJECT'S CLASSIFICATION SYSTEM (CLM_1). 25

4.2.2 METADATA.. 26

4.3 EXCHANGE OF INFORMATION.. 28

4.3.1 EXCHANGE FORMATS. 29

4.3.2 INFORMATION EXCHANGE / ATTRIBUTE DATA.. 29

4.3.2.1 PROJECT'S CONSTRUCTION OPERATIONS BUILDING INFORMATION EXCHANGE (COBIE) STANDARDS 29

4.3.2.2 INFORMATION TO BE EITHER EXCLUDED from OR INCLUDED ın INFORMATION MODELS. 30

4.3.2.3 PROJECT'S IFC & mvd STANDARDS. 30

4.3.2.4 THE EXCHANGE OF INFORMATION WITHIN THE APPOINTING PARTY’S ORGANIZATION.. 31

4.3.2.5 THE EXCHANGE OF INFORMATION BETWEEN THE APPOINTING PARTY AND EXTERNAL STAKEHOLDERS 32

4.3.2.6 THE EXCHANGE OF INFORMATION BETWEEN THE APPOINTING PARTY AND EXTERNAL OPERATORS OR MAINTAINERS. 32

4.3.2.7 THE EXCHANGE OF INFORMATION BETWEEN THE PROSPECTIVE LEAD APPOINTED PARTY AND THE APPOINTING PARTY. 33

4.3.2.8 THE EXCHANGE OF INFORMATION BETWEEN PROSPECTIVE APPOINTED PARTIES ON THE SAME PROJECT 33

4.3.2.9 THE EXCHANGE OF INFORMATION BETWEEN INTERDEPENDENT PROJECTS. 34

4.4 METHOD OF ASSIGNMENT FOR LEVEL OF INFORMATION NEED.. 34

4.5 UNITS, MEASUREMENT & COORDINATE SYSTEM... 34

4.5.1 UNITS & MEASUREMENT. 34

4.5.2 COORDINATE SYSTEM... 35

4.6 LEVEL OF ACCURACY (LOA_1). 35

4.7 SHEETS. 36

4.7.1 SHEET ORGANIZATION & SIZES. 36

4.7.2 DRAWING SHEET TEMPLATES. 36

4.7.3 TITLE BLOCK. 36

4.8 ANNOTATIONS, DIMENSIONS, LINES, SCHEDULES, ABBREVIATIONS AND SYMBOLS. 37

4.8.1 ANNOTATIONS. 37

4.8.2 DIMENSIONS. 37

4.8.3 LINES. 37

4.8.4 SCHEDULES. 37

4.8.5 ABBREVIATIONS. 37

4.8.6 SYMBOLS. 37

4.9 COLLABORATION & MODELING & PUBLISHING STANDARDS (WITHIN THE CDE) (COL-S_2). 38

4.9.1 MODELLING STANDARDS. 38

4.9.2 PUBLISHING STANDARDS. 39

4.10 USE OF INFORMATION DURING THE OPERATIONAL PHASE OF THE ASSET. 39

4.10.1 PIM TO AIM STANDARDS (pat-s). 39

5 INFORMATION PRODUCTION METHODS and PROCEDURES (pmp_2). 40

5.1 SPATIAL COORDINATION (COORDINATES&GEO-LOCATION) METHODS & PROCEDURES (SCO_2). 40

5.1.1 PIM ORIGIN & ORIENTATION.. 40

5.2 FEDERATION STRATEGY & INFORMATION CONTAINER BREAKDOWN STRUCTURE (FSB_1). 41

5.3 THE CAPTURE OF EXISTING ASSET INFORMATION.. 42

5.3.1 SURVEY STRATEGY. 42

5.3.2 QUANTITY EXTRACTION & TRACKING STRATEGY. 42

5.4 THE SECURITY OR DISTRIBUTION OF INFORMATIOn. 43

5.4.1 SECURITY REQUIREMENTS (SCR_1). 43

5.5 THE GENERATION, REVIEW OR APPROVAL OF NEW INFORMATION.. 43

5.5.1 COLLABORATION & MODELLING & publıshıng METHODS & PROCEDURES (WITHIN THE CDE) (COL-mP_2) 43

5.5.1.1 COLLABORATIVE WORKSPACE. 44

5.5.1.2 MODELLING (PROCESS/WORKFLOW) METHODS & procedures (wıthın cde). 44

5.5.1.3 PROJECT'S IFC & mvd METHODS & PROCEDURES. 44

5.5.1.4 BIM TEST MOCK-UP. 45

5.5.1.5 COMMUNICATION PROCEDURES (WITHIN CDE). 45

5.5.1.5.1 ELECTRONIC COMMUNICATION PROCEDURES. 45

5.5.1.5.2 MEETING COMMUNICATION PROCEDURES. 45

5.5.1.6 PUBLISHING METHODs & PROCEDURES. 46

5.5.1.7 CHANGE LOG.. 46

5.5.1.8 DATA MANAGEMENT ACCORDING TO SEGREGATION (DAS_2). 46

5.5.2 QUALITY ASSURANCE MANUAL (QUA_3). 47

5.5.2.1 QUALITY CONTROL (QC). 47

5.5.2.2 QUALITY ASSURANCE (QA). 47

5.5.2.3 QC/QA TOOLS. 47

5.5.3 COORDINATION, CLASH DETECTION & ISSUE MANAGEMENT MANUAL (CCI_3). 48

5.6 CDM/HEALTH & SAFETY REQUIREMENTS (CDM). 49

5.7 PIM TO AIM TRANSITION METHODS AND PROCEDURES (PAT-MP_1). 49

5.7.1 PROJECT'S CONSTRUCTION OPERATIONS BUILDING INFORMATION EXCHANGE (COBIE) METHODS & PROCEDURES. 49

5.8 THE DELIVERY OF INFORMATION TO THE APPOINTING PARTY. 49

6 INFORMATION DELIVERY STRATEGY (dt-ıds_1). 50

6.1 APPOINTMENT RELATED REQUIREMENTS. 50

6.2 TENDER RESPONSE REQUIREMENTS & EVALUATION CRITERIA (TEN-CR. 51

6.2.1 RISK ASSESSMENT REQUIREMENTS (RAS_1). 51

6.2.1.1 KEY PERFORMANCE INDICATORs (KPIS). 51

6.2.2 ACCEPTANCE CRITERIA MANUAL (ACR_1). 51

6.3 TASK TEAMS' CAPABILITY & CAPACITY. 51

6.3.1 CAPABILITY AND CAPACITY ASSESSMENT OF TASK TEAMs (TT-CCA_1). 51

6.3.1.1 INFORMATION MANAGEMENT CAPABILITY AND CAPACITY ASSESSMENT FORM (CCA_IM). 52

6.3.1.2 INFORMATION PRODUCTION CAPABILITY AND CAPACITY ASSESSMENT FORM (CCA_IP). 52

6.3.1.3 IT-INFORMATION TECHNOLOGY CAPABILITY AND CAPACITY ASSESSMENT FORM (CCA_IT). 52

6.3.2 TASK TEAMS' INFORMATION DELIVERY STRATEGIES (TT-IDS_1). 52

6.4 DELIVERY TEAM'S CAPABILITY & CAPACITY (DTCC_1). 52

6.5 DELIVERY TEAM'S MOBILIZATION PLAN.. 52

6.6 DELIVERY TEAM'S RISK REGISTER (drr_1). 53

6.7 INFORMATION DELIVERY STRATEGY (DT-IDS_1). 53

6.7.1 IDM... 53

7 HIGH LEVEL RESPONSIBILITY MATRIX (HLRM_1). 54

7.1 DETAILED RESPONSIBILITY MATRIX (DRM_0). 54

7.2 TASK INFORMATION DELIVERY PLAN (TIDP_1...N). 54

7.3 MASTER INFORMATION DELIVERY PLAN (mıdp_0). 55

8 SCHEDULE OF SOFTWARE, HARDWARE & IT INFRASTRUCTURE (SCH-IT_1). 55

8.1 SOFTWARE. 56

8.2 HARDWARE & IT INFRASTRUCTURE. 56

8.3 SCHEDULE OF SOFTWARE, HARDWARE & IT INFRASTRUCTURE. 56

9 TEMPLATES FOR FURTHER DELIVERY PHASE ACTIVITIES (4.2 - 5.8). 57

9.1 LEAD APPOINTED PARTY'S EXCHANGE INFORMATION REQUIREMENTS (EIR-LEAP). 57

9.2 MOBILIZATION OF RESOURCES. 57

9.3 MOBILIZATION OF INFORMATION TECHNOLOGY. 57

9.4 PROJECT'S INFORMATION PRODUCTION METHODS AND PROCEDURES TEST. 57

9.5 CHECKING TASK TEAM'S AVAILABILITY OF REFERENCE INFORMATION AND SHARED RESOURCES. 58

9.6 TASK TEAM'S QUALITY ASSURANCE CHECK. 58

9.7 TASK TEAM'S INFORMATION REVIEW & APPROVAL (BY TASK TEAM) FOR SHARING.. 58

9.8 DELIVERY TEAM'S INFORMATION REVIEW FOR COORDINATION.. 58

9.9 REVIEW & AUTHORIZATION OF THE INFORMATION MODEL BY LEAD APPOINTED PARTY. 58

9.10 SUBMITTAL LISTS. 59

9.11 INFORMATION MODEL REVIEW & ACCEPTION BY APPOINTING PARTY. 59

9.12 PIM ARCHIVE. 59

9.13 LESSONS LEARNED REGISTER. 59

10 TEMPLATES FOR OPERATIONAL PHASE ACTIVITIES. 60

11 REFERENCE DOCUMENTS & STANDARDS. 60

LIST OF APPENDICES

Annex_2.1 = REM-A_3: Information Management Assignment Matrix

Appendix_3.1 = OIR: Organizational Information Requirements

Appendix_3.2 = AIR: Asset Information Requirements

Annex_3.3 = USE_2: BIM USE MATRIX

Annex_3.4 = BUA_2: BIM USE ANALYSIS

Appendix_3.5 = PLQ_1 : Plain/Pre-Qualification Questions

Annex_3.6 = LOIN_2: Level of Information Need Manual

Appendix_3.7 = PoW-1: Plan of Work (with Milestones & Dates)

Appendix_3.8 = INP_2: Project’s Information Protocol

Annex_4.1 = ATD: Attribute Data Log

Annex_5.1 = CHL: Change Log Template

Annex_5.2 = CLAM: Clash Detection Matrix

Annex_6.1 = ACR_1: Acceptance Criteria Manual

Annex_6.2 = CCA_IM: Information Management Capability and Capacity Assessment Form

Annex_6.3 = CCA_IP: Information Production Capability and Capacity Assessment Form

Annex_6.4 = CCA_IT: Information Technology Capability and Capacity Assessment Form

Appendix_6.5 = MOB_1: DELIVERY TEAM'S MOBILIZATION PLAN

Appendix_6.6 = IDM: INFORMATION DELIVERY MANUAL

Annex_7.1 = HLRM_1: Delivery team’s High Level Responsibility Matrix

Annex_7.2 = DRM_0: Delivery Team’s Detailed Responsibility Matrix Initial Version (Template)

Annex_7.3 = TIDP-TMP: Task Information Delivery Plan Template

Annex_7.4 = MIDP_0: Master Information Delivery Plan Initial Version (Template)

Appendix_9.1 = EIR-LEAP-TMP: Lead Appointed Party's Exchange Information Requirements Template

Appendix_9.2 = MORE-TMP: Mobilization of Resources Report Template

Appendix_9.3 = MOIR-TMP: Mobilization of Information Technology Report Template

Appendix_9.4 = PMP-RR-TMP: Project's Information Production Methods and Procedures Test Report Template

Appendix_9.5 = CR-TT-TMP: Task Team's Access Check Report Template

Appendix_9.6 = QUA-TT-TMP: Task Team's Quality Assurance Check Report Template

Appendix_9.7 = IRR-TT-TMP: Task Team's Information Review (by Task Team) Report Template

Appendix_9.8 = IMR-DT-TMP: Delivery Team's Information Model Review Report Template

Appendix_9.9 = TTS-RR-TMP: Task Teams' Submittals & PIM Review Report by Leap Template

Appendix_9.10 = SBL-TMP: Submittal Lists Template

Appendix_9.11 = PIM-RR-TMP: Appointing Party's PIM Review Report Template

Appendix_9.12 = PAR-TMP: PIM to AIM Requirements Template

Appendix_9.13 = CLL-TMP: Capture Lessons Learned Template (for LEAP and APP's Use)

Appendix_9.14 = RLL-TMP: Lessons Learned Register Template(by APOP)

LIST OF TABLES

Table 0‑1: BEP Document Code. i

Table 0‑2: Project Delivery Manager. i

Table 0‑3:Document Authority. i

Table 0‑4: Document Revision Tracking. ii

Table 0‑5: Document Change Log. ii

Table 1‑1:Project Information Table (PIT_1). 1

Table 1‑2: Major Milestones/Brief Schedule Table. 2

Table 1‑3: BEP versions as per project phases list. 3

Table 2‑1: (FRA_2) Functions Responsibilities & Authorities (Individuals List). 4

Table 3‑1: BIM Goals / BIM Objectives. 6

Table 3‑2: BIM USES ACROSS PROJECT PHASES. 8

Table 3‑3: PRS _2: Procurement Route (Schema & Table). 9

Table 3‑4: Level of Information Need Classification Table (as per BIM Uses). 10

Table 3‑5: Supporting Information List (incl. Location). 10

Table 3‑6: Milestones Schedule (MIS_1, Including Explanations of Key Decision Point Decisions and Dates to be met) 14

Table 3‑7: Shared Resources Folder. 15

Table 3‑8: REF_1: Project’s reference information and shared resources. 16

Table 3‑9: EXAMPLE OF AN INFORMATION CONTAINER DEVELOPMENT IN CDE (AS A GUIDE). 18

Table 3‑10: Plan of Training. 19

Table 4‑1: FILE, & SHEET CODE /FILE (FOR PUBLICATION OF THE SHEET) NAME. 20

Table 4‑2: Project Designators. 21

Table 4‑3: Originator (Design Phases) Designators. 21

Table 4‑4: Zone & Sub-Zone Designators. 21

Table 4‑5: Level Designators. 22

Table 4‑6: File Type Designators. 22

Table 4‑7: Discipline Designators (Excluding MEP). 23

Table 4‑8: Discipline Designators (MEP). 24

Table 4‑9: Sheet/View Naming. 24

Table 4‑10: Workset Naming. 24

Table 4‑11: Number Designator. 25

Table 4‑12:Project's Classification System.. 26

Table 4‑13: Revision Control 26

Table 4‑14: Status codes for information containers within the CDE. 27

Table 4‑15: Metadata Assignment. 27

Table 4‑16: Application of Status Codes. 27

Table 4‑17: Model Description Document Template. 28

Table 4‑18: Exchange Formats Table. 29

Table 4‑19: COBie DATA.. 29

Table 4‑20: Classification and COBie. 30

Table 4‑21: Information to be excluded from or included in information models table. 30

Table 4‑22: Project's IFC Standards Table. 30

Table 4‑23: Main MVDs of The Project. 31

Table 4‑24: Method of assignment for Level of Information Need Table. 34

Table 4‑25: Units and Measurement. 35

Table 4‑26: Level of Accuracy Table (LOA). 35

Table 4‑27: Sheet Sizes. 36

Table 5‑1: Coordinates and Geo-Location Table (SCO). 40

Table 5‑2:Federation Parts List (Sample). 41

Table 5‑3: Survey Strategy. 42

Table 5‑4: Security & Extranet Access, Distribution Authority. 43

Table 5‑5: BIM Test Mock-Ups Table. 45

Table 5‑6: Meeting Schedule. 45

Table 6‑1: Appointment Document RACI Table. 50

Table 6‑2: (KPIS) Key Performance Indicators. 51

Table 8‑1: (SCH-IT_1) Schedule of Software, Hardware & IT. 56

LIST OF FIGURES

Figure 3‑1: Library Structure. 15

Figure 3‑2: CDE concept in ISO 19650-1. 17

Figure 3‑3: Revision control during Work in Progress (WIP). 17

Figure 3‑4: Revision control of Shared information. 17

Figure 3‑5: Revision control of Published information containers. 18

Figure 3‑6: Figure of the schema illustrating the development process mentioned in Table 3.9. 18

Figure 3‑7: Project's Folder Structure in Cloud. 19

Figure 3‑8: Project's Folder Structure in local servers of the actor. 19

Figure 4‑1: Process Map - Exchange of Information Between within the Apop's Organization. 31

Figure 4‑2: Process Map - Exchange of Information Between the Apop and External Stakeholders. 32

Figure 4‑3: Process Map - Exchange of Information Between Apop and External Operators or Maintainers. 32

Figure 4‑4: Process Map - Exchange of Information Between Peap and the App. 33

Figure 4‑5: Process Map - Exchange of Information Between PEAPs on the Same Project. 33

Figure 4‑6: Process Map - Exchange of Information Between Independent Projects. 34

Figure 5‑1: PIM Origin & Orientation. 40

Figure 5‑2: Information Container Breakdown of the Federation Strategy. 41

Figure 5‑3: Quantity extraction & tracking strategy. 42

Figure 5‑4: Modelling Process/Workflow Schema. 44

Figure 6‑1: Project's Brief Process Map. 53

1 OVERVIEW & INTRODUCTION

1.1 INTRODUCTION

? Purpose of this BEP document.

.....

1.2 LIST OF ABBREVIATIONS

v APOP: APPOINTING PARTY

v LEAP: LEAD APPOINTED PARTY

v PEAP: PROSPECTIVE LEAD APPOINTED PARTY

v APP: APPOINTED PARTY

v ...

v ...

v

1.3 PROJECT INFORMATION (PIT_2)

I Ref.to ISO-19650-2/5.1.6, 5.2.2

Project Name	..........
Asset Owner	..........
Project Owner/ Client	..........
Appointing Party	..........
Project Location and Address	..........
Project Code/Number(s)	..........
Contract Type / Delivery Method	..........
Brief Project Description	..........
Additional Project Description	..........
Asset Type	..........
Asset Structure	..........
Design Start Date	..........
Construction Start Date	..........
Handover Date	..........
Estimated Asset Area (Gross)	..........
Estimated Asset Area (Net)	..........
Estimated Asset Value	..........
..........	..........
..........	..........
..........	..........
..........	..........
..........	..........

Table 1‑1:Project Information Table (PIT_1)

1.4 MAJOR PHASES OR MILESTONES / BRIEF SCHEDULE

? Only major phases and/or milestones will be mentioned.

MAIN PHASE	OMNICLASS -Table 31	CODE	DEFINITION	START DATE	FINISH DATE	STATUS- Ended/Started
PREPARATION	31-10 00 00 Inception	A	Appraisal /  Strategic Definition	-	-
	31-20 00 00 Conceptualization	B	Design Brief/ Conceptual Design	-	-
DESIGN	31-30 00 00 Criteria Definition	C	Schematic Design	-	-
	31-40 00 00 Design	D	Design Development	-	-
		E	Technical Design	-	-
PRE-CONSTRUCTION	31-50 00 00 Coordination	F1	Production Information- Construction Documents	-	-
		F2-5	Production Information- Review, Comments for Tender Document Process & Site Safety Project Approval	-	-
		F6-G	Tender Documentation	-	-
		H	Tender Action	-	-
CONSTRUCTION	31-60 00 00 Implementation	J	Mobilization	-	-
		K1	Shop Drawing Phase-Start (In line with executions)	-	-
		K2	Construction Start -Excavation	-	-
		K3	Construction Works (Foundation Pouring Start)	-	-
		K4	Substantial Completion	-	-
		K5	Construction Completion	-	-
HANDOVER/ CLOSE OUT	31-70 00 00 Handover / Closeout	K6-7	Handover / Close-out , Data Drop-5	-	-
OPERATIONS	31-80 00 00 Operations	L	USE-Post Practical Completion	-	N/A
		M	R&D-Model Maintenance & Development	N/A	N/A
CLOSE-OUT	31-90 00 00 Closure	Z	Demolition	N/A	N/A

Table 1‑2: Major Milestones/Brief Schedule Table

1.5 BEP USE

I BEP will be reviewed and updated/revised at the end of each phase (ref.to Milestones List) as per the outputs during the process and effects of the outputs on the further activities. BEP versions related to phases will be listed.

PHASE or MILESTONE

BEP VERSION

DATE

Table 1‑3: BEP versions as per project phases list

1.6 EXECUTIVE SUMMARY

? Executive summary will be written after finishing the BEP.

.....

2 INFORMATION MANAGEMENT INDIVIDUALS

I Ref. to ISO-19650-2/5.4.1: confirm the names of the individual(s) who will undertake the information management function within the delivery team and ref. to ISO 19650-2/5.1.1, Include any agreed changes from "Tender Response" Package. Ref. to ISO 19650-2/5.3.1, 5.3.2

Ú Documents:

4 OIR: Organizational Information Requirements

4 FRA_1: Functions Responsibilities & Authorities (Individuals List)

4 REM-A_2: Information Management Assignment Matrix-(Responsibility Matrix-Information Management Activities)

2.1 FUNCTIONS RESPONSIBILITIES & AUTHORITIES (INDIVIDUALS LIST)-FRA_2

? Project Information Management Functions, Task Information Management Functions, Asset Information Functions: (asset information management should be involved in all stages of project delivery as defined in Table 1, Refer to ISO 19650-1/7.2).

ACTOR ROLES				ACTOR
Functional	Omniclass Table 33	Professional	Omniclass Table 34	RESPONSIBLE PARTY			CONTACT INFO
				Abbr.	Description	Name	e-mail	phone
						Company/ Individual
e.g. Task Team Information Man.		e.g. Architect

Table 2‑1: (FRA_2) Functions Responsibilities & Authorities (Individuals List)

2.2 INFORMATION MANAGEMENT ASSIGNMENT MATRIX (REM-A_3)

I Ref. to ISO-19650-2/Annex-A (Note: It is also called as Responsibility Matrix-Information Management Activities or Information management . responsibility matrix)

I Ref.to ISO-19650-1/3.1.1: responsibility matrix: chart that describes the participation by various functions in completing tasks or deliverables [SOURCE: ISO 37500:2014, 3.16 – modified]. Note 1 to entry: A responsibility matrix can indicate accountability, consultation and informing, alongside the obligation to complete tasks or deliverables.

I Ref.to ISO-19650-1/10.3: A responsibility matrix should be generated as part of the information delivery planning process in one or more levels of detail. The axes of a responsibility matrix should identify:

· information management functions; and

· either project or asset information management tasks, or information deliverables as appropriate.

The content of a responsibility matrix should show the appropriate detail relevant to the axes.

Refer to below document (under folder: Delivery_IMDocs/BEP):

Annex_2.1 = REM-A_3: Information Management Assignment Matrix

3 UPDATED REQUESTS & INFORMATION FROM INVITATION TO TENDER & TENDER RESPONSE PACKAGES

I Refer to Cl.4 for "Information Standard", and Cl. 5 for "Information Production Methods and Procedures"

Ú Documents:

4 EIR-APOP: Appointing Party's Exchange Information Requirements

4 REF_1: Project’s reference information and shared resources

4 TEN-CR: Tender Response Requirements & Evaluation Criteria

4 MIS_1: Milestones List (Including detailed description of the information at each key decision point)

4 INS_1: Project's Information Standard

4 PMP_1: Project's Information Production Methods and Procedures

4 INP_1: Project's Information Protocol

4 OIR: Organizational Information Requirements

4 PIR: Project Information Requirements

4 AIR: Asset Information Requirements

4 ACR: Acceptance Criteria Manual

4 RAS_1: Risk Assessment Requirements

4 COL-PP: Collaboration Process & Procedures (within the CDE)

4 LOIN: Level of Information Need Manual

4 LOA: Level of Accuracy Table

4 CDE-SMP_1: Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Req.s and COL-PP)

4 LIB_1: Library Guide & Library Structure in Data Environment

4 SHR_1: Shared Resources Guide & Shared Resources in Data Environment

4 PoW_1: Plan of Work

4 INP_1: Project's Information Protocol

4 REF_1: Project’s reference information and shared resources

4 AAP: APOP Assurance Processes

4 QUA: Quality Assurance, Coordination & Issue Management Manual

4 SUP: Supporting Information for LEAP

4 PSC: Project's Schedule from Project Plan

3.1 APPOINTING PARTY'S EXCHANGE INFORMATION REQUIREMENTS

I Refer to Cl.3.2 for "Reference Information & Shared Resources", Cl.6.1.2 for "Acceptance Criteria", Cl.4 for "Information Standard", Cl.5 for "Information Production Methods and Procedures" .

....

3.1.1 APPOINTING PARTY'S INFORMATION REQUIREMENTS (INCL. UPDATES)

I Establish the appointing party’s information requirements to be served during the appointment, and in doing so shall consider their OIR, PIR and AIR. (ref. to. ISO 19650-2/5.2.1)

I Include updates from PIR content. Include handover requirements with referring to AIR.

I PIR explain the information needed to answer or inform high-level strategic objectives within the appointing party in relation to a particular built asset project. PIR are identified from both the project management process and the asset management process. A set of information requirements should be prepared for each of the appointing party’s key decision points during the project. Repeat clients may develop a generic set of PIR that can be adopted, with or without amendment, on all of their projects. (Ref. to ISO-19650-1/5.4).

Refer to:

Ú Documents:

4 PIR: Project Information Requirements

Refer to: (under folder: Delivery_IMDocs)

Appendix_3.1 = OIR: Organizational Information Requirements

Appendix_3.2 = AIR: Asset Information Requirements

3.1.1.1 THE PROJECT SCOPE

3.1.1.1.1 BIM GOALS (CONDITIONS of STATISFACTION-CoS) / BIM OBJECTIVES

? Describe how BIM is used to achieve specific project goal at different stages of the project.

? Following table is presented to describe how BIM is used to achieve specific project goal at different stages of the project.

PRIORITY (high/med./low)

GOAL (CoS) DESCRIPTION

BIM USES

Table 3‑1: BIM Goals / BIM Objectives

3.1.1.2 THE INTENDED PURPOSE

? The intended purpose for which the information will be used by the appointing party.

....

3.1.1.2.1 PROJECT'S BIM USES

? List of expected BIM use cases and deliverables for each BIM use. Include value added use cases and deliverable.

Ú Refer to: (below documents are under folder: Delivery_IMDocs/BEP)

Annex_7.1 = HLRM_1: Delivery team’s High Level Responsibility Matrix

Annex_7.2 = DRM_0: Delivery Team’s Detailed Responsibility Matrix

Annex_3.3 = USE_2: BIM USE MATRIX

Annex_3.4 = BUA_2: BIM USE ANALYSIS

....

BIM USES ACROSS PHASES

BIM USE NO

BIM USE NAME

Appraisal

Conceptual Design

Schematic Design

Design Development

Technical Design

Production Info.- Construction Doc.

Production Inf.-Rev. Site &Safety Project

Tender Doc.

Tender Action

Mobilization

Construction (incl. Shop Drawing)

Handover/Close-out

USE

R&D-Model Maintenance & Development

Demolition

A

B

C

D

E

F1

F2-6

G

H

J

K1-5

K6-7

L

M

Z

1A

Existing Conditions Modeling

1B

Existing Conditions Modeling_ Surrounding Site Modeling

1C

Existing Conditions Modeling_ Geo-technical, Environmental

2A

5D Cost Estimation (Quantity takeoff & Detailed Estimating) & Cost Man.

2B

5D Budgetary Cost Model

3

4D Planning, Scheduling & Construction Sequencing

4

Site Analysis

5

Programming (Spatial Program Validation)

6

Bespoke BIM object library authoring

7

Design Reviews

8

Code Validation_ IBC International Building Code

9

Code Validation_ ADA Guidelines Verification

10

Engineering Analysis_Sustainability Evaluation (Leed Evaluation/ Leed Credit Documentation)

11

Engineering Analysis_Lighting Analysis (Daylight integration)

12

Engineering Analysis_Energy Analysis (Energy Modeling, Sun Studies, Daylight Analysis)

13

Engineering Analysis_Structural An.

14

Engineering Analysis_Mechanical A.

15

Engineering Analysis_Geotechnical

16

Environmental (Passive) Analysis

17

Fire Safety-Active (Code Validation /Analysis and Report with Proposals, Constultancy)

18

Fire Safety-Passive (Code Validation/Analysis and Report with Proposals, Constultancy)

19

Acoustical Analysis & Sound Rating Modeling

20

Design Authoring_Architectural

21

Design Authoring_Structural / Construction System Design

22

Design Authoring_Mechanical

23

Design Authoring_ Fire Protection (Mechanical)

24

Design Authoring_Plumbing

25

Design Authoring_Electrical (including Fire Alarm)

26

Design Authoring_Civil Engineering

27

Design Authoring_Landscape

28

Elevator (& Escalator) Planning & Des.

29

Zone Analysis and Zonning

30a

Facade Design (& Engineering)- Computational & Parametric Des.

30b

Facade Design (& Engineering)- Wind Test & Analysis

30a

Facade Design (& Engineering)- Structural Calculations

30b

Facade Design (& Engineering)- Computational&Parametric Det.Des.

30a

Facade Design (& Engineering) -For Manufacturing

31

Value Engineering Value Management&Design Optimization (&Tenant/Operator Build Out)

32

COBie Data Set/COBie Deliverables

33

Construction Drawing Production

34

3D Coordination/Clash Avoidance, Detection, Issue Management

35

3D Control and Planning & In Field Construction Lay-Out

36

Shop Model and Drawing Coordination, Submittals

37

Digital Fabrication

38

Mechanical/ Equipment Maintenance Clearance,Space Mod.

39

Site Utilization Planning/ Site Logistics and Safety

40

As-Built Model

41

Commissioning

42

Record Modeling

43

Agency-Marketing/Disposal to Market

44

Pedestrian simulation (hazard & dwell)

45

Emergency Management (Security assessment& disaster planning)

46

Space Planning/Management and Tracking-Move Management

47

Asset Management

48

Building System Analysis (Operational)

49

Building (Preventative) Maintenance Scheduling

50

Model for Maintenance Training

51

Building System Automation (BSA) Integration

Table 3‑2: BIM USES ACROSS PROJECT PHASES

3.1.1.3 THE INTENDED PROCUREMENT ROUTE (PRS_2)

? The Intended Procurement Route will be mentioned as schema (or table) with a short description of the organization.

.....

Table 3‑3: PRS _2: Procurement Route (Schema & Table)

3.1.1.4 PLAIN/PRE-QUALIFICATION QUESTIONS (PLQ_1)

? How to use PLQ_1 will be mentioned. For each task team's self-assessment or for future possible assessment of actors such as sub-contractors PLQ_1 will be used.

? Project specific most important Plain/Pre-Qualification Questions will be highlighted with referring to Annex_3.5.

.....

Ú Refer to: (under folder: Delivery_IMDocs)

Appendix_3.5 = PLQ_1 : Plain/Pre-Qualification Questions

3.1.2 LEVEL OF INFORMATION NEED MANUAL (LOIN_2)

? Ref. to ISO-19650-2/5.2.1.b. Ref. to ISO-19650-1/3.3.16 (Level of Information Need: Framework which defines the extent and granularity of information. Note 1 to entry: One purpose of defining the level of information need is to prevent delivery of too much information.)

Ref. to ISO-19650-1/11.2:

· The level of information deliverable should be determined according to its purpose. This should include the appropriate determination of quality, quantity and granularity of information. This is referred to as its level of information need and this can vary from deliverable to deliverable.

· A range of metrics exist to determine levels of information need. For example, two complementary but independent metrics can define the geometrical and alphanumerical content in terms of quality, quantity and granularity. Once these metrics have been defined, they should be used to determine the levels of information need across the whole project or asset. All this should be described clearly within the OIR, PIR, AIR or EIR.

· The levels of information need should be determined by the minimum amount of information needed to answer each relevant requirement and no more. Anything beyond this minimum is considered as waste. Lead appointed parties should consider the risk that importing object information automatically into information models might introduce a higher level of information need than is required.

· The relevance of an information deliverable is not always correlated to its granularity. Level of information need is, however, closely linked to the federation strategy

· The granularity of alphanumerical information should be considered to be at least as important as that of geometrical information.

? Mention main objectives of "Level of Information Need" to be used in the project with referring to LOIN_2

....

Ú Refer to:

Annex_7.1 = HLRM_1: Delivery team’s High Level Responsibility Matrix

Annex_7.2 = DRM: Delivery Team’s Detailed Responsibility Matrix (Initial/Template)

Refer to (under folder: Delivery_IMDocs/BEP) below doc. for the desc. of each "Level of Information Need" in detailed.

Annex_3.6 = LOIN_2: Level of Information Need Manual

I Existing metrics: LOMD (Level of Model Definition) = LOD(Level of Model Detail)+LOI(Level of Model Information) / LOD (Level of Development): 

I Table 3.4 below will be updated as per CEN/TC 442-prEN17412 Level of Information Need Standard (when it is available)

	LOMD		LOD		DEFINITION
	LOD	LOI	LOG	LOI
LOMD1/LOD100					Pre-Design Phase (Symbolic-Brief)
LOMD2/LOD100					Conceptual
LOMD3/LOD200					Schematic Design Phase (Generic-Definition)
LOMD4/LOD300					Design Development
LOMD5/LOD350					Construction Documents by Disciplines for Bidding
LOMD6/LOD400					Shop Drawing (During construction-Build&Commission)
LOMD2/LOD500					As Built & Operations (As Built)

Table 3‑4: Level of Information Need Classification Table (as per BIM Uses)

3.1.3 SUPPORTING INFORMATION FOR LEAP(SUP-LEAP_1)

? Ref. to ISO-19650-2/5.2.1.d "The supporting information that the prospective lead appointed party might need, to fully understand or evaluate each information requirement or its acceptance criteria. When establishing this existing asset information, shared resources, supporting documents or guidance material, references to relevant international, national or industry standards, and exemplars of similar information deliverables will be taken into consideration.

.....

NO	FILE NAME	DESCRIPTION	FOLDER IN CDE
1
2
3
4
5

Table 3‑5: Supporting Information List (incl. Location)

3.1.4 MILESTONES SCHEDULE (MIS_2-INCLUDING DETAILED DESCRIPTION OF THE INFORMATION AT EACH KEY DECISION POINT)

Ú Refer to: ISO-19650-2/5.2.1.e, PSC: Project's Schedule from Project Plan

? In the below table following information was mentioned for your kind consideration;

· dates that each requirement has to be met with regarding the time needed by the appointing party to review and accept information and the appointing party’s internal assurance processes (ref. to. ISO 19650-2/5.2.1.e)

· detailed description of the information at each of the key decision point (Ref .to ISO-19650-2/5.1.2, 5.1.3, 5.2.1)

I For detailed Plan of Work please review and apply to; (under folder: Delivery_IMDocs)

Appendix_3.7 = PoW-1: Plan of Work (with Milestones & Dates)

MILESTONES (& DETAILED PHASES) & KEY DECISION POINTS SCHEDULE
MAIN PH.		CODE		DEFINITION	KEY DECISION POINT		START DATE DD/M/YY	FINISH DATE DD/M/YY	STATUS End/ Start
					CODE	DEFINITION
PREPARATION	INCEPTION	A		Appraisal / Strategic Definition	-	-	../Jan/..	../m/..	Start
	CONCEPTUAL DESIGN	B	1	Proceed to Conceptual Design	KDP-1	Decision & Comments for to proceed on Conceptual Des.	../m/..	../m/..	..
		B	2	Design Brief/Conceptual Design	-	-	../m/..	../m/..	..
		B	3	*Data Drop 1			../m/..	../m/..	..
		B	4	Approval: Design Notice to Proceed	KDP-2	Apop's Approval and comments for to start Schematic Design ("Basic Project” contract agreement)	../m/..	../m/..	..
		B	5	-	KDP-3	Basic MEP Design Criterias Decision	../m/..	../m/..	..
		B	6	*Data Drop 1 Package Update Comments of APOP & MEP criteria decisions are added.			../m/..	../m/..	..
DESIGN	SCHEMATIC DESIGN	C	1	Schematic Design	-	-	../m/..	../m/..	..
		C	2	*Data Drop 2			../m/..	../m/..	..
		C	3	Approval (Appointing Party): Design Notice to Proceed	KDP-4	Apop's Approval & Comments for to start Design Development	../m/..	../m/..	..
		C	4	Local Public Authority: Interview with local authorities	-	-	../m/..	../m/..	..
		C	5	Update of MEP Design Criterias & Apop's Comments as per the interviews with Local Authorities	KDP-5	Updated MEP Design Criteria & Comments	../m/..	../m/..	..
		C	6	*Data Drop 2 Package Update according to C5			../m/..	../m/..	..
		C	7	Approval (Local Public Authority): Design Notice to Proceed	KDP-6	Approval from Local Public Authorities for to start Design Development Process	../m/..	../m/..	..
	DESIGN DEVELOPMENT	D	1	Design Development Start	-	-	../m/..	../m/..	..
		D	1a	Design Development Check Point - %25 completion	-	-	../m/..	../m/..	..
		D	1b	Design Development Check Point -%50 completion	-	-	../m/..	../m/..	..
		D	1c	Design Development Check Point - %75 completion	-	-	../m/..	../m/..	..
		D	1d	Design development completion	-	-	../m/..	../m/..	..
		D	2	*Data Drop 3	-	-	../m/..	../m/..	..
		D	3	Approval (Appointing Party): Design Notice to Proceed	KDP-7	Apop's Approval & Comments for to start Technical Design Process	../m/..	../m/..	..
		D	4	Approval (&Comments): from Local Building Authority/Application for detailed planning permission	KDP-8	Comments from Local Building Authority	../m/..	../m/..	..
		D	5	*Data Drop 3 Package Update according to D3&D4			../m/..	../m/..	..
	TECHNICAL DESIGN	E	1	Technical Design-Start	-	-	../m/..	../m/..	..
		E	1a	Technical Design- Check Point %25 completion	-	-	../m/..	../m/..	..
		E	1b	Technical Design- Check Point %50 completion	-	-	../m/..	../m/..	..
		E	1c	Technical Design- Check Point %75 completion	-	-	../m/..	../m/..	..
		E	1c	Technical Design- Completion	-	-	../m/..	../m/..	..
		E	2	*Data Drop 4			../m/..	../m/..	..
		E	3	Approval (Appointing Party): Design Notice to Proceed	KDP-9	Apop's Approval & Comments for to start Construction Documents Process	../m/..	../m/..	..
		E	4	Local Public Authority: Interview with local authorities	-	-	../m/..	../m/..	..
		E	5	*Data Drop 4 Package Update according to E3 & E4			../m/..	../m/..	..
PRE-CONSTRUCTION	CONSTRUCTION / IMPLEMENTATION DOCUMENTS	F	1	Production Information- Construction Documents-Start	-	-	../m/..	../m/..	..
		F	1a	Construction Documents Check Point -01	-	-	../m/..	../m/..	..
		F	1b	Construction Documents Check Point -02	-	-	../m/..	../m/..	..
		F	1n	Construction Documents Check Point -n	-	-	../m/..	../m/..	..
		F	2a	Production Information: Construction Documents End & Getting the OCTis Report	-	-	../m/..	../m/..	..
		F	2b	*Data Drop 5		CONSTRUCTION DOCUMENTS	../m/..	../m/..	..
		F	3a	Approval (Appointing Party): Design Notice to Proceed	KDP-10	Apop's Approval & Comments for to start application for statutory approvals	../m/..	../m/..	..
		F	3b	Update as per Apop's Comments	-	-	../m/..	../m/..	..
		F	4	Approval (Local Building Authority) Application for statutory approvals & the Building License	KDP-11	Statutory approvals & Receiving the Building License	../m/..	../m/..	..
		F	5	*Data Drop 5 Package Update according to F3b & F4		CONSTRUCTION DOCUMENTS-UPDATE	../m/..	../m/..	..
	TENDER DOCUMENTATION	F	6a	Production Information- Final Review by all parties and final comments for tender documentation process	-	-	../m/..	../m/..	..
		F	6b	Approval (Appointing Party): Notice to Proceed	KDP-12	Approval for proceed on tender documentation & Site Safety	../m/..	../m/..	..
		F	6c	Site Safety Project Approval	KDP-13	Aproval by Apop & Local Public Authority	../m/..	../m/..	..
		G		Tender Documentation	-	-	../m/..	../m/..	..
		H	1	Tender Action	-	-	../m/..	../m/..	..
		H	2	Tender Action- Approval	KDP-14	Apop's Approval&Comments (Approval with notes)	../m/..	../m/..	..
		H	3	*Data Drop 6 (Updated as per F6a-H3)		TENDER DOCUMENTS PACKAGE	../m/..	../m/..	..
CONSTRUCTION	MOBILIZATION	J	1	Construction Bid Received	KDP-15	Bid approval by Apop/Client	../m/..	../m/..	..
		J	2	Approval Local Public Authority: Construction Notice to Proceed	KDP-16	Approval of the “Construction Area” (requested by the Construction Com./GC) by Local Public Authority	../m/..	../m/..	..
		J	3a	Mobilization	-	-	../m/..	../m/..	..
		J	3b	Apop/Leap Decision Note: It is recommended to involve Architect in Administration of Construction to Practical Completion Proces	KDP-17	Decision for shop drawing responsibilities and construction administration	../m/..	../m/..	..
	SHOP DRAWINGS AND CONSTRUCTION	K	1	Shop Drawing Phase -Start (In line with executions-In each check point necessary approvals from Apop will be taken for further executions)	-	Approval (by Apop) of Shop Drawing Package Part- 1	../m/..	../m/..	..
		K	2	Construction Start-Excavation	KDP-18	Approval (by Apop) of Shop Drawing Package...	../m/..	../m/..	..
		K	3	Construction Works (Foundation Pouring Start)	KDP-19	Approval (by Apop) of Shop Drawing Package...	../m/..	../m/..	..
		K	3a	Construction Works Check Point-A1 (to be determined special for the project)	KDP-20a	Approval (by Apop) of Shop Drawing Package...	../m/..	../m/..	..
		K	3b	Construction Works Check Point-A2 (to be determined special for the project)	KDP-20b	Approval (by Apop) of Shop Drawing Package...	../m/..	../m/..	..
		K	3n	Construction Works Check Point-An (to be determined special for the project)	KDP-20n	Approval (by Apop) of Shop Drawing Package Part-N	../m/..	../m/..	..
		K	4a	Substantial Completion- Construction Works Check Point -B1 (to be determined special for the project) Including Shop Drawings Completion	KDP-21	Completion of the approvals (by Apop) of all Shop Drawing Package	../m/..	../m/..	..
		K	4b	*Data Drop 7		SHOP DRAWING PACKAGE
		K	4c	Construction Works Check Point -B2 (to be determined special for the project)	-	-	../m/..	../m/..	..
		K	4n	Construction Works Check Point -Bn (to be determined special for the project)	-	-	../m/..	../m/..	..
		K	5	Construction Completion	-	-	../m/..	../m/..	..
HANDOVER/CLOSE OUT		K	6	Handover / Close-out: Appointing Party Comments	KDP-25	Inspection & Comments by Apop	../m/..	../m/..	..
		K	7a	Handover / Close-out: Construction Work Revisions as per comments	-	-	../m/..	../m/..	..
		K	7b	*Data Drop 8		AS BUILT	../m/..	../m/..	..
		K	7c	Approval (Appointing Party): Design Notice to Proceed	KDP-26	Apop's Approval & Comments for to start application for statutory approvals	../m/..	../m/..	..
		K	7d	*Data Drop 8 Package Update according to K7c		AS BUILT-UPDATE	../m/..	../m/..	..
		K	7e	Approval (Appointing Party & All Parties): Notice to Acceptance	KDP-27	Acceptance Certificate (construction completion document) drafted and signed by all the parties involved in the construction.	../m/..	../m/..	..
OPERATIONS	USE (POST PRACTICAL COMPLETION)	L	1	OPERATION/USE-Post Practical Completion: Administration of the building contract after Practical Completion and making final inspections.	-	-	../m/..	../m/..	..
		L	2	*Data Drop 9 OPERATION/USE: Update BIM Data		PIM to AIM	../m/..	../m/..	..
		L	3	OPERATION/USE:Apop's/Operator's Approval	KDP-28	Apop/Operator Notice to Proceed Facility Management	../m/..	../m/..	..
		L	4	OPERATION/USE-Post Practical Completion: Assisting building user during initial occupation period.	-	-	../m/..	../m/..	..
	MAINTENANCE&DEVELOPMENT	M	1a	R&D-Model Maintenance & Development	-	-	../m/..	../m/..	..
		M	1b	*Data Drop 10		AIM TO PIM	../m/..	../m/..	..
		M	2a	Renovation Decision-1 &Re-Life Cycle	KDP-29	Renovation Decision-1	../m/..	../m/..	..
		M	2b	*Data Drop 11		AIM TO PIM	../m/..	../m/..	..
		M	2n	Renovation Decision-n &Re-Life Cycle	KDP-N	Renovation Decision-n	../m/..	../m/..	..
		M	2n	*Data Drop n		AIM TO PIM	../m/..	../m/..	..
Closure		Z		Closure/Demolition	-	-	../m/..	../m/..	..

Table 3‑6: Milestones Schedule (MIS_1, Including Explanations of Key Decision Point Decisions and Dates to be met)

3.2 REFERENCE INFORMATION & SHARED RESOURCES (REF_2)

I Please refer to "PIT_1" for "Project Information" & Ref. to. ISO 19650-2/5.1.6, 5.2.2)

Ú Documents:

4 LIB_1: Library Guide & Library Structure in Data Environment

4 SHR_1:Shared Resources Guide & Shared Resources in Data Environment

.....

3.2.1 LIBRARY GUIDE & LIBRARY STRUCTURE IN DATA ENVIRONMENT (LIB_2)

? Mention how to use the library, library structure, how to create new objects and how to use the existing ones, exception rules, library procedures..

.....

Figure 3‑1: Library Structure

3.2.2 SHARED RESOURCES GUIDE & SHARED RESOURCES IN DATA ENVIRONMENT (SHR_2)

? Mention how to use shared resources, shared resources folder structure, who will do what to have a proper shared resource and which shared resource is appropriate to use and current, the procedures.

.....

SHARED RESOURCES FOLDER
XXXXXX/06-RESOURCE/SHARED_RESOURCES FOLDER CONSISTS OF THREE SUB-FOLDERS MENTIONED BELOW
ARCHIVE Old resources files will be archived in separate sub-folders folders as per dates. Sub-folder:YYYY/MM/DD	SHARED (Responsible party will share the file first here. If the file needs review by all parties (such as new survey).	PUBLISHED (Development plan Legal Documents of Site. etc)

Table 3‑7: Shared Resources Folder

3.2.3 PROJECT’S REFERENCE INFORMATION AND SHARED RESOURCES (REF_2)

? With referring to LIB and SHR mention all the procedures related to REF.

.....

NO	FILE NAME	DESCRIPTION	REVISION (METADATA)	FOLDER IN CDE
1
2
3
4

Table 3‑8: REF_1: Project’s reference information and shared resources

3.3 PROJECT'S INFORMATION PROTOCOL RELATED REQUIREMENTS

I Ref.to ISO-19650-2/5.1.8: The appointing party shall establish the project’s information protocol, as defined below, including any associated license agreements, which will, subsequently and appropriately, be incorporated into all appointments. In doing this, the appointing party shall consider:

specific obligations of the appointing party, prospective lead appointed parties and prospective appointed parties relating to the management or production of information, including the use of the project’s common data environment;

· any warranties or liabilities associated to the project information model; background and foreground intellectual property rights of information; the use of existing asset information; the use of shared resources; the use of information during the project, including any associated licensing terms; and the re-use of information following the appointment or in the event of termination.

Ú Refer to: (under folder: Delivery_IMDocs)

Appendix_3.8 = INP_2: Project’s Information Protocol

? Mention most important, crucial protocol items which every single user should be aware of.

? Mention the items which are changing during BEP's evolution throughout the phases, milestones.

.....

3.3.1 PROJECT'S COMMON DATA ENVIRONMENT STANDARDS, METHODS & PROCEDURES (CDE_2)

I Ref. to ISO-19650-2/5.1.7: The appointing party shall establish (implement, configure and support) the project’s common data environment (CDE) to serve the overall requirements of the project and to support the collaborative production of information. The project’s common data environment shall enable:

a) each information container to have a unique ID, based upon an agreed and documented convention comprised of a number of fields separated by a delimiter;

b) each field to be assigned a value from an agreed and documented codification standard;

c) each container to have the following attributes assigned:

· status (suitability); revision (and version); classification (in accordance with the framework defined in ISO 12006-2)

d) the ability for information containers to transition between states;

e) the recording of the name of user and date when information container revisions transition between each

state; and

f) controlled access at an information container level.

It is strongly recommended that the project CDE is in place prior to issuing the invitation to tender, so that information can be shared with tendering organizations in a secure manner.

The appointing party can also appoint a third-party to host, manage or support the project’s CDE. In this case, it is recommended that this is done as a separate appointment before procurement of any other appointed party starts. Or the appointing party can also, at a later date, appoint an appointed party to take over the hosting, management or support of the project CDE. In either case, it is recommended that the appointing party defines a functional and non-functional requirements specification.

? The structure of CDE created according to the ISO-19650 and standards mentioned in 3.3.1 and 4.4.2

.....

Figure 3‑2: CDE concept in ISO 19650-1

? Mention all standards, methods and procedures of CDE which will be used during the Life Cycle.

.....

Figure 3‑3: Revision control during Work in Progress (WIP)

Figure 3‑4: Revision control of Shared information

Figure 3‑5: Revision control of Published information containers

STEP	DESCRIPTION	STATE	REVISION	STATUS
0
1
2
3
4
5
6
..

Table 3‑9: EXAMPLE OF AN INFORMATION CONTAINER DEVELOPMENT IN CDE (AS A GUIDE)

Figure 3‑6: Figure of the schema illustrating the development process mentioned in Table 3.9

Figure 3‑7: Project's Folder Structure in Cloud

Figure 3‑8: Project's Folder Structure in local servers of the actor

3.3.2 TRAINING REQUIREMENTS (TRA_1)

I Ref. to ISO-19650-2/5.3.3, 5.3.5

? Explain the training requirements with referring to below table and mention the update conditions of the training plan.

.....

TRAINING SUBJECT

RELATED BIM USE (CODE)

TEAM TO BE TRAINED

INDIVIDUALS IN THE TEAM TO BE TRAINED (as number)

START DATE (dd/Mon/yy)

FINISH DATE (dd/Mon/yy)

Table 3‑10: Plan of Training

4 INFORMATION STANDARD (ıns_2)

I Ref.to ISO-19650-2/5.4.1: agree with the appointing party any additions or amendments to the project information standard).

I Ref.to ISO-19650-2/5.2.1, 5.2.4,

I Ref.to ISO-19650-2/5.3.2: f) In Pre-App. BEP include, any proposed additions or amendments to the project’s information standard that the delivery team require to facilitate the effective:

· exchange of information between task teams,

· distribution of information to external parties, or

· delivery of information to the appointing party;

I Ref.to ISO-19650-2/5.1.4: The appointing party shall establish any specific information standards required by the appointing party’s organization within the project’s information standard. In doing this, the appointing party shall consider:

a) the exchange of information:

· within the appointing party’s organization,

· between the appointing party and external stakeholders,

· between the appointing party and external operators or maintainers,

· between the prospective lead appointed party and the appointing party

· between prospective appointed parties on the same project, and

· between interdependent projects;

b) the means of structuring and classifying information;

c) the method of assignment for level of information need; and

d) the use of information during the operational phase of the asset.

I This section includes updates from "Invitation to Tender" and "Tender Response Packages"

Ú Documents:

4 REM-A_3: Information Management Assignment Matrix

4 FRA_2: Functions Responsibilities & Authorities (Individuals List )

4 PRS_2: Procurement Route (Schema & Table)

4 COL-PP: Collaboration Process & Procedures (within the CDE)

4 CDE_2: Project's CDE Structure, Standards, Methods, Procedures

4 (Incl. Security Requirements and COL-PP)

4 ICN_0: Information Container Naming Requirements

4 CLM: Project's Classification System & Metadata

I Construction tolerances for all disciplines are mentioned in Cl. 3.1.3

.....

4.1 INFORMATION CONTAINER NAMING REQUIREMENTS (ICN_2)

I Ref. to ISO-19650-1/3.3.12, ISO-19650-1/12.1, ISO 13567‑2

I Explain each type of information container naming requirement which will be used in the project.

I Mention each type of designator which will be used in the project. (Below examples were given.)

I Mention the method of naming rooms / areas, stairs, windows, doors and other element (Such as room naming will start from the staircase as clockwise etc.).

The revision and status are required to track the progression of a file or document to its completion and authorization. The revision and status code need to be part of the attributed metadata, not part of the file name. For "Metadata" please refer to Clause 4.2.2 below.

.....

PROJECT

ORIGINATOR (Design Phase)

VOLUME/ SYSTEM ZONE

SUB- ZONE

LEVELS & LOCATION

TYPE/ FILE TYPE

FUNCTION DISCIPLINE

NUMBER

DOCUMENT GROUP TYPE DESIGNATOR

NUMBER

111803

-

XXX

-

XXXX

-

XXXX

-

XX

-

XXX

-

XX

-

XX

XXXX

Table 4‑1: FILE, & SHEET CODE /FILE (FOR PUBLICATION OF THE SHEET) NAME

4.1.1 PROJECT DESIGNATORS

.....

DESCRIPTION	DESIGNATOR / NUMBER
PROJECT'S FULL NAME	M3BEPG11-Olympic_Tower
PROJECT'S CODE	M3BEPG11-OT
PROJECT'S NUMBER	111803

Table 4‑2: Project Designators

4.1.2 ORIGINATOR (DESIGN PHASES) DESIGNATORS

.....

Phase Code			DEFINITION
Classification (e.g.Omniclass Number)	Code (Ref.to. Table 1-2)
10		A	Appraisal / Strategic Definition
20		B	Design Brief/Conceptual Design
30		C	Schematic Design
40		D	Design Development
40		E	Technical Design
50		F	Production Information (Construction Documents, Review & Site-Safety Approval
50		G	Tender Documentation
50		H	Tender Action
60		J	Mobilization
60		K	Construction & Shop Drawings
70		K	Handover / Close-out
80		L	USE-Post Practical Completion
80		M	R&D-Model Maintenance & Development
90		Z	Demolition

Table 4‑3: Originator (Design Phases) Designators

4.1.3 ZONE & SUB-ZONE

.....

ZONE

SUB-ZONE

ZONE

SUB-ZONE

ZONE

SUB-ZONE

ZONE

SUB-ZONE

Table 4‑4: Zone & Sub-Zone Designators

4.1.4 LEVELS

.....

LEVEL	DESCRIPTION	LEVEL	DESCRIPTION	LEVEL	DESCRIPTION	LEVEL	DESCRIPTION
RF	ROOF	...	.....	...	.....	...	.....
...	.....	...	.....	...	.....	B2	Basement -2
...	.....	...	.....	01	1st Floor	B3	Basement -3
...	.....	...	.....	GF	Ground Fl.	B4	Basement -4
...	.....	...	.....	B1	Basement -1	FN	Foundation

Table 4‑5: Level Designators

4.1.5 FILE TYPE DESIGNATORS

.....

MAIN SHARED RESOURCES			MODELS /DRAWINGS
EIR	Exchange Information Requirements		M2D	2d Model File
OIR	Organizational Information Requirements		M3D	3d Model File
			COR	Coordination Model (Naviswork, Solibri) Clash Rendition
AIR	Asset Information Requirements		ANM	Animation (of the Model)
PIR	Project Information Requirements		VSM	Visualization File (of the Model)/ Model Rendition
INP	Project Information Protocol		VIS	Visualization File (Render)
BEP	BIM Execution Plan		COM	Federated/Combined Model
SUR	Surveys		DRW	2D Drawing
MODELS /DRAWINGS
BOQ		Bill of quantities	SCH	Schedule
CMT		Comments	SNL	Snagging List
COP		Correspondence	SPC	Specification
CSP		Cost Plan	STC	Structural Calculations
DBS		Database	TQS	Technical Survey
FNT		File Note	WCD	Work change directives
HSF		Health and Safety	ASI	Architectural supplemental instruction
MIA		Minutes /Action Notes	COR	Change order request
MOS		Method of Statement	CCD	Construction change directive
PPT		Presentation	COP	Change order proposal
PRG		Programme	DCVR	Design clarification verification request
RDT		Room Data Sheet	FDR	Field deficiency report
RFI		Request for Information	NCR	Nonconformance report
RPT		Report	CVN	Contract violation notice
SCA		Schedule of accommodation	ORS	Observation reports

Table 4‑6: File Type Designators

4.1.6 DISCIPLINE DESIGNATORS

.....

DISCIPLINE DESIGNATORS (EXCLUDING MEP)
DESIGNATOR		AS NUMBER		DESCRIPTION
LEVEL 1	LEVEL 2	LEVEL 1	LEVEL 2
SYSTEM	SUB-SYSTEM	SYSTEM	SUB-SYSTEM
Z	0	00	00	General (non-specific)
A	0	01	00	Architectural-All
A	F	01	00	Architectural-Facade Engineer
S	0	02	00	Structural-All
S	S	02	01	Strtuctural-Steel Structure
I	0	03	00	Interior Design (ers)
L	0	06	00	Landscape Architects
C	I	11	00	Civil-Infrasructure_Drainage/Waste Water Management
B	0	10	00	Building Surveyors
G	L	12	00	GIS, land surveyors
Q	S	13	00	Quantitiy Surveyors
K	0	20	00	Client
W	0	21	00	Contractor/Design Builder
X	0	22	00	Sub-contractor
Y	A	23	00	Acoustical Consultant /Analysis
Y	F	23	00	Fire Consultant/Engineer (Active and Passive)
Y	L	23	00	Lighting Consultant/Engineer
Y	E	23	00	Elevators & Escalators Sub-Contractor/Consultant
O	F	24	00	Operations-Facilities Manager

Table 4‑7: Discipline Designators (Excluding MEP)

DISCIPLINE DESIGNATORS (MEP)
DESIGNATOR		AS NUMBER		DESCRIPTION
LEVEL 1	LEVEL 2	LEVEL 1	LEVEL 2
SYSTEM	SUB-SYSTEM	SYSTEM	SUB-SYSTEM
M	-	04	00	MEP related general reports etc.
M	0	04	01	Mechanical-General (Calculations & Pre-Design All Mechanical)
M	E	04	02	Mechanical-Combined Services
M	A	04	03	Mechanical-HVAC_Air Conditioning
M	F	04	04	Mechanical-Fire Protection (Fire&Safety, Smoke Control)
M	H	04	05	Mechanical-HVAC_Heating
M	W	04	06	Mechanical-HVAC_Chilled Water & Refrigeration
M	V	04	07	Mechanical-HVAC_Ventilation
P	0	04	08	Plumbing-General (Calculations & Pre-Design All Plumbing)
P	P	04	09	Plumbing-Water Supply_Domestic/Potable Water System
P	H	04	10	Plumbing-Water Supply_Hot Water
P	D	04	11	Plumbing-Drainage (Sanitary Sewer Systems)
P	F	04	12	Plumbing-Fixtures
P	S	04	13	Plumbing-Storm/Rain Water
E	0	05	01	Electrical-General
E	A	05	02	Electrical-Public Adress
E	C	05	03	Electrical-Cable Routing/Cable Containment
E	D	05	04	Electrical-Low Current (IT & Communication, CCTV)
E	F	05	05	Electrical-Fire Detection (Fire Alarm) Systems
E	G	05	06	Electrical-Grounding/Earthing (Internal&External)
E	L	05	07	Electrical-Lighting
E	M	05	08	Electrical-Mechanical Systems' Electrical Services
E	P	05	09	Electrical-Lightning Protection
E	S	05	10	Electrical-Security & Access Control Systems
E	T	05	11	Electrical-Telecommunication
E	V	05	12	Electrical-Billing&Building Management
E	W	05	13	Electrical-Power Systems

Table 4‑8: Discipline Designators (MEP)

4.1.7 SHEET/SUBMITTAL DESCRIPTION-VIEW-WORKSET NAMINGS

.....

DISCIPLINE			ZONE		SUB- ZONE		FLOOR/ BUILDING PART NAME		TYPE
LEVEL 1	LEVEL 2
XX	XX	-	XXXX	-	XXXX	-	(e.g: Parking-1) (e.g:South)	-	(e.g: Floor Plan) (e.g:Elevation)

Table 4‑9: Sheet/View Naming

ZONE		SUB-ZONE		WORKSET DESCRIPTION (underscore in between)
XXXX	-	XXXX	-	(e.g: Interior_Wall)

Table 4‑10: Workset Naming

4.1.8 NUMBER DESIGNATORS

.....

NUMBER DESIGNATOR OF SHEETS & PUBLICATION FILES (PDF etc.) 2 Digits Document Group Type as number + 4 Digits as alphanumeric = 6 Digits
Sample= ...-A0-050011: 050011: 11th sheet of Architectural Details
DOCUMENT GROUP TYPE DESIGNATOR (MAIN DESIGNATOR)
00-09 will be used for all group types. Group Type Designator will be infront of these.
00	General:Symbol legend, abbreviation, general notes
01	Plans
02	Elevations
03	Sections
04	Large Scale Drawings
05	Details
06	Schedules and Diagrams
07	Reflected Ceiling Plans (RCP)
08	Flooring (Floor Pattern)
09	3D drawings
10-11 will be used for the type of submissions which are out of 0 to 9 content.
10	Special for Strtuctural Discipline
11	Special for MEP-HVAC&Gas
12	Special for MEP-Plumbing
13	Special for MEP-Fire
14	Special for Electrical
15	Special for Other Disciplines
16	Non drawing documents (Reports, Moms etc.)
17	Submissions as file (Revit Model, IFC etc.)

Table 4‑11: Number Designator

4.2 MEANS OF STRUCTURING & CLASSIFYING INFORMATION

I ISO 19650‑1 states that classification should be to a system in accordance with ISO 12006‑2.

.....

4.2.1 PROJECT'S CLASSIFICATION SYSTEM (CLM_1)

I Ref. to ISO-19650-1/3.3.13

I Ref. to ISO-19650-1/12.1: Each information container managed through the CDE should have metadata including:

· a revision code, in accordance with an agreed standard for example IEC 82045-1; and

· a status code, showing the permitted use(s) of information.

.....

Table 4‑12:Project's Classification System

4.2.2 METADATA

? Explain the metadata standards to be complied with. Below some sample information is mentioned.

.....

P	01	.	01
Letter for Prefix=P or C "P" represents preliminary (non-contractual) information containers. "C" represents contractual information containers.	Two numeric integer values representing the primary revision that will eventually be shared with other task teams in the delivery team	Two numeric integer values following a decimal point representing the WIP (Work in Progress) version of the primary revision.

Table 4‑13: Revision Control

CODE	DESCRIPTION	REVISION
Work In Progress (WIP)
S0	InitialStatus	Preliminary revision and version
Shared (non-contractual)
S1	Suitable for coordination	Preliminary revision
S2	Suitable for information	Preliminary revision
S3	Suitable for review and comment	Preliminary revision
S4	Suitable for stage approval	Preliminary revision
S5	Withdrawn*	N/A
S6	Suitable for PIM authorization	Preliminary revision
S7	Suitable for AIM authorization	Preliminary revision
Published (contractual)
A1,... An	Authorized and accepted	Contractual revision
B1,... Bn	Partial sign-off (with comments)	Preliminary revision
Published (for AIM acceptance)
CR	As constructed record document	Contractual revision

Table 4‑14: Status codes for information containers within the CDE

CONTAINER	METADATA
INFORMATION	DESCRIPTION	STATUS	REV. NO	AUTHOR	SUBMITTAL	CONTAINER CLASSIFICATION
CONTAINER NAME					DATE	CODE	DESCRIPTION
XXXXXX-XXX-XXXX-XXXX-XX-XXX-XX-XXXXXXX	************ ************	XX	XXX.XX	******* *******	DD/MM/YY	************ ************	************ ************

Table 4‑15: Metadata Assignment

Code	APPLICATION OF STATUS CODES
	DESCRIPTION
S0	Assigned by task teams to identify information containers as Work in Progress and not yet suitable to be Shared outside the task team.
S1	Assigned by task teams to limit the information container’s use to coordination activities only by its recipients. Information containers assigned this status should only be used to understand or advance their own deliverables in a coordinated manner. It is likely to be assigned to a geometrical information container but it is important to understand that S1 can be assigned to any information container.
S2	Assigned by task teams to limit the information container`s use for any specific activity by its recipients. This status denotes that the author is providing it for information only to help others in certain situations. For example, reference information provided by the appointing party such as a dilapidations report would be given this status code. Another example would be an email file containing site photos.
S3	Assigned by task teams to limit the information container`s use to commenting and review activities only by its recipients. Information containers assigned this status should only be used to review their contents against the information requirements or to provide feedback on their development. For example, an outline proposal to solve a technical design problem during Concept stage.
S4	Assigned by task teams to limit the information container`s use to stage approval activities only by its recipients. The outcome of the review following this status should be the acceptance of the information container that it meets stage requirements.
S5	This status code is not used in the National Annex
S6	Assigned by task teams to limit the information container`s use to the lead appointed party’s authorization of the project information model (see ISO 19650-2 clauses 5.7.1 and 5.7.2). The information should not be used for contractual purposes, for example, construction until the project information model that it forms part of has been authorized by the lead appointed party and accepted by the appointing party. If the project information model is rejected but the information container itself does not require amendment its status will remain at S6 until the project information model is authorized. If the project information model is rejected and the information container requires amendment then it is assigned the SO status until it can be shared again. Note that a project information model could be a single information container or it could be multiple information containers depending on the exchange information requirements.
S7	Assigned by task teams to limit the information container`s use to authorization activities for Stage 6 (Handover) only by its recipients. The outcome of this status should be the authorization of the information model that it meets the requirements for handover to facilities and asset management teams.
A0 - An	Assigned by task teams to represent the Stage the authorized and accepted information container relates to in accordance with the task information delivery plan. For example A1 would represent an authorized and accepted information container generated in Stage 1, A2 would represent Stage 2 and so on
CR	Assigned by task teams to represent an information container that has been authorized and accepted and was previously assigned an S7 status.

Table 4‑16: Application of Status Codes

4.3 EXCHANGE OF INFORMATION

Ø All information exchanges will be generated according to "Common Data Environment standards, methods and procedures".

Ø All information exchanges will follow Information Delivery Manual.

MODEL DESCRIPTION DOCUMENT (MDD:) During exchanging models Model Description Document (MDD) has to be maintained by each discipline.

þ At official publishing points, the publisher is responsible for the consequences caused by incomplete or incorrect documentation.

þ Please find the template of MDD to be filled by each responsible party below:

MODEL DESCRIPTION DOCUMENT (MDD)
DOCUMENT NO
DISCIPLINE
PROJECT NAME
BEP REFERENCE & REVISION
AGREED MODEL USE	The model has been issued for ...
MODEL AUTHORING COMPANY
DISCIPLINE BIM LEAD
NATIVE FILE TYPE & VERSION	(e.g. Revit 2020)
ISSUED FILE TYPE & VERSION	(e.g. Navisworks 2020)
UNITS & MEASUREMENT
COORDINATE SYSTEM
ISSUED DATE
MODEL STATUS
MODEL NAME
FILE NAME
LINKED FILES
DATA CONTENT OF THE MODEL
INPUTS
MODEL PURPOSE
CHANGES & UPDATES
AREAS ON HOLD
COMMENTS

Table 4‑17: Model Description Document Template

4.3.1 EXCHANGE FORMATS

.....

FILE TYPE

DESCRIPTION

Table 4‑18: Exchange Formats Table

4.3.2 INFORMATION EXCHANGE / ATTRIBUTE DATA

? Describe the standards of attribute data ( parameters, shared parameters, discipline special parameters, URL Data, Spatial Data, Cobie Data, Classification Number etc.) and how to use them. Describe how to use the Attribute Data Log.

.....

Ú Refer to: (under folder: Delivery_IMDocs/BEP)

Annex_4.1 = ATD: Attribute Data Log

4.3.2.1 PROJECT'S CONSTRUCTION OPERATIONS BUILDING INFORMATION EXCHANGE (COBIE) STANDARDS

? The minimum COBie attributes for typical BIM will be defined in below table and standards for COBie usage in the project will be mentioned.

.....

Attribute /Parameter	Data Type	Description	Responsible Party
COBie-Floor-Category	TEXT	Category of the floor (Site, Floor, Roof).	Design team

Table 4‑19: COBie DATA

COBie Sheet	Classification Table
Contact
Facility
Space
Type
System

Table 4‑20: Classification and COBie

4.3.2.2 INFORMATION TO BE EITHER EXCLUDED from OR INCLUDED ın INFORMATION MODELS

....

ASSET NAME	DESCRIPTION	PIM		AIM
		INCLUDED	EXCLUDED	INCLUDED	EXCLUDED

Table 4‑21: Information to be excluded from or included in information models table

4.3.2.3 PROJECT'S IFC & mvd STANDARDS

? Describe the standards for IFC & MVD to be used in the project.

.....

IFC VERSION	BIM USE
IFC 2x3	Design Authoring
IFC 4	.....

Table 4‑22: Project's IFC Standards Table

MVD VERSION

BIM USE

Table 4‑23: Main MVDs of The Project

4.3.2.4 THE EXCHANGE OF INFORMATION WITHIN THE APPOINTING PARTY’S ORGANIZATION

.....

Figure 4‑1: Process Map - Exchange of Information Between within the Apop's Organization

4.3.2.5 THE EXCHANGE OF INFORMATION BETWEEN THE APPOINTING PARTY AND EXTERNAL STAKEHOLDERS

.....

Figure 4‑2: Process Map - Exchange of Information Between the Apop and External Stakeholders

4.3.2.6 THE EXCHANGE OF INFORMATION BETWEEN THE APPOINTING PARTY AND EXTERNAL OPERATORS OR MAINTAINERS

.....

Figure 4‑3: Process Map - Exchange of Information Between Apop and External Operators or Maintainers

4.3.2.7 THE EXCHANGE OF INFORMATION BETWEEN THE PROSPECTIVE LEAD APPOINTED PARTY AND THE APPOINTING PARTY

.....

Figure 4‑4: Process Map - Exchange of Information Between Peap and the App

4.3.2.8 THE EXCHANGE OF INFORMATION BETWEEN PROSPECTIVE APPOINTED PARTIES ON THE SAME PROJECT

.....

Figure 4‑5: Process Map - Exchange of Information Between PEAPs on the Same Project

4.3.2.9 THE EXCHANGE OF INFORMATION BETWEEN INTERDEPENDENT PROJECTS

.....

Figure 4‑6: Process Map - Exchange of Information Between Independent Projects

4.4 METHOD OF ASSIGNMENT FOR LEVEL OF INFORMATION NEED

I Ref.to ISO-19650-2/5.1.4.c

.....

Ú Refer to:

Annex_7.1 = HLRM_1: Delivery team’s High Level Responsibility Matrix

Annex_7.2 = DRM_0: Delivery Team’s Detailed Responsibility Matrix (Initial/Template)

Table 4‑24: Method of assignment for Level of Information Need Table

4.5 UNITS, MEASUREMENT & COORDINATE SYSTEM

.....

4.5.1 UNITS & MEASUREMENT

I The project team should agree common units of measurement.

.....

TYPE OF INFORMATION	Millimeters	Meters	Degrees	Radians	Clockwise	Counter- Clockwise
SURVEY
Models-ARCHITECTURE
Models-STRUCTURE
Models-MECHANICAL & PLUMBING
Models-ELECTRICAL
Models-LANDSCAPE
Models-Discipline X1
Models-Discipline X2
Drawings-ARCHITECTURE
Drawings-STRUCTURE
Drawings-MECHANICAL & PLUMBING
Drawings-ELECTRICAL
Drawings-LANDSCAPE
Drawings-Discipline X1
Drawings-Discipline X2
XX

Table 4‑25: Units and Measurement

4.5.2 COORDINATE SYSTEM

? Coordinate System type will be mentioned. Origin and other spatial coordination related items will be given in the 5th Chapter.

.....

4.6 LEVEL OF ACCURACY (LOA_1)

I Ref.to ISO-19650-2/5.2.1.b/Note

I Agreed Construction Tolerances for all Disciplines

.....

PHASE

DISCIPLINE

TOLERANCE / DESCRIPTION

Table 4‑26: Level of Accuracy Table (LOA)

4.7 SHEETS

? Mention sheet sizes to be used in the project and describe the sheet organization of the project.

? Describe the templates and title blocks to be used in the project.

.....

4.7.1 SHEET ORGANIZATION & SIZES

.....

Table 4‑27: Sheet Sizes

4.7.2 DRAWING SHEET TEMPLATES

.....

4.7.3 TITLE BLOCK

.....

4.8 ANNOTATIONS, DIMENSIONS, LINES, SCHEDULES, ABBREVIATIONS AND SYMBOLS

.....

4.8.1 ANNOTATIONS

.....

4.8.2 DIMENSIONS

.....

4.8.3 LINES

.....

4.8.4 SCHEDULES

.....

4.8.5 ABBREVIATIONS

.....

4.8.6 SYMBOLS

.....

4.9 COLLABORATION & MODELING & PUBLISHING STANDARDS (WITHIN THE CDE) (COL-S_2)

I Explain the agreed modelling & publishing standards of the Project's organization (such as User Interface, Setting Stories/Levels, Detailing etc.)

.....

4.9.1 MODELLING STANDARDS

.....

4.9.2 PUBLISHING STANDARDS

? Explain the agreed publishing standards of the Project's organization

? Information to be either excluded from or included in information models when publishing.

.....

4.10 USE OF INFORMATION DURING THE OPERATIONAL PHASE OF THE ASSET

? Ref.to ISO-19650-2/5.1.4.d, 5.8.1:

.....

4.10.1 PIM TO AIM STANDARDS (pat-s)

.....

5 INFORMATION PRODUCTION METHODS and PROCEDURES (pmp_2)

(ref.to ISO-19650-2/5.4.1: confirm and document the delivery team’s proposed information production methods and procedures)

Ú Documents:

4 QUA: Quality Assurance, Coordination & Issue Management Manual

4 DAS: Data Segregation

4 SCO: Spatial Coordination (Coordinates) Methods & Procedures

4 SCR: Security Requirements

4 PAT-MP: PIM to AIM Transition Methods and Procedures (Ref.to 5.8.1)

4 CDM: CDM/Health & Safety Requirements

4 COL-PP: Collaboration Process & Procedures (within the CDE)

4 CDE-SMP_1: Project's CDE Structure, Standards, Methods, Procedures

4 OIR: Organizational Information Requirements

4 PIR: Project Information Requirements

4 REM-A_1: Information Management Assignment Matrix

4 PMP_1: Project's Information Production Methods and Procedures

4 PRS_1: Procurement Route (Schema & Table)

.....

5.1 SPATIAL COORDINATION (COORDINATES&GEO-LOCATION) METHODS & PROCEDURES (SCO_2)

.....

Table 5‑1: Coordinates and Geo-Location Table (SCO)

5.1.1 PIM ORIGIN & ORIENTATION

.....

Figure 5‑1: PIM Origin & Orientation

5.2 FEDERATION STRATEGY & INFORMATION CONTAINER BREAKDOWN STRUCTURE (FSB_1)

I Ref. to. ISO 19650-2/5.3.2, 5.4.1

I Including any agreed changes from "Tender Response" Package.

? Mention federation strategy and information container breakdown structure with tables, figures such as below and necessary explanations such as linking strategies.

.....

FEDERATION PARTS LIST
LEVEL 1 FED. PARTS	LEVEL 2 FED. PARTS	LEVEL 3 FEDERATION PARTS					FLOOR LEVEL	DESCRIPTION
		Sub Division Architectural	Stair Elevator Core	Structural	Mechanical &Plumbing	Electrical

Table 5‑2:Federation Parts List (Sample)

Figure 5‑2: Information Container Breakdown of the Federation Strategy

5.3 THE CAPTURE OF EXISTING ASSET INFORMATION

I Ref. to. ISO 19650-2/5.3.2

.....

5.3.1 SURVEY STRATEGY

.....

SURVEY METHOD

DELIVERY FORMAT

SURVEY ORIGIN

NOTES

Table 5‑3: Survey Strategy

5.3.2 QUANTITY EXTRACTION & TRACKING STRATEGY

.....

Figure 5‑3: Quantity extraction & tracking strategy

5.4 THE SECURITY OR DISTRIBUTION OF INFORMATIOn

I Please refer to Project's Common Data Environment standards, methods & procedures mentioned in Chapter 3.3.

.....

5.4.1 SECURITY REQUIREMENTS (SCR_1)

.....

Table 5‑4: Security & Extranet Access, Distribution Authority

5.5 THE GENERATION, REVIEW OR APPROVAL OF NEW INFORMATION

I Please refer to Chapter 3.for CDE

I Please refer to Chapter 4.for Project's Modelling Standards.

I Please refer to Chapter 4.for Project's Publishing Standards.

....

5.5.1 COLLABORATION & MODELLING & publıshıng METHODS & PROCEDURES (WITHIN THE CDE) (COL-mP_2)

? Collaboration (including Modelling Process Management & Publishing) strategy should be defined according to "Federation strategy & information container breakdown structure" and "Common Data Environment Rules" described above.

....

5.5.1.1 COLLABORATIVE WORKSPACE

.....

5.5.1.2 MODELLING (PROCESS/WORKFLOW) METHODS & procedures (wıthın cde)

? Modelling Process/Workflow should be defined with rules, procedures & methods to be followed.

....

Figure 5‑4: Modelling Process/Workflow Schema

5.5.1.3 PROJECT'S IFC & mvd METHODS & PROCEDURES

? Mention the methods and procedures of usage of IFC and MVD in the project.

....

5.5.1.4 BIM TEST MOCK-UP

I As part of planning BIM data exchange methodologies it is beneficial to test the exchange workflows prior to commencing the project models. This process is helping to establish the most efficient ways of collaboratively exchanging information as well as reducing the risk of problems later in the process.

? Before each phase exchange workflows (including all Bim Uses which will be used in that phase) must be tested to establish the most efficient ways of collaboratively exchanging information as well as reducing the risk of problems later in the processes. These tests are recorded in below table.

....

Test Mock-Up No	PHASE	BIM USE (as code, ref. to Annex-3.3)	RESULT (Ok/Not OK Ok with notes)	COMMENT
01
02
03
04
05

Table 5‑5: BIM Test Mock-Ups Table

5.5.1.5 COMMUNICATION PROCEDURES (WITHIN CDE)

.....

5.5.1.5.1 ELECTRONIC COMMUNICATION PROCEDURES

? Mention the electronic communication procedures with taking CDE into consideration.

....

5.5.1.5.2 MEETING COMMUNICATION PROCEDURES

? Mention the meeting communication procedures with taking CDE into consideration.

....

MEETING SCHEDULE
MEETING TYPE	FREQUENCY	PARTICIPANTS

Table 5‑6: Meeting Schedule

5.5.1.6 PUBLISHING METHODs & PROCEDURES

.....

5.5.1.7 CHANGE LOG

? Mention "Change Log" procedures.

Ú Refer to (under folder: Delivery_IMDocs/BEP)

Annex_5.1 = CHL: Change Log Template

.....

5.5.1.8 DATA MANAGEMENT ACCORDING TO SEGREGATION (DAS_2)

? Agreed "Data Management System" according to "Federation Strategy", "Information container naming requirements (ICN)" and above related sub-chapters should be defined.

....

5.5.2 QUALITY ASSURANCE MANUAL (QUA_3)

.....

5.5.2.1 QUALITY CONTROL (QC)

.....

5.5.2.2 QUALITY ASSURANCE (QA)

.....

5.5.2.3 QC/QA TOOLS

.....

5.5.3 COORDINATION, CLASH DETECTION & ISSUE MANAGEMENT MANUAL (CCI_3)

.....

Ú Refer to (under folder: Delivery_IMDocs/BEP)

Annex_5.2 = CLAM: Clash Detection Matrix

5.6 CDM/HEALTH & SAFETY REQUIREMENTS (CDM)

.....

5.7 PIM TO AIM TRANSITION METHODS AND PROCEDURES (PAT-MP_1)

.....

5.7.1 PROJECT'S CONSTRUCTION OPERATIONS BUILDING INFORMATION EXCHANGE (COBIE) METHODS & PROCEDURES

.....

5.8 THE DELIVERY OF INFORMATION TO THE APPOINTING PARTY

I Ref. to. ISO 19650-2/5.1.5, 5.3.2,

.....

6 INFORMATION DELIVERY STRATEGY (dt-ıds_1)

I Ref.to ISO-19650-2/5.4.1: update the delivery team’s information delivery strategy (as required))

I Including any agreed changes from "Invitation to Tender" Package. Ref. to ISO 19650-2/5.1, 5.2

I Including any agreed changes from "Tender Response" Package. Ref. to ISO 19650-2/5.3

Ú Documents:

4 EIR_APOP: Appointing Party's Exchange Information Requirements

4 ACR: Acceptance Criteria Manual

4 CCA_IM: Information Management Capability and Capacity Assessment Form

4 CCA_IP: Information Production Capability and Capacity Assessment Form

4 CCA_IT: Information Technology Capability and Capacity Assessment Form

4 RAS_1: Risk Assessment Requirements

6.1 APPOINTMENT RELATED REQUIREMENTS

? The following areas of BIM implementation should be considered and included in appointments where applicable:

: Model Development and Responsibilities of Parties Involved ; Model Sharing and Reliance; Interoperability; Model Management; Intellectual Property Rights

? Appointment documents (templates & attachments which are addressing the BIM implementation of the project) to be followed (during the first appointment:

Project's Information Protocol

Examples for Appointment documents:

X CIC Documents

X AIA Document C106 - 2013: Digital Data Licensing Agreement.

X AIA Document G201 - 2013: Project Digital Data Protocol Form

X AIA Document G202 - 2013: Project Building Information Modeling Protocol Form

X AIA Document E201 - 2007: Digital Data Protocol Exhibit

X AIA Document E202 - 2008: BIM Protocol Exhibit. This document addresses the development of a model throughout a project.

X AIA Document E203 - 2013: Building Information Modeling and Digital Data Exhibit

X AIA Document B101 - 2007: Standard Form of Agreement Between Owner and Architect

X AIA Document A101 - 2007: Agreement Between Owner and Contractor

X AIA Document B195 - 2008: An Owner-Architect agreement

X AIA Document A195 - 2008: A Guaranteed Maximum Price (GMP) Owner and Contractor Agreement

X AIA Document A295 - 2008: General Conditions of the Agreement for Integrated Project Delivery

X AIA Document B207 - 2008: On-Site Project Representation scope of services document

X AIA Document C195 - 2008: Standard Form Single Purpose Entity

X AIA Document C196 - 2008: The agreement between the SPE and the project owner

X AIA Document C197 - 2008: The agreement between the SPE and any non-owner SPE member.

X Consensus DOCS 301 BIM Addendum. This document addresses the risk management of a BIM design process.

X Consensus DOCS 200.2: Electronic Communications Protocol Addendum

? Appointment documents (templates & attachments which are addressing the BIM implementation of the project) to be followed will be mentioned including the authority (RACI) to check the appointment during deliverables (such as Lead Designer's Project Manager etc.). Appointment documents related requirements specific for BEP will be mentioned.

.....

APPOINTMENT DOCUMENT NAME	AUTHORITY (mentioned with the codes of the actors/parties)
	R	A	C	I
INP_1: Project's Information Protocol
AIA Document - A295–2008: For general

Table 6‑1: Appointment Document RACI Table

6.2 TENDER RESPONSE REQUIREMENTS & EVALUATION CRITERIA (TEN-CR

....

6.2.1 RISK ASSESSMENT REQUIREMENTS (RAS_1)

Ø Please refer to ISO-19650-2/5.1.8, 5.2.1, 5.2.3, 5.3.4, 5.3.6, 5.3.7

? Mention the updated Risk Assessment Requirements (to guide risk management through whole life cycle of the project).

? Mention the Key Performance Indicators

.....

6.2.1.1 KEY PERFORMANCE INDICATORs (KPIS)

.....

KPI NAME	DESCRIPTION	RESULT OF KPI (0=Ineffective, 1=Less, 2= Effective, 3=Strongly Effective, 4= Most Effective, a=Pass/Reasonable, b=Not Pass/Unreasonable)
Reduce implementation cost	Clash detection frequency

Table 6‑2: (KPIS) Key Performance Indicators

6.2.2 ACCEPTANCE CRITERIA MANUAL (ACR_1)

Ø Please refer to ISO-19650-2/5.2.1, 5.2.3, 5.4.3, 5.6.5

Annex_6.1 = ACR_1: Acceptance Criteria Manual

þ Document Location: " ACR_1 " is under folder: Delivery_IMDocs/BEP

? For further details of Acceptance Criteria for both submission and approval processes (for LEAP, APP and all Task Teams) update the ACR and give as annex of this BEP. Refer to ACR_1 document throughout the whole Life Cycle.

? Mention how to use the ACR_1 document.

.....

6.3 TASK TEAMS' CAPABILITY & CAPACITY

Ø Please refer to ISO-19650-2/5.3.3

? Describe the report of updated task teams' capability and capacity with referring to 6.3.1 and 6.3.2

? This report will be checked and updated (if necessary) before each Bim Use and Main Phase begins

.....

6.3.1 CAPABILITY AND CAPACITY ASSESSMENT OF TASK TEAMs (TT-CCA_1)

Ø Please refer to ISO-19650-2/5.3.3

? Describe the result of updated task teams' capability and capacity assessments.

? Task teams' capability and capacity assessments should be checked before each Bim Use and Main Phase begins by the Lead Appointed Party with using below forms (ref.to 6.3.1.1, 6.3.1.2, 6.3.1.3)

.....

6.3.1.1 INFORMATION MANAGEMENT CAPABILITY AND CAPACITY ASSESSMENT FORM (CCA_IM)

Ø Please refer to ISO-19650-2/5.3.3, and;

Annex_6.2 = CCA_IM: Information Management Capability and Capacity Assessment Form

þ Document Location: " CCA_IM " is under folder: Delivery_IMDocs/BEP

? Mention methods to use this form for capability and capacity assessment of task teams.

.....

6.3.1.2 INFORMATION PRODUCTION CAPABILITY AND CAPACITY ASSESSMENT FORM (CCA_IP)

Ø Please refer to ISO-19650-2/5.3.3, and;

Annex_6.3 = CCA_IP: Information Production Capability and Capacity Assessment Form

þ Document Location: " CCA_IP " is under folder: Delivery_IMDocs/BEP

? Mention methods to use this form for capability and capacity assessment of task teams.

.....

6.3.1.3 IT-INFORMATION TECHNOLOGY CAPABILITY AND CAPACITY ASSESSMENT FORM (CCA_IT)

Ø Please refer to ISO-19650-2/5.3.3, and;

Annex_6.4 = CCA_IT: Information Technology Capability and Capacity Assessment Form

þ Document Location: " CCA_IT " is under folder: Delivery_IMDocs/BEP

? Mention methods to use this form for capability and capacity assessment of task teams.

.....

6.3.2 TASK TEAMS' INFORMATION DELIVERY STRATEGIES (TT-IDS_1)

Ø Please refer to ISO-19650-2/5.3.3

? Mention task teams' updated information delivery strategies.

? Task teams' information delivery strategies need to be considered and evaluated before each "Bim Use" or "Main Phase" begins. According to the evaluation necessary revisions must be requested and coordinated.

.....

6.4 DELIVERY TEAM'S CAPABILITY & CAPACITY (DTCC_1)

Ø Please refer to ISO-19650-2/5.3.4

? Mention the delivery teams' updated capability and capacity.

? Delivery team’s capability and capacity needs to be considered and evaluated before each "Bim Use" or "Main Phase" begins. According to the evaluation necessary precautions (trainings etc.) must be taken.

.....

6.5 DELIVERY TEAM'S MOBILIZATION PLAN

Ø Please refer to ISO-19650-2/5.3.5, 5.5.1, 5.5.2, 5.5.3, and;

Appendix_6.5 = MOB_1: DELIVERY TEAM'S MOBILIZATION PLAN

þ Document Location: "MOB_1" is under folder: Delivery_IMDocs

? Update Delivery Team's Mobilization Plan according to 6.1 ,6. 2 and 6.3

? Mention main objectives of the Delivery Team's Mobilization Plan and refer to MOB for further details.

.....

6.6 DELIVERY TEAM'S RISK REGISTER (drr_1)

Ø Please refer to ISO-19650-2/5.3.6

? Describe the updated delivery team's risk register.

? According to the analysis of the finalized activities and lessons learned during each activity, "Delivery Team’s Risk Register" needs to be updated after each activity ends.

.....

6.7 INFORMATION DELIVERY STRATEGY (DT-IDS_1)

I Ref.to ISO-19650-2/5.3.2.b: containing

· the delivery team’s approach to meeting the appointing party’s exchange information requirements,

· a set of objectives/goals for the collaborative production of information,

· an overview of the delivery team’s organizational structure and commercial relationships, and

· an overview of the delivery team’s composition, in the form of one or more task teams;

I Ref.to ISO-19650-2/5.4.1.b: update the delivery team’s information delivery strategy (as required);

? Explain the "Updated Information Delivery Strategy" with referring to IDM and 6.1-6.6 Sub-Chapters:

þ Approach to meeting the appointing party’s EIR

þ Collaborative Production of Information Objectives/Goals

þ Delivery Team's Organizational Structure

þ Delivery Team’s Composition,

.....

6.7.1 IDM

? Short brief summary of "Project's IDM". Refer to "Project's IDM" for further details.

.....

Figure 6‑1: Project's Brief Process Map

Appendix_6.6 = IDM: INFORMATION DELIVERY MANUAL

7 HIGH LEVEL RESPONSIBILITY MATRIX (HLRM_1)

I Ref.to ISO-19650-2/5.3.2: "The delivery team’s high-level responsibility matrix contains the allocated responsibility for each element of the information model and the key deliverables associated to each element."

I Ref.to ISO-19650-2/5.4.1: "Update the delivery team’s high-level responsibility matrix (as required). "

I Ref.to ISO-19650-1/3.1.1: responsibility matrix: chart that describes the participation by various functions in completing tasks or deliverables [SOURCE: ISO 37500:2014, 3.16 – modified]. Note 1 to entry: A responsibility matrix can indicate accountability, consultation and informing, alongside the obligation to complete tasks or deliverables.

I Ref.to ISO-19650-1/10.3: A responsibility matrix should be generated as part of the information delivery planning process in one or more levels of detail. The axes of a responsibility matrix should identify:

· information management functions; and

· either project or asset information management tasks, or information deliverables as appropriate.

The content of a responsibility matrix should show the appropriate detail relevant to the axes.

Ú Please refer to (under folder: Delivery_IMDocs/BEP);

Annex_7.1 = HLRM_1: Delivery team’s High Level Responsibility Matrix

Please kindly find the High Level Responsibility Matrix of the project attached to this document.

.....

7.1 DETAILED RESPONSIBILITY MATRIX (DRM_0)

? Ref.to ISO-19650-2/5.4.2: The lead appointed party shall further refine the high level responsibility matrix to establish the detailed responsibility matrix, which identifies:

· what information is to be produced;

· when the information is to be exchanged and with whom; and

· which task team is responsible for its production.

Ø In doing this, the lead appointed party shall consider:

o the information delivery milestones; the high level responsibility matrix; the project’s information production methods and procedures; the elements of information container breakdown structure allocated to each task team; and the dependencies on the information production process.

? Details (how to use, structure etc.) of "Delivery Team's Detailed Responsibility Matrix" will be given. Template/Initial Work will be given in the first BEP and afterwards during each revision the up-to-date Detailed Responsibility Matrix will be given as Annex of the BEP. Detailed Responsibility Matrix is also including the BIM Uses parameter.

Ú Please refer to (under folder: Delivery_IMDocs/BEP);

Annex_7.2 = DRM_0: Delivery Team’s Detailed Responsibility Matrix Initial Version (Template)

Please kindly find the Detailed Responsibility Matrix Template of the project attached to this document.

.....

7.2 TASK INFORMATION DELIVERY PLAN (TIDP_1...N)

? Ref.to ISO-19650-2/3.1.3.4: task information delivery plan (TIDP) schedule of information containers and delivery dates, for a specific task team.

? Ref.to ISO-19650-2/5.4.4: Each task team shall establish, and maintain throughout its appointment, a task information delivery plan (TIDP). In doing this, each task team shall consider:

· the project’s information delivery milestones;

· the task team’s responsibilities within the detailed responsibility matrix;

· the lead appointed party’s information requirements;

· the availability of shared resources within the delivery team; and

· the time the task team will need to produce (generate, coordinate, review and approve) information

The TIDP shall list and identify, for each container, the:

· name and title;

· predecessors or dependencies;

· level of information need;

· the (estimated) production duration;

· information author responsible for its production; and

· delivery milestones.

? Task Information Delivery Plan Template should be explained (how to use, content etc.).

Ú Please refer to (under folder: Delivery_IMDocs/BEP);

Annex_7.3 = TIDP-TMP: Task Information Delivery Plan Template

Please kindly find the Task Information Delivery Plan Template of the project attached to this document.

.....

7.3 MASTER INFORMATION DELIVERY PLAN (mıdp_0)

I Ref.to ISO-19650-2 / 3.1.3.3: master information delivery plan_MIDP_plan incorporating all relevant task information delivery plans

I Ref.to ISO-19650-2 / 5.4.5: The lead appointed party shall aggregate the TIDP from each task team in order to establish the delivery team’s master information delivery plan (MIDP). In doing this, the lead appointed party shall consider:

the assigned responsibilities within the detailed responsibility matrix; the information predecessors or dependencies on information between task teams; the time the lead appointed party will need to review and authorize the information model; and the time the appointing party will need to review and accept the information model.

Once the MIDP has been established, the lead appointed party shall:

baseline the deliverables and dates within the MIDP; inform each task team and notify if any changes are required to the TIDP; and inform the appointing party of any risks or issues which could impact on the project’s information delivery milestones.

I ISO 19650-1/6.3.4: If new parties join the delivery team, the delivery plan should be updated to include and confirm the information they will be contributing to future information exchanges.

? Initial version of Master Information Delivery Plan will be presented. How to use etc. instructions will be given.

Ú Please refer to (under folder: Delivery_IMDocs/BEP);

Annex_7.4 = MIDP_0: Master Information Delivery Plan Initial Version (Template)

Please kindly find the Master Information Delivery Plan Initial Version (Template) of the project attached to this document.

.....

8 SCHEDULE OF SOFTWARE, HARDWARE & IT INFRASTRUCTURE (SCH-IT_1)

I Ref.to ISO-19650-2 / 5.3.2.g: ..Include a proposed schedule of software (including versions), hardware and IT infrastructure the delivery team intend to adopt.

I Ref.to ISO-19650-2 / 5.3.5.f: ...The delivery team's mobilization plan will be established with considering PEAP's approach, timescales and responsibilities for procuring, implementing, configuring and testing additional software, hardware and IT infrastructure;

I Ref.to ISO-19650-2 / 5.4.1.f : ...confirm the schedule of software, hardware and IT infrastructure the delivery team will use.

I Ref.to ISO-19650-2 / 5.5.2.a: ...procure, implement, configure and test software, hardware and IT infrastructure (as required);

8.1 SOFTWARE

? Requirements to be followed during "Software Selection" process (for to follow during further updates, revisions), process & data management systems, Common Data Environment related instruction.

Ä Note: Please refer to Table 8.1 for the whole schedule.

.....

8.2 HARDWARE & IT INFRASTRUCTURE

? Requirements to be followed during "Hardware Selection" process (for to follow during further updates, revisions).

? Requirements to be followed during "IT Infrastructure" process (for to follow during further updates, revisions).

Ä Note: Please refer to Table 8.1 for the whole schedule.

.....

8.3 SCHEDULE OF SOFTWARE, HARDWARE & IT INFRASTRUCTURE

SOFTWARE
SOFTWARE NAME	SOFTWARE'S SCOPE	VERSION	NATIVE FILE	BIM USE CODE(S) (Ref.to. Bim Uses Desc.&Del.Table)
HARDWARE
HARDWARE NAME	DESCRIPTION			BIM USE CODE(S)
IT INFRASTRUCTURE
NAME	DESCRIPTION / SCOPE		VERSION	BIM USE CODE(S)
ENTERPRISE SOTWARE APPLICATIONS
COMPUTER HARDWARE PLATFORMS
CONSULTANTS & SYSTEM INTEGRATORS
NETWORKING / TELECOMMUNICATIONS
DATA MANAGEMENT & STORAGE
OPERATING SYSTEM PLATFORMS
INTERNET PLATFORMS

Table 8‑1: (SCH-IT_1) Schedule of Software, Hardware & IT

9 TEMPLATES FOR FURTHER DELIVERY PHASE ACTIVITIES (4.2 - 5.8)

I The templates which will be used during further delivery phase activities are mentioned below. These documents are part of the "Project Package" and mentioned in this BEP as a guide for to use during the related activity. Please kindly find the location information for these documents below.

9.1 LEAD APPOINTED PARTY'S EXCHANGE INFORMATION REQUIREMENTS (EIR-LEAP)

Ø Please refer to ISO-19650-2/5.4.3. and;

Appendix_9.1 = EIR-LEAP-TMP: Lead Appointed Party's Exchange Information Requirements Template

þ Document Location:

"EIR-LEAP" is under folder: Delivery_IMDocs

Ä Delivery_IMDocs=Delivery Phase Information Management Documents

þ Template Location:

"EIR-LEAP-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.2 MOBILIZATION OF RESOURCES

Ø Please refer to ISO-19650-2/5.5.1 and;

Appendix_9.2 = MORE-TMP: Mobilization of Resources Report Template

þ Document Location:

"MORE" is under older: Delivery_IMDocs

þ Template Location:

"MORE-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.3 MOBILIZATION OF INFORMATION TECHNOLOGY

Ø Please refer to ISO-19650-2/5.5.2 and;

Appendix_9.3 = MOIR-TMP: Mobilization of Information Technology Report Template

þ Document Location:

"MOIR" is under folder: Delivery_IMDocs

þ Template Location:

"MOIR-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.4 PROJECT'S INFORMATION PRODUCTION METHODS AND PROCEDURES TEST

Ø Please refer to ISO-19650-2/5.5.3 and;

Appendix_9.4 = PMP-RR-TMP: Project's Information Production Methods and Procedures Test Report Template

þ Document Location:

"PMP-RR" is under folder: Delivery_IMDocs

þ Template Location:

"PMP-RR-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.5 CHECKING TASK TEAM'S AVAILABILITY OF REFERENCE INFORMATION AND SHARED RESOURCES

Ø Please refer to ISO-19650-2/5.6.1 and;

Appendix_9.5 = CR-TT-TMP: Task Team's Access Check Report Template

þ Document Location:

"CR-TT" is under folder: Delivery_IMDocs

þ Template Location:

"CR-TT-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.6 TASK TEAM'S QUALITY ASSURANCE CHECK

Ø Please refer to ISO-19650-2/5.6.3 and;

Appendix_9.6 = QUA-TT-TMP: Task Team's Quality Assurance Check Report Template

þ Document Location:

"QUA-TT" is under folder: Delivery_IMDocs

þ Template Location:

"QUA-TT-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.7 TASK TEAM'S INFORMATION REVIEW & APPROVAL (BY TASK TEAM) FOR SHARING

Ø Please refer to ISO-19650-2/5.6.4 and;

Appendix_9.7 = IRR-TT-TMP: Task Team's Information Review (by Task Team) Report Template

þ Document Location:

"IRR-TT" is under folder: Delivery_IMDocs

þ Template Location:

"IRR-TT-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.8 DELIVERY TEAM'S INFORMATION REVIEW FOR COORDINATION

Ø Please refer to ISO-19650-2/5.6.5 and;

Appendix_9.8 = IMR-DT-TMP: Delivery Team's Information Model Review Report Template

þ Document Location:

"IMR-DT" is under folder: Delivery_IMDocs

þ Template Location:

"IMR-DT-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.9 REVIEW & AUTHORIZATION OF THE INFORMATION MODEL BY LEAD APPOINTED PARTY

Ø Please refer to ISO-19650-2/5.7.2 and;

Appendix_9.9 = TTS-RR-TMP: Task Teams' Submittals & PIM Review Report by Leap Template

þ Document Location:

"TTS-RR" is under folder: Delivery_IMDocs

þ Template Location:

"TTS-RR-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.10 SUBMITTAL LISTS

Ø Please refer to ISO-19650-2/5.7.1 & 5.7.3 and;

Appendix_9.10 = SBL-TMP: Submittal Lists Template

þ Document Location:

"SBL" is under folder: Delivery_IMDocs

þ Template Location:

"SBL-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.11 INFORMATION MODEL REVIEW & ACCEPTION BY APPOINTING PARTY

Ø Please refer to ISO-19650-2/5.7.4 and;

Appendix_9.11 = PIM-RR-TMP: Appointing Party's PIM Review Report Template

þ Document Location:

"PIM-RR" is under folder: Delivery_IMDocs

þ Template Location:

"PIM-RR-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.12 PIM ARCHIVE

Ø Please refer to ISO-19650-2/5.8.1 and;

Appendix_9.12 = PAR-TMP: PIM to AIM Requirements Template

þ Document Location:

"PAR" is under folder: Delivery_IMDocs

þ Template Location:

"PAR-TMP" is under folder: Shared_Resources / Delivery _Activities / Templates

9.13 LESSONS LEARNED REGISTER

Ø In collaboration with each lead appointed party, the appointing party shall capture lessons learned during the project and record them in a suitable knowledge store, to be called upon by future projects.

Ø Please refer to ISO-19650-2/5.8.2 and;

Appendix_9.13 = CLL-TMP: Capture Lessons Learned Template (for LEAP and APP's Use)

Appendix_9.14 = RLL-TMP: Lessons Learned Register Template(by APOP)

þ Document Location:

"CLL & RLL" are under folder: Delivery_IMDocs

þ Template Location:

"CLL-TMP & RLL-TMP" are under folder: Shared_Resources / Delivery _Activities / Templates

10 TEMPLATES FOR OPERATIONAL PHASE ACTIVITIES

I Templates as per ISO 19650-3 activities will be produced during PIM to AIM process (the beginning of Operational Phase) and as explained in the Operational Phase BEP .

þ Documents Location:

are under folder: Operational_IMDocs

Ä Operational_IMDocs=Operational Phase Information Management Documents

þ Templates Location:

are under folder: Shared_Resources / Operational _Activities / Templates

11 REFERENCE DOCUMENTS & STANDARDS

: The following documents are listed for reference.

1. ISO 19650-1: Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Information management using building information modelling — Part 1: Concepts and principles

2. ISO 19650-2: Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Information management using building information modelling — Part 2:Delivery phase of the assets

3. ISO_PD-19650-0-2019: Transition guidance to BS EN ISO 19650

4. ISO 29481-1:2016=Building information models-Information delivery manual-Part 1: Methodology and format

5. ISO 29481-2:2012=Building information models-Information delivery manual-Part 2:Interaction framework

6. IS/ISO 13567-1 : 1998=Technical product documentation —Organization and naming of layers for CAD PART 1 OVERVIEW AND PRINCIPLES

7. ISO/TR 13567-3 : TECHNICAL REPORT Technical product documentation —Organization and naming of layers for CAD Part 3: Application of ISO 13567-1 and ISO 13567-2

8. ISO 7200: Technical product documentation — Data fields in title blocks and document headers

9. ISO 12006-2:2015 Building construction —Organization of information about construction works Part 2: Framework for classification

10. ISO 12006-3-2007 Building construction — Organization of information about construction works Part 3: Framework for object-oriented information

11. ISO 22263:2008: Organization of information about construction works -Framework for management of project information

12. ISO TS 12911-2012 Technical Specification-Framework for building information modelling (BIM) guidance

13. BSI_PAS 1192-3:2014= Specification for information management for the operational phase of assets using building information modelling

14. BS 1192-4:2014 =Collaborative production of information (Part 4: Fulfilling employer’s information exchange requirements using COBie – Code of practice)

15. BSI_PAS_1192_5:2015=Specification for security-minded building information modelling, digital built

environments and smart asset management.

16. BSI_PAS_1192_6:2018=Specification for collaborative sharing and use of structured Health and Safety information using BIM

17. BS 8541-1, 2, 3, 4; 5, 6: Library objects for architecture, engineering and construction

18. BS 8536-1:2015=Briefing for design and construction –Part 1: Code of practice for facilities management (Buildings infrastructure)

19. BS 8536-2= Briefing for design and construction –Part 2: Code of practice for asset management (Linear and geographical infrastructure)