You are on page 1of 20

Just one piece of the Level 1 jigsaw – a discussion session

Duncan Reed, Digital Construction Process Manager, Trimble Solutions (UK) Ltd

Suitability Codes
BS 1192:2007 Container numbering
 BS1192 uses the term ‘containers’ for
defining each of the cells in the project
numbering system
 This is the numbering system to be used by
all parties for all project documentation
 There are ten fields to be completed
– 3 are fixed at the start of the project
– 4 more are defined at the start of the project

[Project] - [Originator] - [Zones] - [Levels] - [Type] - [Role] - [Classification] - [Number] - [Suitability] - [Revision]
Suitability
Work in Progress

 WIP is only shared internally


 Should never appear on a project CDE?
 May not be appropriate to an organisation?
Shared

 S1 – models shared for co-ordination (clash detection?)


 But only for graphical content of models
Shared

 S2 – what does information mean in this context?


 Not sure how this code can be used
Shared

 S3 – like S1 but for non-graphical information and documents


 So used together with S1?
Shared

 S4 – documents only
 So linked to current contractual arrangement? Models
provided by documents are the deliverables?
Shared

 S5 and S6 – new to the A1 revision


Published

 At best ‘use at risk’ must be defined


 Can any of these codes practically be used?
BS1192:2007 ‘D’ codes (superseded)

 In the original standard the term ‘Published’ wasn’t used,


instead it was ‘Documentation’
 Pre-construction sign-off actually makes a lot of sense
 So - should a project BEP perhaps amend the current table
to reflect the WIP > Shared > Published workflow
Published

 D1 – data for client side costing?


 So NOT tender information
Published

 D2 - the data and documents sent to a contractor to tender


 Models not issued at tender stage?
Published

 D3 – all forms of information can be issued with this


suitability code for this purpose
Published

 D4 – ‘unauthorized and use at risk’ yet ‘Suitable for


Manufacture/Procurement?
 The previous term of ‘Pre-construction sign off codes’
makes much more sense in my opinion
Published

 Approved – OK we understand that....


 But – A1, A2, A3 – when the next container is ‘Revision’?
Published

 B codes – the reality of the industry


 Should we be trying better though?
Archive

 CR – principally only from Published - status A - information


 Key point is in the title – published for the AIM
Suitability Codes
 In principle are great
 They help to protect the supply chain
 But still not totally ‘fool-proof’
 Use them - in accordance with the standard
 You might not use all of them

 So agree how they are to be used on your project and


record this in the BEP
E: duncan.reed@trimble.com
M: +44 7734 740240
T: @djhreed67

Thank You

You might also like