DELIVERY PHASE INFORMATION MANAGEMENT PROCESS & DOCUMENTS AS PER ISO 19650 
Kerem İlhami Buğdaycıoğlu - 22/Nov./2019 - Version 1.3
PH. CHAPTER ID
/TITLE
 ACTIVITIES NOTE: The number in the code of the document (after underscore) is the update number
Ex.: "…_0"= Initial Version, "…_1"= 1st Update,
"…" No number at the end= No update will be done		  
ID/CODE DESCRIPTION
 
APPOINTING PARTY
5.1.1 Appoint individuals to undertake the information management function
SUB-ACT/ITEMS
TO CONSIDER		 5.1.1.a The tasks that the prospective lead appointed party or third party will be responsible for
5.1.1.b The authority that the appointing party will delegate to the prospective lead appointed party or third party APOP: APPOINTING PARTY
5.1.1.c The competency (knowledge or skills) that the individuals
undertaking the function will need		 LEAP: LEAD APPOINTED PARTY  
DOCUMENTS
TO BE REFERRED		 - - PEAP: PROSPECTIVE LEAD APPOINTED PARTY  
DOCUMENTS TO
BE GENERATED		 OIR Organizational Information Requirements APP: APPOINTED PARTY  
REM-A_0 Information Management Assignment Matrix-(Responsibility Matrix Information Management Activities)        
CHAPTER ID
/TITLE
 ACTIVITIES CHAPTER ID
/TITLE
 ACTIVITIES
