search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
22


ROUND TABLE REVIEW


“We need to have the mindset that there will be no physical or digital documents in future, there will only be data in systems” Chris Lees, Data Clan


The devil is in the details


Chris Lees of Data Clan changed the focus to look at practical needs of end-clients in the housing sector in particular, and what the data should look like them for them to manage buildings effectively. He said the Safety Regulator was requiring them to produce documents “that they couldn’t possibly understand.” He added that AI and machine learning “will help, but it won’t solve the problem.”


Lees said that in the Common Data Environment itself, project data needed to be “machine-led” as opposed to “people-led,” but had concerns that “at the moment we have all these systems which are people-first, which means nothing can happen without a person – there aren’t enough people for the amount of information we have.” Lees added that the standardisation that MMC enabled would support the machine-driven data aspects he was advocating, but also that there is a “middle ground” between prefabrication and bespoke, ie the “mass customisation” found in the world of PC design.


He bemoaned current best practice in this area as “very disappointing,” advocating ‘Connected Data Environments,” rather than the “repository of data” approach currently being seen.


Session 2: Addressing Attendees’ Questions The second session was focused around explorations of the questions submitted by our panel, and delved further into some of the issues already discussed more generally in the first session. These ranged from whether there could be a ‘single source of truth’ as called for by the Hackitt Report (Ben Wallbank), to whether architects would indeed be emerging as Principal Designers as well


WWW.ARCHITECTSDATAFILE.CO.UK


as Lead Designers in projects (Richard Harrison). Other questions included how smaller architectural firms should resource how they address these data challenges (Hannah Pinsent), and what specific competencies were required of project stakeholders in the operational phase.


Lucy Craig from Mace said that the “biggest challenge the industry faces is how do we ensure that the products and systems are compatible and safe. This requires a collaborative approach by all and recognition that more is required by all to get to a descriptive state, but how do we see this process working going forward, and who is the best competent discipline to lead such a complex approach? We also looked at the manufacturer’s role, and where it overlaps


with that of designers (and their liabilities). Subjects raised included the new CCPI product certification within the Golden Thread; will it ensure products are performing as intended, and how can the digital world help product designers ensure compliance? Richard Harrison added that new Principal Designer role carried the risk that it “would just be another role and increase the complexity, which was causing some of the problems – the lack of communication, misunderstandings, and so-called value engineering going on behind closed doors.” Lucy Craig agreed that architects taking the role of Principal Designer raised issues, as they will work “based on integrity,” and they “will have to be strong to maintain the integrity of the project all the way through.” Peter Sutcliffe commented: “I think we will see architects taking on more of that role, but not on their own.” Ben Wallbank said that he wasn’t convinced the Principal Designer role would strengthen architects due to the nature of Design & Build Contracts, but that


ADF MAY 2024


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84