Assembling a Collaborative Project Team

Practical tools including Multidisciplinary Schedules of Services

Dale Sinclair

• Verlag: RIBA Publishing
• Jahr: 2019
• ISBN:
  9781000704969
• Auflage: 1
• Thema: Architecture
• Thema: Architecture General

Contemporary construction practice presents a shift in emphasis from thinking about the design team in isolation, to considering the project team as a collaborative whole: client, design team, and contractor.

This approach requires greater consideration of how the project team is procured and assembled – and Assembling a Collaborative Project Team provides a range of in-depth and invaluable methods for ensuring that this essential task is carried out effectively. It will bring a range of benefits to any project – from facilitating BIM-ready teams, to better construction programming, and reducing risk through ensuring a watertight contractual framework. Many of the methods presented here are likely to become ingrained in the way all projects are coordinated.

It shows that the best way of assembling a collaborative team is by establishing the team at the outset in manner that ensures that each party is fully aware of what they need to do and when, and by agreeing how this will be achieved.

Chapter 1
The importance of Stages 0 and 1

What is the aim of Stages 0 and 1?

Why a robust Initial Project Brief is crucial

What are the benefits of assembling the collaborative project team prior to Stage 2?

What is the relationship between the brief and the collaborative project team?

Chapter overview

Stage 2 is the most crucial stage of any project: the Concept Design is prepared, presented and signed off by the client. Robust Stage 2 outputs are an essential requirement of any project because any changes after Stage 2 can be difficult and costly to implement (as illustrated in Figure 1.1 below). Ensuring that Stage 2, and in particular the assembly of the project team, is undertaken as productively and effectively as possible is therefore a core project requirement. This chapter considers how the successful implementation of Stages 0 and 1 is central to achieving this aim.

Some would advocate the commencement of Stage 2 immediately. Why wait? What purpose do the earlier stages serve? Let’s design! Let’s get on site as soon as possible! With this in mind, this chapter dwells on the importance of Stages 0 and 1 and the crucial purpose that they serve. The Guide to Using the RIBA Plan of Work 2013 also sets out how the requirements of Stages 6 and 7 can influence the earlier stages and these stages must also be considered before design work can commence.

If the best possible start to Stage 2 is to be achieved, some of the initial hurdles to assembling the collaborative project team need to be thought through. These are considered in Chapter 4. This chapter focuses on the importance and aims of Stages 0 and 1 and how their efficient use can facilitate a more effective and productive Stage 2.

The implication of change

Beyond Stage 2, the amount of information produced increases exponentially. The more information that is produced, the greater the amount of information that has to be amended in the event of a change. Significant changes proposed at Stage 3 might require the work of all of the design team to be altered and further reviews and coordination exercises to be undertaken, making these changes costly and difficult to implement.

Figure 1.1 The cost of change

At Stage 4 further, and significant, design team costs will be incurred, as will the costs of design work carried out by the contractor’s specialist subcontractors. When a project reaches site, at Stage 5, the cost of change ramps up even further as change impacts on the ordering of materials, off-site fabrication costs and, in the most onerous of scenarios, the need to alter work already constructed on site.

The impact of change: an example

By way of example, the following considers the implication of introducing an additional escalator into the ground floor of a shopping centre at different RIBA stages.

Stage 2 – Concept Design

The architect’s information needs to be amended to include the escalator and the Cost Information has to be adjusted accordingly.

Stage 3 – Developed Design

The change is instructed via the project Change Control Procedures after a number of studies have been undertaken and the architect’s information is amended followed by the structural and building services engineers’ information. The Cost Information is also adjusted accordingly.

Stage 4 – Technical Design

Process as Stage 3; however, the architect must also alter the ground floor finishes and ceiling information and the balustrading setting out for level 1. The structural engineer must amend the substructure information as well as the detailed steelwork and slab information for level 1, and the building services engineer has to alter the electrical schematics and light fitting layout information on receipt of amended ceiling information from the architect. Depending on the timing, the specialist subcontractor providing the escalators would have to amend their information to show the additional escalator, the steelwork contractor would have to alter the secondary steelwork information and the contractor would have to consider any logistics issues arising from the changes. The lead designer would also be required to undertake additional coordination and integration exercises.

Stage 5 – Construction