FRA_0 Functions Responsibilities & Authorities (Individuals List ) ID/CODE DESCRIPTION ID/CODE DESCRIPTION
APPOINTING PARTY APPOINTING PARTY
5.1.2 Establish the project's information requirements 5.1.3 Establish the project's information delivery milestones
SUB-ACT/ITEMS
TO CONSIDER		 5.1.2.a the project scope SUB-ACT/ITEMS
TO CONSIDER		 5.1.3.a the appointing party’s key decision points
5.1.2.b the intended purpose for which the information will be used by the appointing party 5.1.3.b its own information delivery obligations (if any)
5.1.2.c the project plan of work 5.1.3.c the nature and substance of information to be delivered at each key decision point
5.1.2.d the intended procurement route 5.1.3.d the date(s) relative to each key decision point that the information model is to be delivered
5.1.2.e the number of key decision points throughout the project
5.1.2.f the decisions that the appointing party needs to make at each key decision point DOCUMENTS
TO BE REFERRED		 PSC Project's Schedule from Project Plan
5.1.2.g the questions to which the appointing party needs answers, to make informed decisions
DOCUMENTS
TO BE REFERRED		 OIR Organizational Information Requirements PoW_0 Plan of Work (Including key decision points &
other milestones)
PLQ_0 Plain/Pre-Qualification Questions
PoW_0 Plan of Work
DOCUMENTS TO
BE GENERATED		 USE_0 BIM Uses Matrix PRS_0 Procurement Route (Schema & Table) DOCUMENTS TO
BE GENERATED		 MIS_0 Milestones Schedule (List and dates Including detailed description of the information at each key decision point)
PIR Project Information Requirements(Main Document)   BUA_0 BIM Uses Analysis
APPOINTING PARTY APPOINTING PARTY APPOINTING PARTY
5.1.4 Establish the project’s information standard 5.1.5 Establish the project's information production methods and procedures 5.1.6 Establish the project’s reference information and shared resources
SUB-ACT/ITEMS
TO CONSIDER		 5.1.4.a.1 the exchange of information within the appointing party’s
organization		 SUB-ACT/ITEMS
TO CONSIDER		 5.1.5.a the capture of existing asset information SUB-ACT/ITEMS
TO CONSIDER		 5.1.6.a.1 existing asset information from within the appointing party’s
organization
5.1.4.a.2 the exchange of information between the appointing party and
external stakeholders		 5.1.5.b the generation, review or approval of new information 5.1.6.a.2 existing asset information from adjacent asset owners (utility
companies etc.)
5.1.4.a.3 the exchange of information between the appointing party and
external operators or maintainers		 5.1.5.c the security or distribution of information 5.1.6.a.3 existing asset information under license from external providers
(mapping and imagery, etc.)
5.1.4.a.4 the exchange of information between the prospective lead
appointed party and the appointing party		 5.1.5.d the delivery of information to the appointing party 5.1.6.a.4 existing asset information within public libraries and other sources of historical records
5.1.4.a.5 the exchange of information between prospective appointed
parties on the same project		 DOCUMENTS
TO BE REFERRED		 OIR Organizational Information Requirements 5.1.6.b.1 shared resources, for example process output templates (BIM
execution plan, master information delivery plan, etc.)
5.1.4.a.6 the exchange of information between interdependent projects PIR Project Information Requirements 5.1.6.b.2 shared resources, for example information container templates
(2D/3D geometrical models, documents, etc.)
5.1.4.b the means of structuring and classifying information REM-A_0 Information Management Assignment Matrix-
(Information Man. Act.)		 5.1.6.b.3 shared resources, for example style libraries (lines, text and hatch, etc.)
5.1.4.c the method of assignment for level of information need PRS_0 Procurement Route (Schema & Table) 5.1.6.b.4 shared resources, for example object libraries (2D symbols, 3D objects, etc.)
5.1.4.d the use of information during the operational phase of the
asset		 COL-PP Collaboration Process (within the CDE) 5.1.6.c library objects defined within national and regional standards.
DOCUMENTS TO
BE GENERATED		 QUA_0 Quality Assurance Manual 
DOCUMENTS
TO BE REFERRED		 REM-A_0 Information Management Assignment Matrix-(In. Man.Activities) CCI_0 Coordination Clash Detection & Issue Management Manual DOCUMENTS
TO BE REFERRED		 OIR Organizational Information Requirements
DAS_0 Data Management According to Segregation
FRA_0 Functions Responsibilities & Authorities (Individuals List ) SCO_0 Spatial Coordination (Coordinates & Geo-Location
Methods & Procedures		 COL-PP Collaboration Process (within the CDE)
PRS_0 Procurement Route (Schema & Table) SCR_0 Security Requirements PIR Project Information Requirements
COL-PP Collaboration Process (within the CDE) PAT-MP PIM to AIM Transition Methods and Procedures (5.8.1) DOCUMENTS TO
BE GENERATED		 REF_0 Project’s reference information and shared resources
(MAIN DOCUMENT-Including PIT_0, LIB_0, SHR_0)
DOCUMENTS TO
BE GENERATED		 ICN_0 Information Container Naming Requirements CDM_0 CDM/Health & Safety Requirements 
COL-S Collaboration & Modeling & Publishing Standards
(within the CDE)		 COL-MP Collaboration  & Modeling & Publishing Methods &
Procedures (within the CDE)		 PIT_0 Project Information Table
PAT-S PIM to AIM Transition Standards (Ref.to 5.8.1) PMP_0 Project's Information Production Methods and Procedures
(MAIN DOCUMENT incl. all generated in this activity)		 LIB_0 Library Guide & Library Structure in Data Environment
INS_0 Project's Information Standard SHR_0 Shared Resources Guide & Shared Resources in CDE
APPOINTING PARTY APPOINTING PARTY
5.1.7 Establish the project's common data environment 5.1.8 Establish the project's information protocol
CDE SHALL ENABLE: 51.7.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		 SUB-ACT/ITEMS
TO CONSIDER		 5.1.8.a 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
51.7.b each field to be assigned a value from an agreed and documented codification standard 5.1.8.b any warranties or liabilities associated to the project information model
51.7.c.1 each container to have the "status (suitability)" attribute assigned 5.1.8.c background and foreground intellectual property rights of information
51.7.c.2 each container to have the "revision (and version)" attribute assigned 5.1.8.d the use of existing asset information
51.7.c.3 each container to have the "classification (in accordance with the framework defined in ISO 12006-2)" attribute assigned 5.1.8.e the use of shared resources
51.7.d the ability for information containers to transition between states 5.1.8.f the use of information during the project, including any associated licensing terms
51.7.e the recording of the name of user and date when information
container revisions transition between each state		 5.1.8.g the re-use of information following the appointment or in the event of termination
51.7.f controlled access at an information container level DOCUMENTS
TO BE REFERRED		 RAS_0 Risk Assessment Requirements (Needs to be generated in the beginning of the activity.) PMP_0 Project's Information Production Methods and Procedures
DOCUMENTS
TO BE REFERRED		 ICN_0 Information Container Naming Requirements TRA_0 Training Requirements (Ref.to.5.3.3, 5.5.1)
CLM_0 Project's Classification System & Metadata-
to be generated in the beginning of the activity		 REF_0 Project’s reference information and shared resources  INS_0 Project's Information Standard
COL-S_0 Collaboration & Modeling & Publishing Standards
(within the CDE)		 COL-S_0 Collaboration & Modeling & Publishing Standards
(within the CDE)		 OIR Organizational Information Requirements
COL-MP_0 Collaboration  & Modeling & Publishing Methods &
Procedures (within the CDE)		 COL-MP_0 Collaboration  & Modeling & Publishing Methods &
Procedures (within the CDE)
DOCUMENTS TO
BE GENERATED		 CLM_0 Project's Classification System & Metadata DOCUMENTS TO
BE GENERATED		 AIR Asset Information Requirements (Including Handover Requirements)
CDE_0 Project's CDE Structure, Standards, Methods,
Procedures (Incl. Security Requirements, COL-MP & COL-S) 		 INP_0 Project's Information Protocol
 
APPOINTING PARTY
5.2.1 Establish the appointing party’s exchange information requirements
SUB-ACT/ITEMS
TO CONSIDER		 5.2.1.a.1 establish the appointing party’s information requirements to be served during the appointment, and in doing so  shall consider their organizational information requirements (OIR)
5.2.1.a.2 establish the appointing party’s information requirements to be served during the appointment, and in doing so  shall consider their asset information requirements (AIR)
5.2.1.a.3 establish the appointing party’s information requirements to be served during the appointment, and in doing so  shall consider their project information requirements (PIR)
5.2.1.b.1 establish the level of information need required to meet each information requirement
5.2.1.b.2 Other metrics to describe the status of information, such as level of accuracy, can be added to these metrics as considered appropriate.
5.2.1.c.1 establish the acceptance criteria for each information requirement, and in doing so shall consider the project’s information standard
5.2.1.c.2 establish the acceptance criteria for each information requirement, and in doing so shall consider the project’s information production methods and procedures
5.2.1.c.3 establish the acceptance criteria for each information requirement, and in doing so shall consider the use of reference information or shared resources provided by the appointing party
5.2.1.d.1 establish the supporting information that the prospective lead appointed party might need, to  fully  understand  or  evaluate  each  information  requirement  or  its acceptance  criteria,  and in doing so shall consider existing asset information
5.2.1.d.2 establish the supporting information that the prospective LEAP might need, to  fully  understand  or  evaluate  each  information  requirement  or  its acceptance  criteria,  and in doing so shall consider shared resources
5.2.1.d.3 establish the supporting information that the prospective LEAP might need, to  fully  understand  or  evaluate  each  information  requirement  or  its acceptance  criteria,  and in doing so shall consider supporting documents or guidance material
5.2.1.d.4 establish the supporting information that the prospective LEAP might need, to  fully  understand  or  evaluate  each  information  requirement  or  its acceptance  criteria,  and in doing so shall consider references to relevant international, national or industry standards
5.2.1.d.5 establish the supporting information that the prospective LEAP might need, to  fully  understand  or  evaluate  each  information  requirement  or  its acceptance  criteria,  and in doing so shall consider exemplars of similar information deliverables
5.2.1.e.1 establish the dates, relative to the project’s information delivery milestones and appointing party’s key decision points, that each requirement has to be met, and in doing so shall consider the time needed by the appointing party to review and accept information
5.2.1.e.2 establish the dates, relative to the project’s information delivery milestones and appointing party’s key decision points, that each requirement has to be met, and in doing so shall consider the appointing party’s internal assurance processes
DOCUMENTS
TO BE REFERRED		 OIR Organizational Information Requirements PMP_0 Project's Information Production Methods and Procedures PIT_0 Project Information Table
PIR Project Information Requirements INS_0 Project's Information Standard LIB_0 Library Guide & Library Structure in Data Environment
AIR Asset Information Requirements (Including Handover Requirements) PSC Project's Schedule from Project Plan SHR_0 Shared Resources Guide & Shared Resources in CDE
LOIN_0 Level of Information Need Manual (Needs to be generated in the beginning of
the activity.)		 PoW_0 Plan of Work (Including key decision points & other milestones) QUA_0 Quality Assurance Manual 
CCI_0 Coordination Clash Detection & Issue Management Manual
LOA_0 Level of Accuracy Table (Needs to be generated in the beginning of the activity.) MIS_0 Milestones Schedule AAP APOP Asurance Processes (Needs to be available already.)
RAS_0 Risk Assessment Requirements INP_0 Project's Information Protocol REF_0 Project’s reference information and shared resources 
CDE-SMP_0 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Req. and COL-PP)  BUA_0 BIM Uses Analysis USE_0 BIM Uses Matrix
DOCUMENTS TO
BE GENERATED		 EIR_APOP Exchange Information Requirements (Appointing Party's)
(MAIN DOCUMENT incl. all generated in this activity)		 ACR_0 Acceptance Criteria Manual PoW_1 Plan of Work (Update as per this activity)
SUP-LEAP_0 Supporting Information for LEAP MIS_1 Milestones Schedule (Update as per this activity)
CCI_1 Coordination Clash Detection & Issue Management Manual
LOIN_0 Level of Information Need Manual QUA_1 Quality Assurance Manual  LOA_0 Level of Accuracy Table
 
APPOINTING PARTY APPOINTING PARTY
5.2.2 Assemble reference information and shared resources 5.2.3 Establish tender response requirements and evaluation criteria
SUB-ACT/ITEMS
TO CONSIDER		 5.2.2.a reference information or shared resources identified during
project initiation		 SUB-ACT/ITEMS
TO CONSIDER		 5.2.3.a the contents of the delivery team’s (pre-appointment) BIM execution plan
5.2.2.b information generated during previous stages of the project 5.2.3.b the competency of the prospective individuals undertaking the information management function on behalf of the delivery team
5.2.2.c the suitability for which the information can be used by the prospective lead appointed party 5.2.3.c the prospective lead appointed party’s assessment of the delivery team’s capability and capacity
DOCUMENTS
TO BE REFERRED		 PIT_0 Project Information Table 5.2.3.d the delivery team’s proposed mobilization plan
LIB_0 Library Guide & Library Structure in Data Environment 5.2.3.e the delivery team’s information delivery risk assessment
SHR_0 Shared Resources Guide & Shared Resources in CDE
REF_0 Project’s reference information and shared resources 
CDE_0 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP)  DOCUMENTS
TO BE REFERRED		 RAS_0 Risk Assessment Requirements MOB_I Delivery team's mobilization plan (Initial-Proposed)
to be generated in the beginning of the activity
DOCUMENTS TO
BE GENERATED		 PIT_1 Project Information Table EIR_APOP Exchange Information Requirements (Appointing Party's)
LIB_1 Library Guide & Library Structure in Data Environment ACR_0 Acceptance Criteria Manual REM-A_0 Information Management Assignment Matrix-(In. Man.Activities)
SHR_1 Shared Resources Guide & Shared Resources in CDE DOCUMENTS TO
BE GENERATED		 TEN-CR Tender Response Requirements & Evaluation Criteria (MAIN DOCUMENT) CCA_IT IT-Information Technology Capability & Capacity Assessment
Form
REF_1 Project’s reference information and shared resources
(MAIN DOCUMENT-Including PIT_1, LIB_1, SHR_1)		 CCA_IM Information Management Capability & Capacity Assessment Form RAS_1 Risk Assessment
CCA_IP Information Production Capability & Capacity Assessment Form MOB_I Delivery team's mobilization plan (Initial-Proposed)
to be generated in the beginning of the activity
APPOINTING PARTY
5.2.4 Compile invitation to tender information
SUB-ACT/ITEMS
TO CONSIDER		 5.2.4.a the appointing party’s exchange information requirements
5.2.4.b the  relevant  reference  information  and  shared  resources  (within  the  project’s common  data environment)
5.2.4.c the tender response requirements and evaluation criteria (if applicable)
5.2.4.d the project information delivery milestones
5.2.4.e the project’s information standard
5.2.4.f the project’s information production methods and procedure
5.2.4.g the project information protocol
DOCUMENTS
TO BE REFERRED		 EIR_APOP Exchange Information Requirements (Appointing Party's) MIS_1 Milestones Schedule (List and dates Including detailed description of the information at each key decision point) REF_1 Project’s reference information and shared resources 
TEN-CR_0 Tender Response Requirements & Evaluation Criteria PMP_0 Project's Information Production Methods and Procedures
INP_0 Project's Information Protocol INS_0 Project's Information Standard
DOCUMENTS TO
BE GENERATED		 TEN INVITATION TO TENDER PACKAGE (MAIN DOCUMENT-Including EIR_APOP, TEN-CR_0, INP_0, MIS_1, PMP_0, INS_0, REF-1)
 
PROSPECTIVE LEAD APPOINTED PARTY
5.3.1 Nominate individuals to undertake the information management function
SUB-ACT/ITEMS
TO CONSIDER		 5.3.1.a the appointing party’s exchange information requirements
5.3.1.b the tasks that the prospective appointed party or third party will be responsible for
5.3.1.c the authority that the prospective lead appointed party will delegate to the prospective appointed party or third party
5.3.1.d the competency (knowledge or skills) that the individuals undertaking the function will need
5.3.1.e probity arrangements if potential conflicts of interest may arise
DOCUMENTS
TO BE REFERRED		 OIR Organizational Information Requirements REM-A_0 Information Management Assignment Matrix FRA_0 Functions Responsibilities & Authorities (Individuals List )
PRS_0 Procurement Route (Schema & Table) EIR_APOP Exchange Information Requirements (Appointing Party's)
DOCUMENTS TO
BE GENERATED		 FRA_1 Functions Responsibilities & Authorities (Individuals List )
(Updated as per this activity by Prospective Lead Appointed Party)		 REM-A_1 Information Management Assignment Matrix-(Responsibility Matrix Information Management Activities) (Updated as per this activity by Prospective Lead Appointed Party) PRS_1 Procurement Route (Schema & Table)
(Updated as per this activity by Prospective Lead Appointed Party)
 
PROSPECTIVE LEAD APPOINTED PARTY
5.3.2 Establish the delivery team's (pre-appointment) BIM execution plan
SUB-ACT/ITEMS
TO CONSIDER		 5.3.2.a the proposed names and professional résumés of the individuals who will undertake information management function within the delivery team
5.3.2.b.1 the delivery team’s information delivery strategy, containing: the  delivery  team’s  approach  to  meeting  the  appointing  party’s  exchange  information requirements
5.3.2.b.2 the delivery team’s information delivery strategy, containing: set of objectives/goals for the collaborative production of information
5.3.2.b.3 the delivery team’s information delivery strategy, containing: an overview of the delivery team’s organizational structure and commercial relationships
5.3.2.b.4 the delivery team’s information delivery strategy, containing: an overview of the delivery team’s composition, in the form of one or more task teams
5.3.2.c the proposed federation strategy to be adopted by the delivery team
5.3.2.d the delivery team’s high-level responsibility matrix, containing the allocated responsibility for each element of the information model and the key deliverables associated to each element
5.3.2.e.1 any  proposed  additions  or  amendments  to  the  project’s  information  production  methods  and procedures that the delivery team require in order to facilitate the effective:  capture of existing asset information,
5.3.2.e.2 any  proposed  additions  or  amendments  to  the  project’s  information  production  methods  and procedures that the delivery team require in order to facilitate the effective:  generation, review, approval and authorization of information,
5.3.2.e.3 any  proposed  additions  or  amendments  to  the  project’s  information  production  methods  and procedures that the delivery team require in order to facilitate the effective:  security and distribution of information
5.3.2.e.4 any  proposed  additions  or  amendments  to  the  project’s  information  production  methods  and procedures that the delivery team require in order to facilitate the effective:  delivery of information to the appointing party
5.3.2.f.1 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
5.3.2.f.2 any proposed additions or amendments to the project’s information standard that the delivery team require to facilitate the effective: distribution of information to external parties
5.3.2.f.3 any proposed additions or amendments to the project’s information standard that the delivery team require to facilitate the effective: delivery of information to the appointing party
5.3.2.g a proposed schedule of software (including versions), hardware and IT infrastructure the delivery team intend to adopt
DOCUMENTS
TO BE REFERRED		 FRA_1 Functions Responsibilities & Authorities (Individuals List ) REM-A_1 Information Management Assignment Matrix-(Resp. Matrix Infor. Man. Act.)  PRS_0 Procurement Route (Schema & Table)
PMP_0 Project's Information Production Methods and Procedures INS_0 Project's Information Standard INP_0 Project's Information Protocol
CCI_1 Coordination Clash Detection & Issue Management Manual QUA_1 Quality Assurance Manual      COL-S_0 Collaboration & Modeling & Publishing Standards
(within the CDE)
LOIN_0 Level of Information Need Manual     USE_0 BIM Uses Matrix COL-MP_0 Collaboration  & Modeling & Publishing Methods &
Procedures (within the CDE)
EIR_APOP Exchange Information Requirements (Appointing Party's) BUA_0 BIM Uses Analysis ICN_0 Information Container Naming Requirements
DOCUMENTS TO
BE GENERATED		 PRE-BEP Delivery team’s Pre-appointment BIM execution plan
(MAIN DOCUMENT incl. all generated in this activity)		 HLRM_0 Delivery team’s High Level Responsibility Matrix INS_1 Project's Information Standard
DT-IDS_0 Delivery team’s information delivery strategy SCH-IT_0 Schedule of Software, Hardware & IT
COL-MP_1 Collaboration  & Modeling & Publishing Methods & Procedures (within the CDE) COL-S_1 Collaboration&Modeling&Publishing Standards (within the CDE) 
CCI_2 Coordination Clash Detection & Issue Management Manual QUA_2 Quality Assurance Manual  PRS_1 Procurement Route (Schema & Table)
LOIN_1 Level of Information Need Manual BUA_1 BIM USES ANALYSIS  ICN_1 Information Container Naming Requirements
FSB_0 Federation Strategy & Information Container Breakdown Structure PMP_1 Project's Information Production Methods and Procedures USE_1 BIM Uses Matrix
TASK TEAM-1 TASK TEAM-2 TASK TEAM-n
5.3.3 Assess each task team capability and capacity 5.3.3 Assess each task team capability and capacity 5.3.3 Assess each task team capability and capacity
SUB-ACT/ITEMS
TO CONSIDER		 5.3.3.a.1 the task team’s capability and capacity to manage information, based upon:the relevant experience and number of task team members who have managed information in accordance with the proposed information delivery strategy;  SUB-ACT/ITEMS
TO CONSIDER		 5.3.3.a.1 the task team’s capability and capacity to manage information, based upon:the relevant experience and number of task team members who have managed information in accordance with the proposed information delivery strategy;  SUB-ACT/ITEMS
TO CONSIDER		 5.3.3.a.1 the task team’s capability and capacity to manage information, based upon:the relevant experience and number of task team members who have managed information in accordance with the proposed information delivery strategy; 
5.3.3.a.2 the task team’s capability and capacity to manage information, based upon: the relevant education and training available to task team members 5.3.3.a.2 the task team’s capability and capacity to manage information, based upon: the relevant education and training available to task team members 5.3.3.a.2 the task team’s capability and capacity to manage information, based upon: the relevant education and training available to task team members
5.3.3.b.1 the task team’s capability and capacity to produce information, based upon: the relevant experience and number of task team members who have produced information in accordance with the project’s information production methods and procedures 5.3.3.b.1 the task team’s capability and capacity to produce information, based upon: the relevant experience and number of task team members who have produced information in accordance with the project’s information production methods and procedures 5.3.3.b.1 the task team’s capability and capacity to produce information, based upon: the relevant experience and number of task team members who have produced information in accordance with the project’s information production methods and procedures
5.3.3.b.2 the task team’s capability and capacity to produce information, based upon: the relevant education and training available to task team members 5.3.3.b.2 the task team’s capability and capacity to produce information, based upon: the relevant education and training available to task team members 5.3.3.b.2 the task team’s capability and capacity to produce information, based upon: the relevant education and training available to task team members
5.3.3.c.1 the availability of information technology (IT) within the task team, based upon: the proposed IT schedule 5.3.3.c.1 the availability of information technology (IT) within the task team, based upon: the proposed IT schedule 5.3.3.c.1 the availability of information technology (IT) within the task team, based upon: the proposed IT schedule
5.3.3.c.2 the availability of information technology (IT) within the task team, based upon: the specification and quantity of the task team’s hardware 5.3.3.c.2 the availability of information technology (IT) within the task team, based upon: the specification and quantity of the task team’s hardware 5.3.3.c.2 the availability of information technology (IT) within the task team, based upon: the specification and quantity of the task team’s hardware
5.3.3.c.3 the availability of information technology (IT) within the task team, based upon: the architecture, maximum capacity and current utilization of the task team’s IT infrastructure;  5.3.3.c.3 the availability of information technology (IT) within the task team, based upon: the architecture, maximum capacity and current utilization of the task team’s IT infrastructure;  5.3.3.c.3 the availability of information technology (IT) within the task team, based upon: the architecture, maximum capacity and current utilization of the task team’s IT infrastructure; 
5.3.3.c.4 the availability of information technology (IT) within the task team, based upon: the associated support and service level agreements available to the task team 5.3.3.c.4 the availability of information technology (IT) within the task team, based upon: the associated support and service level agreements available to the task team 5.3.3.c.4 the availability of information technology (IT) within the task team, based upon: the associated support and service level agreements available to the task team
DOCUMENTS
TO BE REFERRED		 TRA_0 Training Requirements DOCUMENTS
TO BE REFERRED		 TRA_0 Training Requirements DOCUMENTS
TO BE REFERRED		 TRA_0 Training Requirements
PMP_1 Project's Information Production Methods and Procedures PMP_1 Project's Information Production Methods and Procedures PMP_1 Project's Information Production Methods and Procedures
TEN-CR_0 Tender Response Requirements & Evaluation Criteria TEN-CR_0 Tender Response Requirements & Evaluation Criteria TEN-CR_0 Tender Response Requirements & Evaluation Criteria
CCA_IM Information Management Capability & Capacity Assessment Form CCA_IM Information Management Capability & Capacity Assessment Form CCA_IM Information Management Capability & Capacity Assessment Form
CCA_IP Information Production Capability & Capacity Assessment Form CCA_IP Information Production Capability & Capacity Assessment Form CCA_IP Information Production Capability & Capacity Assessment Form
CCA_IT IT-Information Technology Capability & Capacity Assessment Form CCA_IT IT-Information Technology Capability & Capacity Assessment Form CCA_IT IT-Information Technology Capability & Capacity Assessment Form
DOCUMENTS TO
BE GENERATED		 TT-IDS-0 Task Teams' Information Delivery Strategies DOCUMENTS TO
BE GENERATED		 TT-IDS-0 Task Teams' Information Delivery Strategies DOCUMENTS TO
BE GENERATED		 TT-IDS-0 Task Teams' Information Delivery Strategies
TT-CCA-1 Capability and capacity assessment of Task Team-1 TT-CCA-1 Capability and capacity assessment of Task Team-1 TT-CCA-1 Capability and capacity assessment of Task Team-1
 
  PROSPECTIVE LEAD APPOINTED PARTY  
  5.3.4 Establish the delivery team's capability and capacity  
  SUB-ACT/ITEMS
TO CONSIDER		 The prospective lead appointed party shall establish the delivery team’s capability and capacity by aggregating the assessments undertaken by each task team to produce a summary of the delivery team’s capability to manage and produce information and its capacity for timely delivery of the information.  
   
  DOCUMENTS
TO BE REFERRED		 TT-IDS_0 Task Teams' Information Delivery Strategies  
  TT-CCA_0 Capability and capacity assessment of Task Teams  
  RAS_1 Risk Assessment Requirements  
  DOCUMENTS TO
BE GENERATED		 REM-A_2 Information Management Assignment Matrix (Updated as per this activity by Prospective Lead Appointed Party)  
  DTCC_0 Delivery Team's Capability and Capacity Assessment  
 
PROSPECTIVE LEAD APPOINTED PARTY PROSPECTIVE LEAD APPOINTED PARTY
5.3.5 Establish the delivery team’s mobilization plan 5.3.6 Establish the delivery team’s risk register
SUB-ACT/ITEMS
TO CONSIDER		 5.3.5.a approach,  timescales  and responsibilities for:testing and documenting the proposed information production methods and procedures;  SUB-ACT/ITEMS
TO CONSIDER		 5.3.6.a consider risks associated with:assumptions the delivery team have made in relation to the appointing party’s exchange information requirements
5.3.5.b approach,  timescales  and responsibilities for:testing the information exchanges between task teams;
5.3.5.c approach,  timescales  and responsibilities for:testing the information delivery to the appointing party; 5.3.6.b consider risks associated with:meeting the appointing party’s project
information delivery milestones;
5.3.5.d approach,  timescales  and responsibilities for:configuring and testing the project’s common data environment CDE in accordance with 5.1.7;
5.3.5.e approach,  timescales  and responsibilities for:configuring and testing the delivery team’s (distributed) CDE and its connectivity to the project CDE (if applicable) in accordance with 5.1.7;
 5.3.6.c consider risks associated with:the contents of the project
information protocol;
5.3.5.f approach,  timescales  and responsibilities for:procuring,   implementing,   configuring   and   testing   additional   software,   hardware   and   IT infrastructure;
 5.3.6.d consider risks associated with:achieving the proposed information delivery
strategy;
5.3.5.g approach,  timescales  and responsibilities for:developing additional shared resources to be used by the delivery team;
5.3.5.h approach,  timescales  and responsibilities for:developing and delivering education (knowledge required) to delivery team members;  5.3.6.e consider risks associated with:adopting the project’s information standard and
information production methods and procedures; 
5.3.5.i approach,  timescales  and responsibilities for:developing and delivering training (skills required) to the delivery team members;
5.3.5.j approach,  timescales  and responsibilities for:recruiting additional members of the delivery team to achieve the required capacity;  5.3.6.f consider risks associated with:inclusion (or non-inclusion) of proposed
amendments to the project’s information standard;
5.3.5.k approach,  timescales  and responsibilities for:supporting individuals and organizations that join the delivery team during the appointment.
DOCUMENTS
TO BE REFERRED		 DTCC_0 Delivery Team's Capability and Capacity Assessment SCH-IT_0 Schedule of Software, Hardware & IT 5.3.6.g consider risks associated with:the mobilization of the delivery team to achieve
the required capability and capacity.
PMP_1 Project's Information Production Methods and Procedures REM-A_2 Information Management Assignment Matrix
CDE_0 Project's CDE Structure, Standards, Methods, Procedures EIR_APOP Exchange Information Requirements (Appointing Party's) DOCUMENTS
TO BE REFERRED		 EIR_APOP Exchange Information Requirements (Appointing Party's)
DT-IDS_0 Delivery team’s information delivery strategy TRA_0 Training Requirements MIS_1 Milestones Schedule (List and dates Including detailed description of the information at each key decision point)
FRA_1 Functions Responsibilities & Authorities (Individuals List ) PRS_1 Procurement Route (Schema & Table) INP_0 Project's Information Protocol
REM-A_2 Information Management Assignment Matrix-
(Responsibility Matrix Information Management Activities) 		 HLRM_0 Delivery team’s High Level Responsibility Matrix RAS_0 Risk Assessment Requirements
DT-IDS_0 Delivery team’s information delivery strategy
DTCC_0 Delivery Team's Capability and Capacity Assessment
MOB_I Delivery team's mobilization plan (Initial-Proposed) INS_1 Project's Information Standard
PMP_1 Project's Information Production Methods and Procedures
DOCUMENTS TO
BE GENERATED		 CDE_1 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) -(Data Exchange Process Update) DOCUMENTS TO
BE GENERATED		 DRR_0 Delivery team’s Risk Register (Information delivery
risk assessment)
MOB_0 Delivery Team's Mobilization Plan
PROSPECTIVE LEAD APPOINTED PARTY  
5.3.7 Compile the delivery team's tender response  
SUB-ACT/ITEMS
TO CONSIDER		 5.3.7.a (pre-appointment) BIM execution plan (5.3.2);  
5.3.7.b capability and capacity assessment summary (5.3.4);   
5.3.7.c mobilization plan (5.3.5);   
5.3.7.d information delivery risk assessment (5.3.6  
DOCUMENTS
TO BE REFERRED		 PRE-BEP Delivery team’s Pre-appointment BIM execution plan  
DTCC_0 Delivery Team's Capability and Capacity Assessment  
DRR_0 Delivery team’s Risk Register (Information delivery risk assessment)  
MOB_0 Delivery Team's Mobilization Plan  
INP_0 Project's Information Protocol  
DOCUMENTS TO  BE GENERATED  DTTR Delivery team’s Tender Response (Incl. PRE-BEP, DRR, DTCC, MOB)  
      INP_1 Project's Information Protocol (Updated as per previous activities)    
 
LEAD APPOINTED PARTY
5.4.1 Confirm the delivery team's BIM execution plan
SUB-ACT/ITEMS
TO CONSIDER		 5.4.1.a confirm the names of the individual(s) who will undertake the information management function within the delivery team;
5.4.1.b update the delivery team’s information delivery strategy (as required);
5.4.1.c update the delivery team’s high-level responsibility matrix (as required);
5.4.1.d confirm  and  document  the  delivery  team’s  proposed  information  production  methods  and procedures;
5.4.1.e agree with the appointing party any  additions  or  amendments  to the project information standard;
5.4.1.f confirm the schedule of software, hardware and IT infrastructure the delivery team will use.
DOCUMENTS
TO BE REFERRED		 OIR Organizational Information Requirements AIR Asset Information Requirements EIR_APOP Exchange Information Requirements (Appointing Party's)
(MAIN DOCUMENT incl. all generated in this activity)
REM-A_2 Information Management Assignment Matrix INP_1 Project's Information Protocol TEN-CR_0 Tender Response Requirements & Evaluation Criteria
CCI_2 Coordination Clash Detection & Issue Management Manual QUA_2 Quality Assurance Manual USE_1 BIM Uses Matrix
PLQ_0 Plain/Pre-Qualification Questions MIS_1 Milestones Schedule  MOB_0 Delivery Team's Mobilization Plan
FRA_1 Functions Responsibilities & Authorities (Individuals List ) ICN_1 Information Container Naming Requirements DTCC_0 Delivery Team's Capability and Capacity Assessment
LOIN_1 Level of Information Need Manual PMP_1 Project's Information Production Methods and Procedures DRR_0 Delivery team’s Risk Register (Information delivery risk asses.)
PIR Project Information Requirements INS_1 Project's Information Standard BUA_1 BIM Uses Analysis
CDE_1 Project's CDE Structure, Standards, Methods, Procedures (In. Sec. Req.& COL-PP)  HLRM_0 Delivery team’s High Level Responsibility Matrix PIT_1 Project Information Table
DT-IDS_0 Delivery team’s information delivery strategy MOB_0 Delivery Team's Mobilization Plan PRS_1 Procurement Route (Schema & Table)
SCH-IT_0 Schedule of Software, Hardware & IT SUP_LEAP_0 Supporting Information for LEAP TT-CCA-0 Capability and capacity assessment of Task Team
LOA_0 Levelof Accuracy TRA_0 Training Requirements PAT-S_0 PIM to AIM Transition Standards
RAS_0 Risk Assessment Requirements ACR_0 Acceptance Criteria Manual SCR_0 Security Requirements
SCO_1 Spatial Coordination (Coordinates & Geo-Location) Methods & Procedures SCR_0 Security Requirements CDM_0 Health and Safety Requirements
DAS_1 Data Management According to Segregation PAT-MP_0 PIM to AIM Transition Methods & Procedures LIB_1 Library Guide & Library Structure in Data Environment
TT-IDS-0 Task Teams' Information Delivery Strategies CLM_0 Project's Classification System SHR_1 Shared Resources Guide & Shared Resources in CDE
COL-MP_1 Collaboration  & Modeling & Publishing Methods & Procedures (within the CDE) COL-S_1 Collaboration & Modeling & Publishing Standards (within the CDE)  FSB_0 Federation Strategy&Information Container Breakdown Structure
PRE-BEP Delivery team’s Pre-appointment BIM execution plan REF_1 Project’s reference information and shared resources  PAT-S_0 PIM to AIM Transition Standards
DOCUMENTS TO  BE GENERATED
(as Annex, Appendix or Section Inside BEP)		 REM-A_3 Information Management Assignment Matrix-(Responsibility Matrix Information Management Activities) (Updated as per this activity and REM-B-1 by LEAP FRA_2 Functions Responsibilities & Authorities (Individuals List ) PIT_2 Project Information Table
USE_2 BIM Uses Matrix TEN-CR_1 Tender Response Requirements & Evaluation Criteria
PLQ_1 Plain/Pre-Qualification Questions PRS_2 Procurement Route (Schema & Table) BUA_2 BIM Uses Analysis
SUP_LEAP_1 Supporting Information for LEAP LOIN_2 Level of Information Need Manual
CDE_2 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security
Requirements and COL-PP) -(Data Exchange Process Update)		 REF_2 Project’s reference information and shared resources  LIB_2 Library Guide & Library Structure in Data Environment
MIS_2 Milestones Schedule SHR_2 Shared Resources Guide & Shared Resources in CDE
INS_2 Project's Information Standard TRA_1 Training Requirements INP_2 Project's Information Protocol
LOA_1 Levelof Accuracy CLM_1 Project's Classification System ICN_2 Information Container Naming Requirements
SCO_2 Spatial Coordination (Coordinates & Geo-Location) Methods & Procedures PMP_2 Project's Information Production Methods and Procedures PAT-S_1 PIM to AIM Transition Standards
DAS_2 Data Management According to Segregation CHL Change Log Template SCR_1 Security Requirements
CCI_3 Coordination Clash Detection & Issue Management Manual CLAM Clash Detection Matrix QUA_3 Quality Assurance Manual
As Annex= DT-IDS_1 Delivery Team's Imformation Delivery Strategy PAT-MP_1 PIM to AIM Transition Methods & Procedures CDM_1 Health and Safety Requirements
Magenta Color TT-CCA_1 Capability and Capacity Assessment of Task Teams ACR_1 Acceptance Criteria Manual RAS_1 Risk Assessment Requirements
Sample:HLRM_1 TT-IDS-1 Task Teams' Information Delivery Strategies CCA_IM Information Management Capability and Capacity Assessment Form  CCA_IP Information Production Capability and Capacity Assessment Form
  COL-MP_2 Collaboration  & Modeling & Publishing Methods & Procedures (within the CDE) COL-S_2 Collaboration & Modeling & Publishing Standards (within the CDE)  CCA_IT Information Technology  Capability and Capacity Assessment Form
  MOB_1 Delivery Team's Mobilization Plan DTCC_1 Delivery Team's Capability and Capacity Assessment DRR_1 Delivery Team's Risk Register
As Appendix= IDM Information Delivery Manual DT-IDS_1 Delivery team’s information delivery strategy FSB_1 Federation Strategy & Information Container Breakdown Structure
Red Color HLRM_1 Delivery team’s High Level Responsibility Matrix TIDP-TMP Task Information Delivery Plan Template MIDP_0 Master Information Delivery Plan Initial Version (Template)
SampleCLL-TMP EIR-LEAP-TMP Lead Appointed Party's Exchange Information Requirements Template (Ref.to5.4.3) SCH-IT_1 Schedule of Software, Hardware & IT DRM_0 Delivery team’s detailed responsibility matrix (Template)
  PMP-RR-TMP Project's Information Production Methods & Procedures Test Report Temp.(Ref.to 5.5.2) MOIR-TMP Mobilization of information technology report template (Ref.to 5.5.2) MORE-TMP Mobilization of resources report template (Ref.to 5.5.1)
As Section Inside IRR-TT-TMP Task Team's Information Review (by LEAP)  Report Template (Ref.to.5.6.4) QUA-TT-TMP Task Team's Quality Assurance Check Report Template  (Ref.to.5.6.3) CR-TT-TMP Task Team's Access Check Report Template (Ref.to.5.6.1)
the BEP= TTS-RR-TMP Task Teams Submittals Review Report Template (Ref.to.5.7.2) IMR-DT-TMP Delivery Team's Information Model Review Report Template (Ref.to.5.6.5) PAR-TMP PIM to AIM Requirements Template (Ref.to 5.8.1)
Black Color SBL-TMP Submittal List Templates (Ref.to.5.7.1 & 3) PIM-RR-TMP PIM Review Report Template (Ref.to.5.7.4) RLL-TMP Lessons learned record (template Ref.to.5.8.2)
Sample:SCH-IT_1 * Templates as per ISO 19650-3 CLL-TMP Capture lessons learned (template Ref.to.5.8.2)
Capture lessons learned document will be updated at the end of each main phase		 BEP_0 Delivery Team's Post Appointment BEP (MAIN DOCUMENT)
LEAD APPOINTED PARTY LEAD APPOINTED PARTY
5.4.2 Establish the delivery team’s detailed responsibility matrix 5.4.3 Establish the lead appointed party’s exchange information requirements
SUB-ACT/ITEMS
TO CONSIDER		 5.4.2.a.1 refine the high level resp. matrix to establish the detailed resp. matrix, which identifies: what information is to be produced SUB-ACT/ITEMS
TO CONSIDER		 5.4.3.a.1 define each information requirement, and in doing so shall consider: the appointing party’s information requirements, which the lead appointed party requires the
appointed party to meet
5.4.2.a.2 refine the high level resp. matrix to establish the detailed resp. matrix, which identifies: when the information is to be exchanged and with whom 5.4.3.a.2 define each information requirement, and in doing so shall consider: any additional information requirements that the lead appointed party requires the appointed
party to meet
5.4.2.a.3 refine the high level resp. matrix to establish the detailed resp. matrix, which identifies: which task team is responsible for its production 5.4.3.b.1 establish the level of information need required to meet each information requirement.
5.4.2.b.1 consider: the information delivery milestones 5.4.3.c.1 establish the acceptance criteria for each information requirement, and in doing so shall consider the project’s information standard
5.4.2.b.2 consider: the high level responsibility matrix 5.4.3.c.2 establish the acceptance criteria for each information requirement, and in doing so shall consider the project’s information production methods and procedures
5.4.2.b.3 consider: the project’s information production methods and
procedures		 5.4.3.c.3 establish the acceptance criteria for each information requirement, and in doing so shall consider the use of reference information or shared resources provided by the appointing party or lead appointed party
5.4.2.b.4 consider: the elements of information container breakdown structure allocated to each task team 5.4.3.d.1 establish the dates that need to be met for each requirement, relative to the project's information delivery milestones, and in doing so shall consider: the time needed by the lead appointed party to review and authorize information
5.4.2.b.5 consider: the dependencies on the information production
process		 5.4.3.d.2 establish the dates that need to be met for each req., relative to the project's information delivery milestones, and in doing so shall consider: the lead appointed party’s internal assurance processes
DOCUMENTS
TO BE REFERRED		 MIS_2 Milestones Schedule 5.4.3.e.1 establish  the  supporting  information  that  the  appointed  party  might  need,  to  fully understand or evaluate each information requirement or its acceptance criteria, and in doing so shall consider: existing asset information
HLRM_1 Delivery team’s High Level Responsibility Matrix 5.4.3.e.2 establish  the  supporting  information  that  the  appointed  party  might  need,  to  fully understand or evaluate each information requirement or its acceptance criteria, and in doing so shall consider: shared resources
PMP_2 Project's Information Production Methods and Procedures 5.4.3.e.3 establish  the  supporting  information  that  the  appointed  party  might  need,  to  fully understand or evaluate each information requirement or its acceptance criteria, and in doing so shall consider: supporting documents or guidance material
FSB_1 Federation Strategy & Information Container Breakdown Structure 5.4.3.e.4 establish  the  supporting  information  that  the  appointed  party  might  need,  to  fully understand or evaluate each information requirement or its acceptance criteria, and in doing so shall consider: references to relevant international, national or industry standards
REM-A_3 Information Management Assignment Matrix-(Responsibility Matrix Information
Management Activities)		 5.4.3.e.5 establish  the  supporting  information  that  the  appointed  party  might  need,  to  fully understand or evaluate each information requirement or its acceptance criteria, and in doing so shall consider: exemplars of similar information deliverables
FRA_2 Functions Responsibilities & Authorities (Individuals List ) DOCUMENTS
TO BE REFERRED		 EIR-APOP Exchange Information Requirements (Appointing Party's) OIR Organizational Information Requirements
CDE_2 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP)  LOIN_2 Level of Information Need Manual  PIR Project Information Requirements
AIR Asset Information Requirements
INS_2 Project's Information Standard LOA_1 Level of Accuracy Table
PRS_2 Procurement Route (Schema & Table) PMP_2 Project's Information Production Methods and Procedures PSC Project's Schedule from Project Plan
DRM_0 Delivery team’s detailed responsibility matrix (Template) REF_1 Project’s reference information and shared resources  RAS_1 Risk Assessment Requirements
DOCUMENTS TO  BE GENERATED
(as Annex, Appendix or Section Inside BEP)		 DRM_1 Delivery team’s detailed responsibility matrix SUP-APP Supporting Information for APP ACR_1 Acceptance Criteria Manual
QUA_3 Quality Assurance, Coordination & Issue Management Manual  PoW_1 Plan of Work (Including key decision points & other milestones)
INS_2 Project's Information Standard MIS_2 Milestones Schedule
INP_2 Project's Information Protocol
DOCUMENTS TO BE GENERATED EIR-LEAP lead appointed party’s exchange information requirements (Main Document) SUP-APP Supporting Information for APP
TASK TEAM-1 TASK TEAM-2 TASK TEAM-n
5.4.4 Establish the task information delivery plan(s) 5.4.4 Establish the task information delivery plan(s) 5.4.4 Establish the task information delivery plan(s)
SUB-ACT/ITEMS
TO CONSIDER		 5.4.a.1 consider: the project’s information delivery milestones; SUB-ACT/ITEMS
TO CONSIDER		 5.4.a.1 consider: the project’s information delivery milestones; SUB-ACT/ITEMS
TO CONSIDER		 5.4.a.1 consider: the project’s information delivery milestones;
5.4.a.2 consider: the task team’s responsibilities within the detailed
responsibility matrix; 		 5.4.a.2 consider: the task team’s responsibilities within the detailed
responsibility matrix; 		 5.4.a.2 consider: the task team’s responsibilities within the detailed
responsibility matrix; 
5.4.a.3 consider: the lead appointed party’s information requirements; 5.4.a.3 consider: the lead appointed party’s information requirements; 5.4.a.3 consider: the lead appointed party’s information requirements;
5.4.a.4 consider: the availability of shared resources within the
delivery team; 		 5.4.a.4 consider: the availability of shared resources within the
delivery team; 		 5.4.a.4 consider: the availability of shared resources within the
delivery team; 
5.4.a.5 consider: the time the task team will need to produce (generate, coordinate, review and approve) inform 5.4.a.5 consider: the time the task team will need to produce (generate, coordinate, review and approve) inform 5.4.a.5 consider: the time the task team will need to produce (generate, coordinate, review and approve) inform
5.4.b.1 The TIDP shall list and identify, for each container,
the name and title;		 5.4.b.1 The TIDP shall list and identify, for each container,
the name and title;		 5.4.b.1 The TIDP shall list and identify, for each container,
the name and title;
5.4.b.2 The TIDP shall list and identify, for each container,
the predecessors or dependencies;		 5.4.b.2 The TIDP shall list and identify, for each container,
the predecessors or dependencies;		 5.4.b.2 The TIDP shall list and identify, for each container,
the predecessors or dependencies;
5.4.b.3 The TIDP shall list and identify, for each container,
the level of information need		 5.4.b.3 The TIDP shall list and identify, for each container,
the level of information need		 5.4.b.3 The TIDP shall list and identify, for each container,
the level of information need
5.4.b.4 The TIDP shall list and identify, for each container,
the (estimated) production duration		 5.4.b.4 The TIDP shall list and identify, for each container,
the (estimated) production duration		 5.4.b.4 The TIDP shall list and identify, for each container,
the (estimated) production duration
5.4.b.5 The TIDP shall list and identify, for each container,
the information author responsible for its production		 5.4.b.5 The TIDP shall list and identify, for each container,
the information author responsible for its production		 5.4.b.5 The TIDP shall list and identify, for each container,
the information author responsible for its production
5.4.b.6 The TIDP shall list and identify, for each container,
the  delivery milestones.		 5.4.b.6 The TIDP shall list and identify, for each container,
the  delivery milestones.		 5.4.b.6 The TIDP shall list and identify, for each container,
the  delivery milestones.
DOCUMENTS
TO BE REFERRED		 MIS_2 Milestones Schedule DOCUMENTS
TO BE REFERRED		 MIS_2 Milestones Schedule DOCUMENTS
TO BE REFERRED		 MIS_2 Milestones Schedule
EIR-LEAP lead appointed party’s exchange information requirements EIR-LEAP lead appointed party’s exchange information requirements EIR-LEAP lead appointed party’s exchange information requirements
ICN_2 Information Container Naming Requirements ICN_2 Information Container Naming Requirements ICN_2 Information Container Naming Requirements
PSC Project's Schedule from Project Plan PSC Project's Schedule from Project Plan PSC Project's Schedule from Project Plan
PoW_1 Plan of Work (Including key decision points & other milestones) PoW_1 Plan of Work (Including key decision points & other milestones) PoW_1 Plan of Work (Including key decision points & other milestones)
DOCUMENTS TO
BE GENERATED		 TIDP_1 Task Team 1's Task Information Delivery Plan DOCUMENTS TO
BE GENERATED		 TIDP_2 Task Team 2's Task Information Delivery Plan DOCUMENTS TO
BE GENERATED		 TIDP_n Task Team n's Task Information Delivery Plan
LEAD APPOINTED PARTY  
5.4.5 Establish the master information delivery plan  
SUB-ACT/ITEMS
TO CONSIDER		 5.4.5.a.1 consider: the assigned responsibilities within the detailed responsibility matrix  
5.4.5.a.2 consider: the information predecessors or dependencies on information between task teams  
5.4.5.a.3 consider: the time the lead appointed party will need to review and authorize the information model  
5.4.5.a.4 consider: the time the appointing party will need to review and accept the information model  
5.4.5.b.1 Once the MIDP has been established, the lead appointed party shall:
baseline the deliverables and dates within the MIDP
  
5.4.5.b.2 Once the MIDP has been established, the lead appointed party shall:
inform each task team and notify if any changes are required to the TIDP
  
5.4.5.b.3 Once the MIDP has been established, the lead appointed party shall:inform the appointing party of any risks or issues which could impact on the project’s information delivery milestones

  
DOCUMENTS
TO BE REFERRED		 DRM_1 Delivery team’s detailed responsibility matrix  
CDE_2 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Req.&COL-PP)   
PMP_2 Project's Information Production Methods and Procedures  
TIDP_1…n Task Information Delivery Plans  
DOCUMENTS TO
BE GENERATED		 MIDP_0 Master information delivery plan  
APPOINTING PARTY  
5.4.6 Complete lead appointed party’s appointment documents  
SUB-ACT/ITEMS
TO CONSIDER		 5.4.6.a the appointing party’s exchange information requirements  
5.4.6.b the project’s information standard (including any agreed additions or amendments)  
5.4.6.c the project information protocol (including any agreed additions or amendments)  
5.4.6.d the delivery team’s BIM Execution plan  
5.4.6.e the delivery team’s MIDP  
DOCUMENTS
TO BE REFERRED		 EIR_APOP Exchange Information Requirements (Appointing Party's)  
INS_2 Project's Information Standard  
INP_1 Project's Information Protocol  
BEP_0 Delivery Team's Post Appointment BEP   
MIDP_0 Master information delivery plan  
DOCUMENTS TO
BE GENERATED		 L-APD Lead appointed party’s appointment documents  
LEAD APPOINTED PARTY  
5.4.7 Complete appointed party’s appointment documents  
SUB-ACT/ITEMS
TO CONSIDER		 5.4.7.a the lead appointed party’s exchange information requirements;  
5.4.7.b the project’s information standard (including any agreed additions or amendments)  
5.4.7.c the project’s information protocol (including any agreed additions or amendments)  
5.4.7.d the delivery team’s BIM Execution plan  
5.4.7.e the agreed TIDP.  
DOCUMENTS
TO BE REFERRED		 EIR-LEAP lead appointed party’s exchange information requirements  
INS_2 Project's Information Standard  
INP_1 Project's Information Protocol  
BEP_0 Delivery Team's Post Appointment BEP (Including all BEP annexes attached to BEP such as MIDP)  
TIDP_1…n Task Information Delivery Plans  
        DOCUMENTS TO
BE GENERATED		 A-APD Appointed party’s appointment documents  
 
LEAD APPOINTED PARTY   LEAD APPOINTED PARTY
5.5.1 Mobilize resources 5.5.2 Mobilize information technology
SUB-ACT/ITEMS
TO CONSIDER		 5.5.1.a confirm the resource availability of each task team SUB-ACT/ITEMS
TO CONSIDER		 5.5.2.a procure, implement, configure and test software, hardware and IT infrastructure (as required);
5.5.1.b develop  and  deliver  education  on  topics  such  as  the  project’s  scope,  exchange  information requirements and delivery milestones (knowledge required) to delivery team members 5.5.2.b configure and test the project’s CDE in accordance with 5.1.7
5.5.2.c configure and test the delivery team’s (distributed) CDE and its connectivity to the project CDE (if applicable) in accordance with 5.1.7
5.5.2.d test the information exchanges between task teams
5.5.1.c develop and deliver training (skills required) to the delivery
team members		 5.5.2.e test the information delivery to the appointing party
DOCUMENTS
TO BE REFERRED		 MOB_1 Delivery Team's Mobilization Plan DOCUMENTS
TO BE REFERRED		 MOB_1 Delivery Team's Mobilization Plan
TRA_1 Training Requirements (Ref.to. 5.5.1) INS_2 Project's Information Standard
PMP_2 Project's Information Production Methods and Procedures
DTCC_1 Delivery team’s capability and capacity assessment SCH-IT_1 Schedule of Software, Hardware & IT
CDE_2 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) 
DOCUMENTS TO
BE GENERATED		 MORE Mobilization of resources report DOCUMENTS TO
BE GENERATED		 CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) 
INS_3 Project's Information Standard
MOIR Mobilization of information technology report
LEAD APPOINTED PARTY  
5.5.3 Test the project’s information production methods and procedures  
SUB-ACT/ITEMS
TO CONSIDER		 5.5.3.a test and document the project’s information production methods and procedures;  
5.5.3.b refine and verify the proposed information container breakdown structure
is workable		  
5.5.3.c develop shared resources to be used by the delivery team  
5.5.3.d communicate the project’s information production methods and procedures to all
tasks teams		  
DOCUMENTS
TO BE REFERRED		 LIB_2 Library Guide & Library Structure in Data Environment  
SHR_2 Shared Resources Guide & Shared Resources in CDE  
RES_2 Project’s reference information and shared resources   
FSB_1 Federation Strategy & Information Container Breakdown Structure  
PMP_2 Project's Information Production Methods and Procedures  
DOCUMENTS TO  BE GENERATED  LIB_3 Library Guide & Library Structure in Data Environment  
SHR_3 Shared Resources Guide & Shared Resources in CDE  
RES_3 Project’s reference information and shared resources   
FSB_2 Federation Strategy & Information Container Breakdown Structure  
PMP_RR Project's Information Production Methods and Procedures Test Report  
      PMP_3 Project's Information Production Methods and Procedures    
 
TASK TEAM-1   TASK TEAM-2   TASK TEAM-n
5.6.1 Check availability of reference information and shared resources 5.6.1 Check availability of reference information and shared resources 5.6.1 Check availability of reference information and shared resources
SUB-ACT/ITEMS
TO CONSIDER		 5.6.1.a Prior to generating information, each task team shall check that they have access to the relevant reference information and shared resources within the project’s CDE. If not, they shall, as soon as practicable, inform the lead appointed party
and assess the potential impact that this could have on the TIDP		 SUB-ACT/ITEMS
TO CONSIDER		 5.6.1.a Prior to generating information, each task team shall check that they have access to the relevant reference information and shared resources within the project’s CDE. If not, they shall, as soon as practicable, inform the lead appointed party
and assess the potential impact that this could have on the TIDP		 SUB-ACT/ITEMS
TO CONSIDER		 5.6.1.a Prior to generating information, each task team shall check that they have access to the relevant reference information and shared resources within the project’s CDE. If not, they shall, as soon as practicable, inform the lead appointed party
and assess the potential impact that this could have on the TIDP
DOCUMENTS
TO BE REFERRED		 CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP)  DOCUMENTS
TO BE REFERRED		 CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP)  DOCUMENTS
TO BE REFERRED		 CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) 
LIB_3 Library Guide & Library Structure in Data Environment LIB_3 Library Guide & Library Structure in Data Environment LIB_3 Library Guide & Library Structure in Data Environment
SHR_3 Shared Resources Guide & Shared Resources in CDE SHR_3 Shared Resources Guide & Shared Resources in CDE SHR_3 Shared Resources Guide & Shared Resources in CDE
RES_3 Project’s reference information and shared resources  RES_3 Project’s reference information and shared resources  RES_3 Project’s reference information and shared resources 
DOCUMENTS TO
BE GENERATED		 CR-TT-1 Task Team's Access Check Report DOCUMENTS TO
BE GENERATED		 CR-TT-2 Task Team's Access Check Report DOCUMENTS TO
BE GENERATED		 CR-TT-n Task Team's Access Check Report
TASK TEAM-1 TASK TEAM-2 TASK TEAM-n
5.6.2 Generate information 5.6.2 Generate information 5.6.2 Generate information
SUB-ACT/ITEMS
TO CONSIDER		 5.6.2.a.1 generate information: in compliance with the project’s information standard SUB-ACT/ITEMS
TO CONSIDER		 5.6.2.a.1 generate information: in compliance with the project’s information standard SUB-ACT/ITEMS
TO CONSIDER		 5.6.2.a.1 generate information: in compliance with the project’s information standard
5.6.2.a.2 generate information: in accordance with the project’s information production methods and procedures 5.6.2.a.2 generate information: in accordance with the project’s information production methods and procedures 5.6.2.a.2 generate information: in accordance with the project’s information production methods and procedures
5.6.2.b.1 not generate information that: exceeds the required level of information need 5.6.2.b.1 not generate information that: exceeds the required level of information need 5.6.2.b.1 not generate information that: exceeds the required level of information need
5.6.2.b.2 not generate information that: extends beyond the allocated
element of the information container breakdown structure		 5.6.2.b.2 not generate information that: extends beyond the allocated
element of the information container breakdown structure		 5.6.2.b.2 not generate information that: extends beyond the allocated
element of the information container breakdown structure
5.6.2.b.3 not generate information that: duplicates information generated by other task teams 5.6.2.b.3 not generate information that: duplicates information generated by other task teams 5.6.2.b.3 not generate information that: duplicates information generated by other task teams
5.6.2.b.4 not generate information that: contains superfluous detail 5.6.2.b.4 not generate information that: contains superfluous detail 5.6.2.b.4 not generate information that: contains superfluous detail
5.6.2.c coordinate and cross-referenced all information with information shared within the project’s common data environment, in accordance with the project’s information production methods and procedures 5.6.2.c coordinate and cross-referenced all information with information shared within the project’s common data environment, in accordance with the project’s information production methods and procedures 5.6.2.c coordinate and cross-referenced all information with information shared within the project’s common data environment, in accordance with the project’s information production methods and procedures
5.6.2.d spatially coordinate geometrical models with other geometrical models shared with the appropriate suitability, residing within the project’s CDE 5.6.2.d spatially coordinate geometrical models with other geometrical models shared with the appropriate suitability, residing within the project’s CDE 5.6.2.d spatially coordinate geometrical models with other geometrical models shared with the appropriate suitability, residing within the project’s CDE
DOCUMENTS
TO BE REFERRED		 PMP_3 Project's Information Production Methods and Procedures DOCUMENTS
TO BE REFERRED		 PMP_3 Project's Information Production Methods and Procedures DOCUMENTS
TO BE REFERRED		 PMP_3 Project's Information Production Methods and Procedures
INS_3 Project's Information Standard INS_3 Project's Information Standard INS_3 Project's Information Standard
LOIN_2 Level of Information Need Manual LOIN_2 Level of Information Need Manual LOIN_2 Level of Information Need Manual
FSB_1 Federation Strategy & Information Container Breakdown Structure FSB_1 Federation Strategy & Information Container Breakdown Structure FSB_1 Federation Strategy & Information Container Breakdown Structure
SCO_2 Spatial Coordination (Coordinates) Methods & Procedures SCO_2 Spatial Coordination (Coordinates) Methods & Procedures SCO_2 Spatial Coordination (Coordinates) Methods & Procedures
CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP)
DOCUMENTS TO
BE GENERATED		 * Each Task Team's Information Genaration Process DOCUMENTS TO
BE GENERATED		 * Each Task Team's Information Genaration Process DOCUMENTS TO
BE GENERATED		 * Each Task Team's Information Genaration Process
TASK TEAM-1 TASK TEAM-2 TASK TEAM-n
5.6.3 Undertake quality assurance check 5.6.3 Undertake quality assurance check 5.6.3 Undertake quality assurance check
SUB-ACT/ITEMS
TO CONSIDER		 5.6.3.a.1 if the check is successful: mark the information container
as checked		 SUB-ACT/ITEMS
TO CONSIDER		 5.6.3.a.1 if the check is successful: mark the information container
as checked		 SUB-ACT/ITEMS
TO CONSIDER		 5.6.3.a.1 if the check is successful: mark the information container
as checked
5.6.3.a.2 if the check is successful: record the outcome of the check 5.6.3.a.2 if the check is successful: record the outcome of the check 5.6.3.a.2 if the check is successful: record the outcome of the check
5.6.3.b.1 if the check is unsuccessful: reject the information container 5.6.3.b.1 if the check is unsuccessful: reject the information container 5.6.3.b.1 if the check is unsuccessful: reject the information container
5.6.3.b.2 if the check is unsuccessful:inform the information author of the
outcome and corrective action required		 5.6.3.b.2 if the check is unsuccessful:inform the information author of the
outcome and corrective action required		 5.6.3.b.2 if the check is unsuccessful:inform the information author of the
outcome and corrective action required
DOCUMENTS
TO BE REFERRED		 QUA_3 Quality Assurance Manual  DOCUMENTS
TO BE REFERRED		 QUA_3 Quality Assurance Manual  DOCUMENTS
TO BE REFERRED		 QUA_3 Quality Assurance Manual 
CCI_3 Coordination Clash Detection & Issue Management Manual CCI_3 Coordination Clash Detection & Issue Management Manual CCI_3 Coordination Clash Detection & Issue Management Manual
PMP_3 Project's Information Production Methods and Procedures PMP_3 Project's Information Production Methods and Procedures PMP_3 Project's Information Production Methods and Procedures
INS_3 Project's Information Standard INS_3 Project's Information Standard INS_3 Project's Information Standard
DOCUMENTS TO
BE GENERATED		 QUA-TT-1 Task Team's Quality Assurance Check Report DOCUMENTS TO
BE GENERATED		 QUA-TT-2 Task Team's Quality Assurance Check Report DOCUMENTS TO
BE GENERATED		 QUA-TT-N Task Team's Quality Assurance Check Report
TASK TEAM-1 TASK TEAM-2 TASK TEAM-n
5.6.4 Review information and approve for sharing 5.6.4 Review information and approve for sharing 5.6.4 Review information and approve for sharing
SUB-ACT/ITEMS
TO CONSIDER		 5.6.4.a.1 In doing this, the task team shall consider:
the lead appointed party’s information requirements		 SUB-ACT/ITEMS
TO CONSIDER		 5.6.4.a.1 In doing this, the task team shall consider:
the lead appointed party’s information requirements		 SUB-ACT/ITEMS
TO CONSIDER		 5.6.4.a.1 In doing this, the task team shall consider:
the lead appointed party’s information requirements
5.6.4.a.2 In doing this, the task team shall consider:
the level of information need		 5.6.4.a.2 In doing this, the task team shall consider:
the level of information need		 5.6.4.a.2 In doing this, the task team shall consider:
the level of information need
5.6.4.a.3 In doing this, the task team shall consider:
information needed for coordination by other task teams.		 5.6.4.a.3 In doing this, the task team shall consider:
information needed for coordination by other task teams.		 5.6.4.a.3 In doing this, the task team shall consider:
information needed for coordination by other task teams.
5.6.4.b.1 Once the review is complete, the task team shall:if the review is
successful: assign the suitability for which the information contained within the information container can be used		 5.6.4.b.1 Once the review is complete, the task team shall:if the review is
successful: assign the suitability for which the information contained within the information container can be used		 5.6.4.b.1 Once the review is complete, the task team shall:if the review is
successful: assign the suitability for which the information contained within the information container can be used
5.6.4.b.2 Once the review is complete, the task team shall:if the review is
successful: approve the information container for sharing		 5.6.4.b.2 Once the review is complete, the task team shall:if the review is
successful: approve the information container for sharing		 5.6.4.b.2 Once the review is complete, the task team shall:if the review is
successful: approve the information container for sharing
5.6.4.c.1 Once the review is complete, the task team shall:if the review is unsuccessful: record why the review was unsuccessful 5.6.4.c.1 Once the review is complete, the task team shall:if the review is unsuccessful: record why the review was unsuccessful 5.6.4.c.1 Once the review is complete, the task team shall:if the review is unsuccessful: record why the review was unsuccessful
5.6.4.c.2 Once the review is complete, the task team shall:if the review is unsuccessful: record any amendments for the task team to complete 5.6.4.c.2 Once the review is complete, the task team shall:if the review is unsuccessful: record any amendments for the task team to complete 5.6.4.c.2 Once the review is complete, the task team shall:if the review is unsuccessful: record any amendments for the task team to complete
5.6.4.c.3 Once the review is complete, the task team shall:if the review is unsuccessful: reject the information container 5.6.4.c.3 Once the review is complete, the task team shall:if the review is unsuccessful: reject the information container 5.6.4.c.3 Once the review is complete, the task team shall:if the review is unsuccessful: reject the information container
DOCUMENTS
TO BE REFERRED		 PMP_3 Project's Information Production Methods and Procedures DOCUMENTS
TO BE REFERRED		 PMP_3 Project's Information Production Methods and Procedures DOCUMENTS
TO BE REFERRED		 PMP_3 Project's Information Production Methods and Procedures
EIR-LEAP Lead Appointed Party's Exchange Information Requirements EIR-LEAP Lead Appointed Party's Exchange Information Requirements EIR-LEAP Lead Appointed Party's Exchange Information Requirements
LOIN_2 Level of Information Need Manual LOIN_2 Level of Information Need Manual LOIN_2 Level of Information Need Manual
DOCUMENTS TO
BE GENERATED		 IRR-TT-1 Task Team's Information Review (by Task Team) Report DOCUMENTS TO
BE GENERATED		 IRR-TT-2 Task Team's Information Review (by Task Team)  Report DOCUMENTS TO
BE GENERATED		 IRR-TT-N Task Team's Information Review (by Task Team)  Report
 
  DELIVERY TEAM  
  5.6.5 Information model review  
  SUB-ACT/ITEMS
