A DESIGN MANAGEMENT DOCUMENT
PDG
©
D03
PROJECT
www.projectdesignguides.com
D03
DESIGN
GUIDES
PROJECT DESIGN GUIDE D03
‘DESIGN INFORMATION FLOW
MAPPING’
Project Name:
Project No.:
Date:
Name
Number
Date
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
1 of 10
A DESIGN MANAGEMENT DOCUMENT
Document No.: PDG-PDG-PRO-D03.0
D03
Date Created: 8th June 2012
www.projectdesignguides.com
Date Revised: R01 06.06.2014
Revision:
Revision description:
Revision date:
01
Guide list omitted, graphics updated, alpha codes updated.
6 June 2014
02
03
Edited to be project specific / Revised by:
Name:
Position:
Signature:
Date:
Checked by:
Name:
Position:
Signature:
Date:
Authorised by:
Name:
Position:
Signature:
Date:
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
2 of 10
A DESIGN MANAGEMENT DOCUMENT
D03
www.projectdesignguides.com
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
3 of 10
A DESIGN MANAGEMENT DOCUMENT
D03
www.projectdesignguides.com
Document Distribution:
Name
Company
Status
A
Date
00/00/2012
Status key:
A – Action
I – Information
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
4 of 10
A DESIGN MANAGEMENT DOCUMENT
1.0
D03
www.projectdesignguides.com
Introduction
There are several important flows of design information that, for clarity, benefit from being illustrated. It is
important to check the main contract documents for explicit time scales and inclusion of client processes.
Creating flow charts of the project design process highlights the complexity of service required to manage the
project design, an important factor, in addition to complexity of the design intself, when bidding for a project
and when managing fees / resources.
The following are examples only, and may need to be redrawn to be project specific. They form a hierarchy,
from overall project process to drilling down into the detail of individual actions.
Flow
Flow
Flow
Flow
Flow
charts included:
Chart 1: Project Process Map for Design.
Chart 2: Design Team Drawing Life Cycle.
Chart 3: Design Team Information Approval Process Iteration Diagram.
Chart 4: Approval process (Consultants and sub-contractors).
Flow Chart 1: Project Process Map for Design: illustrates the complexity of service, inter-relationships, and
highlights busy stages.
Flow Chart 2: Design Team Drawing Life Cycle: maps out the journey for any particular piece of design
information. Importantly informs on approval process/es, which stage/s they need to happen and if there is a
client approval process.
Flow Chart 3: Design Information Approval Process Iteration Diagram: gives clear guidance on the likely
length of parallel and sequential approval processes, with a realistic second iteration incorporated. The Project
Planner should include this as float when programming.
Flow Chart 4: Approval process (Consultants and sub-contractors): drills down to individuals, indicating
responsibilities, tasks and timescales, as well as the flow between parties.
Note: these flow charts do not relate to BIM.
These flow charts create a quick easy tool for briefing other team members and are particularly important for
informing Project Planning, on the inter-relationships, time scales and float required in the detail of the
processes.
1.0
Decisions
With every process map there are decisions to be made. The following are possible items to consider. Amend
as required:
 If there is a Client process how does this effect / dictate the information flow.
 Understand the processes (i.e. BREEAM points are gained from the early stages).
 What stages do drawings need approval for:
o Every stage issue,
o Tender & Construction,
o Construction only.
 What approval time scales are allowed for, for each party.
 Is the Contractors Design Manager the lead reviewer?
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
5 of 10
A DESIGN MANAGEMENT DOCUMENT
Stage
D03
To be Approved by the
Contractor
www.projectdesignguides.com
To be Approved by the Client
Prelim
NO
NO
LA Planning
YES
YES
Tender
YES
NO
Construction
YES
YES
Record information
YES
YES
Table 1.0 Stages to be approved (amend as required)
2.0
Managing this Document
Once set up this document should not need amending. Care should be taken to ensure this document is right
first time. To change flow charts part way through the design process will cause great confusion.
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
6 of 10
A DESIGN MANAGEMENT DOCUMENT
Flow Chart 1:
D03
www.projectdesignguides.com
Project Process Map for Design
Amend to be project specific
CLIENT PROCESSES
CONTRACTOR PROCESSES
CLIENT / TENANT
Line of contract depends on procurement route
Stage 1
Stage 2
Approval
Stage 3
Approval
Stage 4 Coordination
CP’s
Tender Info
Planning
Submission
Construction
Info
CDP co-ord
check
Planning Conditions
CDM process
H&S File
C
O
N
S
T
R
U
C
T
I
O
N
Building Control process
DfMA/MMC
input
DfMA/MMC
Design
DfMA/MMC
Manufacture
DfMA/MMC
Assembly
Quality Conformance process
BREEAM / Code process
Secure by Design process
Clients Agents process
RDD process
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
7 of 10
Building in use
A DESIGN MANAGEMENT DOCUMENT
Flow Chart 2:
D03
www.projectdesignguides.com
Design Team Drawing Life Cycle RIBA stage 3 onwards
Action by: Document Controller / Approval Status: QA checked / Time: 2 working days
Amend as appropriate
STAGE D SIGN OFF
LA Planning Application
STAGE 3
Action by: Originator issue
Status: Preliminary
Reason: For Coordination
STAGE 3
Action by: DT Comment & Building Control
Status: Preliminary
Reason: For Coordination & Statutory conformance
STAGE 4
Action by: Originator issue
Status: For Tender
Reason: For Pricing
STAGE 4
Review Cost &
Programme
implications
Refer to Flow
Chart 3
STAGE 4
Action by: Originator issue
Status: For Construction Approval
Reason: For Approval (A/B/C)
STAGE 4
Action by: Lead
Designer
Status: For
Construction
Approval
Reason: For
Lead Design
Approval
Approval
Status: A/B/C
Time: 5 days
Rejected
STAGE 4
Action by:
Design
Manager
Status: For
Construction
Approval
Reason: For
Contractor
Approval
Approval
Status: A/B/C
Time: 14 days
(7 days
additional to
DT)
STAGE 4
Action by:
Client [TBC]
Status: For
Construction
Approval
Reason: For
Client Approval
Time: 14 days
Approved
STAGE 5
Action by: Originator
Status: For Construction
Reason: For Action
Approval Status: A
STAGE 5
Site works
STAGE 5 – Building Control
Action by: Originator
Status: For Construction
Reason: For Building Control Approval
Approval Status: Yes / No
Rejected
STAGE 5
Review Cost &
Programme
implications
Approved
STAGE 6
Action by: Originator
Status: As Built Record Drawing
Reason: For O&M’s / H&S file
DC to ‘sense’ check issue to O&M provider.
Project name: / No.
Document Version: V01 – June 2012
© Philip D G Yorke 2012
8 of 10
A DESIGN MANAGEMENT DOCUMENT
Flow Chart 3:
D08
Project Design Guides Ltd
DRAFT
Design Information Approval Process Iteration Diagram
Contractor and Client parallel process
wk 1
wk 2
Refer to Flow Chart
4
FCA
DT 1
DT 2
CT 1
CT 2
Approvals
wk 3
A
FC
B
Letter ?
C
FCA
wk 4
wk 5
DT 1
DT 2
CT 1
CT 2
Approvals
wk 6
A
FC
B
Letter ?
FCA
C
Contractor and Client Sequential process
wk 1
wk 2
Approvals
A
FCA
DT 1
DT 2
wk 3
CT 1
wk 4
wk 5
Approvals
wk 5
A
FC
B
Letter ?
CT 2
FCA
C
FCA
A
DT 1
DT 2
Key:
DT 1
Design Team approval week/s
CT 1
Client Team approval week/s
FC
For Construction
Note: Time scales for the Parallel process above are the same with or without client involvement.
Project name: / No.
Last edited on: 2 May 2012
CT 1
B
C
For Construction Approval
wk 7
B
C
FCA
wk 6
9 of 10
FCA
CT 2
Approvals
wk 8
A
FC
B
Letter ?
C
FCA
A DESIGN MANAGEMENT DOCUMENT
Flow Chart 4:
D08
Project Design Guides Ltd
DRAFT
Approval process (Consultants and sub-contractors)
(without client approval process) – amend as appropriate
ORIGINATOR
DOCUMENT
CONTROLLER
DESIGN TEAM
LEAD REVIEWER
Step 3 Design Team to markup documents and
create comments
incorporation mark-ups
if required. Lead
Designer to have final
say and return
comments.
Step 4 Lead Reviewer to make
any final comments.
Step 1
Drawings: PDF + ZIP
(DWG or DWF or ?)
Revision: P01
Design Team uploads
documents (update to
reflect previous
comments if revision).
Purpose of issue: For
(Tender /
Construction)
Approval
All documents must be
issued to the document
controller ‘For
Distribution’ to initiate
the workflow.
Return to originator or
amendment
Doc OK?
NO
Step 2b
Comment
on
document to
state the
document
does not
conform to
QA
standards
Status:
QA reject
YES
Step 2a
Comment
Documents
to be
distributed to
design team
and trade
contractor
for comment
as
appropriate
Step 5 Design Team to markup documents and
create comments
incorporation mark-ups
if required. Lead
Designer to have final
say and return
comments.
Step 6
Receive comments
and/or make counter
comments
Status: A
or
Status: B
Step 7 Drawing issue
Design Team uploads
document incorporation
comments as required.
Revision: T01 / C01
Purpose of issue: For
Tender /
Construction
Step 8
Issue to Document
Controller ‘For
Distribution’.
2 WORKING DAYS
5 WORKING DAYS
3 WORKING DAYS
Project name: / No.
Last edited on: 2 May 2012
10 of 10