Process as Stage 4; however, work already undertaken on site must be considered. Adjustment of the cast ground floor slab is required, secondary steelwork has not yet been delivered to site but requires modification and the ground floor tiling works have to be reprogrammed and the critical path reviewed.

Summary

This example demonstrates the additional work triggered by change and underlines the increased complexity at each stage. The cost of change will directly relate to the amount of activity undertaken, significantly increasing when fabricated or completed works on site have to be altered.

What is the aim of Stages 0 and 1?

In the extract from the RIBA Plan of Work 2013 in Figure 1.2 below, the Core Objectives and Suggested Key Support Tasks of Stages 0 and 1 are set out. The rationale behind having two stages prior to the commencement of the Concept Design stage is straightforward: Stage 0 considers strategic issues and Stage 1 adds ‘flesh’ to these strategic bones. The outputs at the end of a successful Stage 1 would be:

• a robust Initial Project Brief, and
• a collaborative project team.

These two outputs and the connection between them are considered in detail below.

Figure 1.2 Extract from the RIBA Plan of Work 2013

Why a robust Initial Project Brief is crucial

Without a robust brief, the Concept Design stage cannot begin productively and, more crucially, may be taken in a direction that is not suited or aligned to a client’s goals and objectives. It is fair to say that the brief needs to be developed in tandem with the developing Concept Design before it is finalised at the end of Stage 2, along with the Concept Design, but it is also essential to acknowledge that the brief and any associated Feasibility Studies should be sufficiently developed during Stage 1 to facilitate an effective start to Stage 2.

Stage 0

At Stage 0, the aim of the brief is to consider the client’s Business Case and the strategic aspects of the project:

• Is the project, as anticipated by the client, taking the right strategic approach?
• What are the desired Project Outcomes?
• Is there a better way of achieving the desired outcomes?
• Is the site appropriate?
• Would refurbishment or an extension of an existing building be a more appropriate solution?

By stringently testing the client’s Business Case and their initial thoughts on their requirements, all parties can proceed to Stage 1 confident that the Project Strategy is robust. This gives the client the comfort of knowing that the strategic aspects are correct and ensures that the project team is less likely to go down a ‘blind alley’ at Stage 1.

Stage 1

The goals of the briefing aspects at Stage 1 are to progress the client’s detailed briefing requirements and to test them against the specific issues associated with the site as well as considering matters such as Project Outcomes, Sustainability Aspirations and the Project Budget. It is recognised that there is a fine line between briefing and feasibility aspects and the development of the Concept Design; however, a skilled ‘briefmaker’ will avoid making the leap to a design solution or drawing firm conclusions at this stage. In the Guide to Using the RIBA Plan of Work 2013, the increasing use of BIM ‘briefing’ models linked to an area schedule is noted as an example of how new briefing techniques and tools are facilitating more effective briefing processes.

The three briefing stages in the RIBA Plan of Work 2013 and their importance are considered further in Chapter 5.

What are the benefits of assembling the collaborative project team prior to Stage 2?

After strategically defining the project team at Stage 0, the assembly of the project team continues during Stage 1 until the majority of the team members, and certainly those undertaking the core project roles, have been appointed prior to Stage 2 commencing.

Figure 1.3 How the requirement for project roles changes from stage to stage

Figure 1.3 illustrates an example of which project roles might be required at each stage of a project, showing how the required roles vary from stage to stage with the number of project roles ramping up during the design stages and tapering back down following project handover at the end of Stage 6. If the additional project roles were to be considered, this tapering would be even more pronounced. This diagram underlines the need to properly conceive WHO will be in the project team at an early stage (as set out in Chapter 6). If this core strategic task is not carried out, the detailed tasks to be undertaken by each role (WHAT) cannot be prepared or adequate fee allowances made within the Cost Information.

There are a number of other important reasons for ensuring that the project team is properly assembled before Stage 2 commences:

• The shift from a design team to a project team results in the involvement of a greater number of parties, with a corresponding increase in the number of relationships that have to be managed and the creation, in turn, of a greater number of contractual relationships. Determining the interrelationships between all the members of the project team is therefore an important first step.
• The core project roles can be undertaken by different parties (see page 58). It is important to consider this aspect before assembling the project team.
• The additional project roles must be carefully considered to ensure that there are no overlaps or gaps in the work being undertaken by the core project team members and, more importantly, that the need and justification for the additional roles are clear to the client.
• The relationship between the project ...