TO CONSIDER		 5.6.5.a the appointing party’s information requirements and acceptance criteria  
  5.6.5.b the containers listed within the master information delivery plan  
  DOCUMENTS
TO BE REFERRED		 ACR_1 Acceptance Criteria Manual  
  EIR-APOP Appointing Party's EIR  
  MIDP_0 Master Information Delivery Plan  
  PMP_3 Project's Information Production Methods and Procedures  
      DOCUMENTS TO
BE GENERATED		 IMR-DT Delivery Team's Information Model Review Report      
 
TASK TEAM-1   TASK TEAM-2   TASK TEAM-n
5.7.1 Submit information model for lead appointed party authorization 5.7.1 Submit information model for lead appointed party authorization 5.7.1 Submit information model for lead appointed party authorization
DOCUMENTS TO
BE GENERATED		 APP-711 Submittal List DOCUMENTS TO
BE GENERATED		 APP-712 Submittal List DOCUMENTS TO
BE GENERATED		 APP-71n Submittal List
 
 
  LEAP (Lead Appointed Party)  
  5.7.2 Review and authorize the information model  
  SUB-ACT/ITEMS
TO CONSIDER		 5.7.2.a the deliverables listed in the master information delivery plan  
  5.7.2.b the appointing party’s exchange information requirements  
  5.7.2.c the lead appointed party’s exchange information requirements  
  5.7.2.d the acceptance criteria for each information requirement  
  5.7.2.e the level of information need for each information requirement  
  DOCUMENTS
