Appendix 3 - Master Information Delivery Plan (MIDP) Template
Appendix 3 - Master Information Delivery Plan (MIDP) Template
Project Number
Project Title
Author Example file name
Date Created
Date Last Updated
Document Reference OWNER INSERT NAME OF OWNER
Refer to file naming convention doc for info INFORMATION EXCHANGE #01 INFORMATION EXCHANGE #02 INFORMATION EXCHANGE #03 INFORMATION EXCHANGE #04 INFORMATION EXCHANGE #05 INFORMATION EXCHANGE #06 INFORMATION EXCHANGE
OPERATION #07
IN Client
OPTIONAL STAGE: BRIEF STAGE: CONCEPT STAGE: DEFINITION STAGE: DESIGN STAGE: BUILD AND COMMISSION STAGE: HANDOVER AND CLOSE OUT STAGE: USE Client adviser
FILE NAME
PROGRAMME REF: PROGRAMME REF: PROGRAMME REF: PROGRAMME REF: PROGRAMME REF: PROGRAMME REF: PROGRAMME REF: Project lead
PROJECT ORIGINATO VOLUME / LEVEL/ TYPE ROLE NUMBER CLASSIFICATION (UNICLASS NRM1 DATE REQUIRED TO DATE REQUIRED TO DATE REQUIRED TO DATE REQUIRED DATE REQUIRED TO DATE REQUIRED Lead designer
DELIVERABLE (TITLE) DESCRIPTION EXCHANGE FORMATS CODE R CODE SYSTEM* LOCATIO OWNER OWNER OWNER OWNER OWNER OWNER DATE REQUIRED TO ISSUE OWNER
2015) CODE ISSUE ISSUE ISSUE TO ISSUE ISSUE TO ISSUE Construction lead
N
MODELS Architect
Civil and structural engineer
Building services engineer
Cost consultant
Contract administrator
Health and safety advisor
Access consultant
Acoustic consultant
Archaeologist
BREEAM assessor
Cladding specialist
Catering consultant
Facilities management (FM) advisor
Fire engineer
Highways consultant
DRAWINGS (CUT FROM MODEL) Information manager
Interior designer
Landscape architect
Lighting designer
Masterplanner
Operational lead
Party wall surveyor
Planning consultants
Security advisor
Signage designer
Sustainability advisor
Technical advisor
Other additional project role 1
Other additional project role 2
REPORTS
SPECIFICATIONS
OTHER
* When planning complex projects and determining the number of model files required, it is commonplace and good practice for
the project to be divided into volumes defined by coordinates within an overall project model that will be held as separate model
files. This enables multiple users to work on the project efficiently. Volumes should be allocated using cut lines to indicate their
limits. Volume boundaries could be structural joints or grid lines; for road projects they could be chainage distances; or they could
be defined by use e.g. a vertical distribution shaft.