A lengthy Twitter conversation last night and this morning has got me thinking about the Common Data Environment (CDE), BIM and the role of the various Software-as-a-Service collaboration vendors that operate in the architecture, engineering and construction space.
Common Data Environment
As many readers may know, the UK government has mandated building information modelling for public sector projects. By 2016, designers, contractors, subcontractors, suppliers and other project team members working on public sector projects will need to achieve ‘Level 2’ BIM. This means, according to a 2011 BIM Strategy Working Party report (PDF here), using collaboration platforms – eg: 4Projects, Asite, Conject, etc – as a “data management server” (since described as the CDE) to share data between multiple ‘federated’ models, with 4D construction sequencing and/or 5D cost information in linked repositories.
Since 2011, the BIM Task Group has coordinated industry efforts to create structures and methodologies to accommodate BIM. Earlier this year, on 28 February, the British Standards Institution published PAS 1192-2 which provides guidance on how the CDE might work, but other process issues remain, such as ownership of the model or data, intellectual property, commercially sensitive information, risk and insurance, contract forms, early involvement of supply chains, etc. Last night’s Twitter conversation saw some debate about who should pay for the system and how it should be managed.
CDE: taking online collaboration to BIM and beyond
I have long held that SaaS-based platforms are the natural home for BIM data. However, at the moment, much of the BIM debate is focused on the design and construction phases, and less on the data requirements of the ultimate owner or operator of the built assets. But the Twitter conversation (like the ground-breaking discussions about BIM, FM and Government Soft Landings at ThinkBIM in Leeds in July 2012 and July 2013) included contributions from a facilities management perspective. For, once clients begin to benefit from the collation and re-use of data, and the addition of complementary information gained through asset operation, they will – I hope – quickly begin to insist on the use of a CDE to manage any future project(s) they procure.
OK, there are limits to the amount of detail that can be included in tweets, but a lot of useful points emerged. QS Dave Monswhite, for example, said the CDE should be in the business case or cost plan: “It’s a project cost, like design fees”.
Kath Fontana, MD of BAM FM, and BIM manager Olly Thomas, took up the theme of using the employer’s information requirements (EIR) as a starting point, but asked “who pays for the CDE?”. I jumped in and likened the CDE to current use of collaboration platforms: “Client ends up paying … either directly or indirectly [so] make CDE explicitly client owned.” Making information an indivisible part of the built asset is in the client’s best interest, particularly when it can feed data to future briefs, and become part of a “whole life cost” solution, enabling continuous post-occupancy evaluation.
A recurring theme in the Twitter conversation was the need to promote a collaborative culture to enable BIM to work, and how some project team members might be reluctant to take the risk of managing the CDE (thanks, Matt McCarter). I again took the example of SaaS collaboration vendors – their customers (contractors, clients, consultants, etc) transfer that risk to them as they are specialists in providing online data management services, with service level agreements in place to cover uptime, reliability, etc. This avoids budget silos, I said, as the third party SaaS vendors are trusted experts sitting outside the traditional project team (I also mentioned integrated project insurance as one way in which teams could be incentivised through gain/pain sharing mechanisms to collaborate and think in the client’s best long-term interests).
SaaS and CDE
2016 is now just over two years away and some SaaS vendors are moving more quickly than others towards supporting the CDE requirement. I have talked about 4Projects’ 4BIM initiative several times (eg: April 2013); Asite has long pushed its cBIM capabilities; Aconex’s CEO Leigh Jasper is talking about BIM as a key trend for 2014; and Conject is now blogging about its BIM plans too. I’m looking forward to hearing more from all of these vendors (and others!) about how they will be providing CDEs to support clients and their project team’s long-term data requirements.