TO BE REFERRED		 PMP_3 Project’s Information Production Methods and Procedures  
  MIDP_0 MIDP  
  EIR_APOP Appointing Party's EIR  
  EIR_LEAP Lead Appointed Party's EIR  
  ACR_1 Acceptance Criteria Manual  
  LOIN_2 Level of Information Need Manual  
  LOA_1 Level of Accuracy Table  
  DOCUMENTS TO
BE GENERATED		 TTS-RR Task Teams' Submittals & PIM Review Report by Leap  
 
TASK TEAM-1 TASK TEAM-2 TASK TEAM-n
5.7.3 Submit information model for appointing party acceptance 5.7.3 Submit information model for appointing party acceptance 5.7.3 Submit information model for appointing party acceptance
DOCUMENTS TO
BE GENERATED		 APP-731 Submittal List DOCUMENTS TO
BE GENERATED		 APP-732 Submittal List DOCUMENTS TO
BE GENERATED		 APP-73n Submittal List
 
  APPOINTING PARTY  
  5.7.4 Review and accept the information model  
  SUB-ACT/ITEMS
TO CONSIDER		 5.7.4.a the deliverables listed in the master information delivery plan  
  5.7.4.b the appointing party’s exchange information requirements  
  5.7.4.c the acceptance criteria for each information requirement  
  5.7.4.d the level of information need for each information requirement  
  DOCUMENTS
TO BE REFERRED		 PMP_3 Project’s Information Production Methods and Procedures  
  MIDP_0 MIDP  
  EIR_APOP Appointing Party's EIR  
  ACR_1 Acceptance Criteria Manual  
  LOIN_2 Level of Information Need Manual  
  LOA_1 Level of Accuracy Table  
      DOCUMENTS TO
BE GENERATED		 PIM-RR Apop's PIM Review Report        
  APPOINTING PARTY   APPOINTING PARTY
5.8.1 Archive the project information model 5.8.2 Capture lessons learned for future projects
SUB-ACT/ITEMS
TO CONSIDER		 5.8.1.a which information containers will be needed as part of the asset information model SUB-ACT/ITEMS
TO CONSIDER		 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
5.8.1.b future access requirements
5.8.1.c future re-use
5.8.1.d relevant retention policies to be applied DOCUMENTS
TO BE REFERRED		 CLL Capture lessons learned
(To be used by LEAP and APP's starting from the tender response stage)
DOCUMENTS
TO BE REFERRED		 PMP_3 Project’s Information Production Methods and Procedures
CDE_3 Project's CDE Structure, Standards, Methods, Procedures (Incl. Security Requirements and COL-PP) 
DOCUMENTS TO
BE GENERATED		 PAR PIM to AIM Requirements DOCUMENTS TO
BE GENERATED		 RLL Lessons learned record(APOP will establish the RLL from CLLs)
DP-ARC DATA DROP_Archive of CDE and PIM (Delivery Phase)