Tuesday, November 27, 2012

2016 & the BIM-enabled graduate

 (I just realised I never got around to posting externally this article from my Atkins internal blog on my external one - so here it is! These are the words and some slides for a talk I gave in April 2012 at the ICE to ACED - the Heads of Department for the UK's civil and structural degrees. Por Ray Purvis also presented, as did Costain. You can see the full slide deck at http://www.jbm.org.uk/uploads/ACED_Atkins_John_Roberts.pdf)
 
Assets in the built environment: How it was 
o    The client wrote something
o    The designer drew something
o    Contractor A dug something
o    Contractor B poured something
o    Contractor C bolted something on
o    The client paid the utility bills
o    Contractor D added some stuff
o    One day it got knocked down

These were separate activities by separate entities, carried out in a potentially adversarial contractual atmosphere. At each step there was a loss of data and inefficiency crept in.

We are now moving towards a nirvana that has been talked about for a decade or so now, but now we are starting to smell it, see it and are almost touching it. Instead of the old process we move to one where there is a clear flow of data through the project, being added to, evolving, refining and eventually being usefully delivered to end users, informing and supporting the lifetime use of the asset.


This flow of data is one key way to achieve the key aims of the Government's Construction strategy. It is a key step towards improving the performance of the government estate in terms of its cost, value and carbon performance: "the purposeful management of information throughout the lifecycle of an infrastructure project”. BIM becomes is the key vehicle for information on its journey through the project lifecycle in a managed process.

So let's think about the key abilities and behaviours all team members are going to need when working with information on this journey. Two key aspects are going to be:
o    Understanding data management
o    Ability to work within a virtual environment

In fundamental terms all our team members need to understand how to receive or source data, use or develop data and then finally issue or archive data.

Let's think about civil infrastructure projects - as there is much more diversity in its data formats than for building projects. When starting a project the simple phrase 'survey' has been replaced by an increasing range of geomatic data types, file formats and all sorts of geospatially related information.

Understanding what you have got and what you can get is a key first step for any project. It is also vitally important to understand the level of reliance you can place on received data. It is easy to fall into the trap that digital data is accurate to multiple decimal points. Since this information is about to become enshrined in everything that follows it is important that engineers know the issues to question about data accuracy.

Next new data gets generated within that context. At the moment that is mainly the model data that we use to generate our 'drawings', but generation of, or linkage with, our analysis, programme, cost and carbon data is now all feasible and adoption is mainly limited by the speed our teams are able to incorporate multiple parallel innovations into their standard practice. A key skill will be how data sources can be combined to efficiently generate optimised designs.

And once a design has been developed that information needs to be issued and be suitable for its legacy end use. When we just issued paper drawings to a contractor we didn't need to anticipate how the end user would once day be interfacing with that data. BIM is going to require our designers to understand much more about our client's future needs.

So you can see that one of the key requirements of BIM is that team members understand how to manage data on this journey. Data sources, file types, data reliability and the way it can be combined are all key issues that engineers must understand to make sure a project's information journey is successful as it passes through their hands. 

Alongside that it is vital that all team members are able engage in a collaborative 3D virtual project environment. I have great hopes that that BIM is going to reverse a fragmentation that has crept into the industry with CAD.

Once upon a time design offices were places with big drawings boards where everyone could see how the design was developing over the days a drawing took to produce. It was naturally a social, collaborative environment and experienced eyes naturally saw everything going out of the office.
The CAD-based office at its worst has been a very different animal. Potentially you have the Nintendo generation all focused on their own small screens. The team of engineers are each looking at a series of unrelated analysis models. Meanwhile a separate CAD team are working on unrelated 2D plans and sections. This is not a naturally collaborative diagram.

If we get it right the BIM-enabled design team could look like this. Design, analysis and delivery  teams all looking at a single shared version of the truth. We're not there yet as an industry but this is an implicitly collaborative diagram.

Our ability to move to this way of working is based on all our team members being able to engage in a 3D virtual project environment. They need to be able to conceptualise, scheme, analyse, review and deliver in that environment. If you can't work in 3D you will effectively be locked out of the project.

A final thought about interfaces and design management. Once upon a time kids played with wooden blocks. They were loose fit, but if you were careful and didn't knock them over you can lots of fun building stuff. 

Then there was then an unrelated series of technology changes enabling highly accurate plastic injection moulding. A Dane invented an interface standard that remains unchanged to this day.


Now, it always feels that new rules are going to tie your hands and stifle creativity. However that is evidently not the case with Lego. There are now a huge variety of block types and colours and you only have to go to Legoland to see that that interface standard has allowed a toy to move well beyond what could be achieved with mere wooden blocks. I was proud to see my Canary Wharf Station roof there two weeks ago - fame indeed!

So, why am I telling you this? A technology change has triggered as similar revolution in the way the building blocks of design data fit together. The best run projects have always been the ones that implement best practice design management. Our Lego standards are BS1192, BIM execution plans and a planned delivery process.

Of course, management of these interfaces actually isn't new. If you are good you are naturally doing all this already.
o    Ray and I call it design management
o    Costain might call it construction management
o    The operator would call it facilities management, and
o    The client might call it asset management

The only thing that BIM changes is that you absolutely can't get away with ignoring the issues about how your work relates to the overall project.  It is no longer good enough only for your technical work to be technically excellent. Introducing your wooden block into a Lego project will not work. Your work needs to be delivered to BS1192 and project standards and your data has to be reliable and reusable by the other team members who will rely on it. BIM requires us to be much sharper on our Design Management.


So, it is now 4 years time. You are delivering this year's batch of 4-year course Masters students to the industry. It is 2016 and the Government's Construction Strategy has provided the catalyst for the whole of UK construction to be at or above Level 2 BIM. 2D AutoCAD is dead. Why am I going to employ your graduates?

Why I'll employ a grad in September 2016:
o    To understand data
·   the sources, formats, reliability and use
o    An ability to be engaged in a collaborative 3D virtual environment
·   to receive, review, evolve, create, share, deliver
o    To have a clear appreciation of design management
·   the lifecycle of data from inception to completion 

If you can give me that I'll be happy. At one level I think this is quite a simple list of 'new' requirements.
Note however, this is isn't an 'expert' list. These are not PhDs from your new department of BIM. This is not Ray's new BIM team. This is 'entry level' for grads. This is right alongside wl2/8. If they don't have the potential for working this way there isn't really a place in the UK construction industry for them.

They will be wooden blocks in a Lego world.

Wednesday, November 14, 2012

Simplicity - and safety

I was attracted to last night's ICE and Costain Prestige Health and Safety Lecture at Great George Street by one word - Simplicity.

A lot of what I've been thinking about and doing for the last couple of year has been around the fact that life is already complicated enough without us adding to it. The Design Principles are an attempt to cut through all those processes (that I either don't know about or don't follow) and to try an express something simpler that we all 'get' and actually 'do' all of the time.

There were three good speakers on behavioural safety, but the first, Gareth Llewellyn from Network Rail resonated with me the most. Up until recently Network Rail had over 1600 standards and procedures around safety (four to do with the right colour orange for safety gear). As a result they had over 4000 non-compliances. What sort of message did that send out to their employees at the sharp end, down at track level amongst the trains?

Working with the support of Trade Unions they have now agreed 11 "Lifesaving Rules" - clear messages that address the vast majority of their risks. Which are:

Contact with trains:
- Always have a valid safe system of work in place before going on or near the line.

Working with electricity:
- Always have a valid permit to work where required.
- Always test before applying earths.
- Never assume equipment is isolated – always test before touch.

Working at height:
- Unless it is clear other protection is in place, never work at height without a safety harness.
- Always use equipment for working at heights that is fit for purpose.

Working moving equipment:
- Never enter the agreed exclusion zone, unless directed to by the person in charge.

Driving:
- Always wear a seat belt while in a moving vehicle and always obey the speed limit.
- Never use a hand-held device or programme any hands-free device while you are driving a road vehicle.

Taking responsibility:
- Never undertake an activity unless you have been trained, assessed as competent and have the right equipment.
- Never drive or work while under the influence of drugs or alcohol.

I understand that - and apparently the feedback is that Network Rail's teams do as well. This is a great example of removing unnecessary complexity and there are strong parallels with what we have done with the Design Principles.

Network Rail's next stage was to create a culture where reporting was encourages and reporting. However, this was not focused on making sure the guilty could be punished though. Only 10% of incidents were deliberate of malicious. 90% were due to system failures and the feedback received meant that something could be done to address these problems.

Beyond that Network Rail worked with the Unions and asked them to set what the consequences for infringements should be. This has removed many debates about 'fairness' and everyone understands the consequences of their actions – a key aspect of developing a safety culture.

 A few additional fun soundbites to think about:

“Nobody has ever been regulated into a world class safety culture.”

“The highest standards we can expect are the lowest standards we personally exhibit.”
 
"If you don't like the cost of compliance, try non-compliance".

And the weight loss analogy: For success you need to do the right thing all the time and check once a week. So why do often stand on the scales daily and agonise about what we ate last night? Less measurement and more behaviour!

Monday, October 22, 2012

My letter in NCE

A on 4 October "The Origins of the Species" almost struck a chord with me, but had one very duff note. It wanted us all to be more focused on doing our existing activities correctly before complicating life by adding BIM. Yes, it is important we get better at this stuff, but BIM is a way that can help us achieve this. Don't hold back but think carefully, simplify, clarify and focus on purpose and quality.  
The letter below ended up published on 18 October as 'BIM is here if we want it" - not my title!
"Michael Redhead implores “the construction industry to improve working practices before adding to the complexity of the design process” by introducing BIM. BIM requires our industry to improve, standardise and simplify the way we share information throughout procurement, delivery and operation.
Technology and skills have made production of 2D drawings from a 3D model cost effective. Now these models exist, many ‘downstream’ activities in the supply chain, such as pricing and programming, can attach data to a project’s advantage. Legacy operational data is beginning to appear over the horizon of the possible.
We recently bid our first project where we received a BIM model as part of the tender package. This radically improved the way the design and construction teams worked together to bid the job. As models of the permanent works become the norm I am sure better, faster, cheaper temporary works will follow. 
Better basic information will be a key output of BIM. Mr Redman can look forward to always knowing where ground level is as his borehole logs will be geospatially fixed within industry standard BIM workflows. The technology is already there for the log to ‘know’ where it is. Our industry just needs to organise itself."

Thursday, July 19, 2012

Raining Olympic Champions

I hope it stops raining before the Olympics. After all the effort put in by the country (and Atkins!) it is important that UK plc gets its moment in the sun.

These games will be the greenest ever – or as it was put at the snappily named ‘Green Building Council’s London 2012 Lessons Learnt Grand Finale’, perhaps we should say the least non-sustainable games in modern history.

So there will be a strong sense of irony if these become the first games disrupted by climate change.


New Scientist (7 July 2012) returned to its task of clearly showing that climate change is real and here. ‘Freak weather is fast becoming normal’, evidenced by not only this terrible UK summer, but the US’s ‘Summer in March’ with one weather station breaking its record by 17 degrees Centigrade (yep – not Fahrenheit).

One key issue it addressed was how “our weather is getting wilder – more variable as well as steadily hotter.” Decade by decade the land temperatures over the northern hemisphere (see graph below) show the bell curve both shifting and widening as the planet warms. Whilst the average has moved up by around 0.8 degrees Centigrade the bottom temperatures have remained similar, but the top of the range is up by almost two!

So how’s that going to look when the centre of the bell curve is 4 degrees higher? By pumping 30 Giga-tonnes of carbon dioxide into the atmosphere annually we are conducting the world’s biggest science experiment. And since we are pretty sure of the answer, and it is not good, why are we carrying on?

New Scientist finishes off with our new favourite weather phrase – the ‘Lazy Jet Stream’ that has so far wrecked our summer. Firm predictions of its movements seem difficult – apparently partly because the meshing on our climate change models is still relatively coarse at around 2km. Think about that next time you are meshing a flat slab for analysis!

Still the BBC seems to think the Jet Stream is going back north next week. After reading this article I fear that may be more hope than science.

Fingers crossed then! I hope it stops raining before the Olympics.

Sunday, July 08, 2012

Thoughts after too much code

Reproduced from my Atkins blog article of 09.03.12
I have just spent a few hours going through aspects of BS1192 with some of our key CAD and BIM people. This code will be central to our data management as we make a success of adopting BIM across all our Infrastructure projects – it is not just for buildings!
Three side thoughts I need to remember to take forward (hence being jotted here):
  1. What review and when: Central to BS1192 is the idea of moving data through a process of WIP (Work In Progress), Shared and Issued. What are the differences between the levels of check, review and authorise as data moves up these two steps. Does WIP to shared have a lower level of review that Shared to Issued for instance. How does this fit into the process required by our BMS (and reiterated in the upcoming Design Principles)?
  2. How do we slickly review our BIM data? At the moment we are stuck in 2D, with engineers looking at the drawn output. Perhaps this is appropriate when the client wants a 2D deliverable. However can we start making the leap to reviewing 3D dwfs and marking these up using tools from Autodesk? I need to make some experiments as this is probably the way for effective 'high level' reviews before drawings start to get spat out.
  3. Finally, how do we communicate the status of data when items in one model have different levels of completeness and firmness? One key thing to remember is that we can’t replace the effectiveness of team members actually talking to each other, but are there ways we can tag objects within a model so users are clear of their status. Ray Purvis says he has a cunning plan........

Autodesk BIM Conference 2011 – Crossing the chasm

Reproduced from my Atkins blog article of 22.11.2011
I just spent a valuable day at Autodesk’s UK BIM conference in London. The event had its focus clearly on ‘not Why, but How’ and had been aimed at senior managers rather than users. There were a huge number of grey suits and no one demonstrated software, so I think they succeeded in gaining their audience. Key presentations included:
1. The conference was opened by Phil Bernstein, VP of Industry Strategy & Relations at Autodesk and, interestingly, the guy who made the decision for them to buy Revit. He contrasted progress either side of the Atlantic towards BIM as:

· UK - solid theoretical progress with papers being written by industry leaders supported by government, but meanwhile slow uptake ‘on the ground’ with small and sustained groups of enthusiasts being watched by the industry to see what they will do, and...
· US – lots happening but no organising principles being developed to tie industry together as BIM develops further.

Phil felt BIM in the UK was an good example of ‘Chasm Theory’ (Geoffrey Moore) with adoption having happened for the Techies and Visionaries, but still being in the chasm just before take up by the Pragmatists, Conservatives and finally Sceptics. In the last 12 months the force that is finally driving the UK across the chasm is the Government Construction Strategy which aims to realise improvements in construction, productivity and the environment with BIM as the key enabler.

 2. Next up was Paul Morrell, who is leading implementation of this strategy. As Paul put it this is the transition from builder’s bum to builder’s BIM (I worked with Paul in the 90s and the jokes haven’t got better!).

Paul sees the requirement for industry to move to Level 2 BIM by 2016 as not being a ‘Big Bang’ requiring major change. The focus for his team is very much on determining what future Plans of Work will require as part of the Data Drops at key stages for client review. What information is needed for all teams’ models to talk to each other? Only ask for what you will use and what gets taken out of the model is a key focus for deliverables.

No one so far found a coherent case against BIM once they have started using it. Every business is undergoing a journey and his message was (and I quote) “INTEGRATE YOU BASTARDS!”

Paul’s message was followed up in the afternoon by David Philp of the Cabinet Office. His view was that the UK’s approach is now at the point where ‘the US will start to learn from us’, a view supported by the fact that Paul Morrell is just back from consulting in Washington how the US government can rein in multiple BIM initiatives by various departments. David saw that early adoption of Asset Information Modelling and COBie 2.4 potentially gives the UK future export opportunities as ‘our way’ becomes a default world standard. Makes you proud!

3. There were two very good presentations from HoK, who are rightly seen as industry leaders. In the second Andrew Barraclough noted that their implementation had been based around a firmwide view with no exceptions.

Shared internal guidelines and standards were created and a ‘tipping point’ of what success would look like set, with 65% of technical staff using BIM software daily (now just being achieved in their leading offices – some are much further behind). It was important to choose the first projects wisely to ensure success, and designers needed to be on board, moving away from tools such as SketchUp, to avoid Revit being seen as only a delivery tool.

4. James Middling’s description of progress at Motts closely fits where Atkins is going.

Motts is currently in the business of joining up ‘islands of excellence’ driven by a strong message from the top. Senior management have developed a clear view of how BIM will support their existing business plans, thought of how they can make it happen, and then appointed Champions to push this change ‘top down’.

Meanwhile local centres of learning, seeds and superusers are being developed around the globe to provide ‘bottom up’ pressure. They have an interesting ‘virtuous triangle’ joining up experienced 2D technicians undergoing conversion, new graduates and senior professionals who all can feed off each other’s experience, enthusiasm and skills.

James’ key message was ‘it won’t happen without the top down pressure’. He saw the main blocker to adoption as the ‘blancmange layer’ – his unfortunate name for the PMs and PDs who have all be keeping us in business for the past few years through their pragmatism and labours. Getting them to take what they see as a risk to delivery is a key issue, but all people pushing BIM adoption need to work on the message and their support at this level as these guys will eventually be the key supporters.

Other fun facts and thoughts:

5. Phil Bernstein mentioned that the US military consumes 1% of the world’s energy and one third of that is in their building stock. They see huge savings to be made through improving energy and facility management through BIM.

6. To date Autodesk have spend $600million on Revit and are just hitting break even. Scary though this number is, in reality they have managed to replace the cash cow that is AutoCAD financed off only part of the cash flow it generates. Here’s to the next 15 years for Autodesk I guess!

7. Chris Millard from Balfour Beatty: How come UPS can tell us exactly where our parcels are in the world but we don’t know where we store stuff on site?

8. David Miller, who leads a Revit based architectural practice presented how they have grown from 4 to 20 people in four years of recession. It was impressive to see what clear direction and a small empowered group can do. At the coffee break all us ‘big boys’ were discussing ‘wouldn’t it be nice to do it that way’. Interestingly it was strange to see how late BIM execution plans appeared in their development timeline as everyone sees them as a key implementation document for collaboration.

9. Jamie Johnson of Brydan Wood noted the financial advantages of tying BIM development into a company’s R&D tax credit scheme.

Climate Change: What we do know – and what we don’t.

Reproduced from my Atkins blog article of 18.11.2011

“The big thing we are working on now the global warming hoax. It’s all voodoo, nonsense hokum, a hoax.”
Michele Bachmann, candidate for the Republican nomination for US President, 2008.
There were two great articles in New Scientist on 22 and 29 October, tackling what we know about climate change, and the rise of science rejectionism (my word). If you get your science from the Daily Mail or Fox News you often are told that climate change is not understood and thus should be doubted. As New Scientist notes:

Know: Greenhouse gases are warming the planet.
Don’t know: How far greenhouse gas levels will rise.
Know: Other pollutants are cooling the planet.
Don’t Know: How great our cooling effects are.
Know: The planet is going to get a lot hotter.
Don’t know: Exactly how much hotter things will get.
Don’t know: How the climate will change in specific regions.
Know: Sea level is going to rise many metres.
Don’t know: How quickly sea level will rise.
Don’t know: How serious a threat global warming is to life.
Know: There will be more floods and droughts.
Don’t know: Whether there will be more hurricanes and the like.
Don’t know: If and when tipping points will be reached.

We don’t actually understand gravity either. It could be a particle, or a wave, but favourite is that is a distortion in multi-dimensional space time.

Despite not understanding it the advice remains ‘don’t jump off tall buildings’.

The list of ‘Know/Don’t Know’ above makes it clear we need to act to reduce our impact on the climate. We can’t stop it but we can mitigate.

Personal actions I have taken to get ahead of the inevitable changes to the economy:
  • I sold my house from 1870 (an energy nightmare) and have bought a flat from 2003 (much more efficient and hence will keep its value better).
  • When I reinvested the balance in property to let I turned down options near sea level as once public opinion realises the inevitable they will instantly become worthless.
Have you considered what will your property be worth when the inevitability of climate change is accepted by all?

Scan&Solve for Rhino

Reproduced from my Atkins blog of 15.09.2011
As anyone who has been bored by me on the subject will know, my favourite program for the past decade has been Rhino. For accurate engineering 3D modelling I think it can’t be beat! Add in the great renders you can get from Flamingo and who could want more.
When I was invited to a webinar on Scan&Solve, a new analytical plug-in for Rhino the idea was so strange I had to have a listen. Analysis programs have been improving their graphics for years. But a graphics program improving its analysis? Weird.

Scan&Solve wasn’t written only for Rhino and may be adapted to work for other 3D modelling software. It works on solids, not assemblies, and is able to work on any Rhino object that can give volume data.

To be honest though, I am not impressed. The guys presenting it evidently come out of an academic background and are doing some pretty interesting stuff – but I am not sure if it is useful to us, and there are other programs that probably do it better. Currently it is limited to single materials with few releases and not that huge models. Add in the strange use of ‘Danger Level’ instead of terms like utilisation and the hopes of composite materials ‘like reinforced concrete’ being dealt with and I came away not at all sure if they knew where they were heading and what the business model is for their future. ‘We’re working on it’ was the answer to many questions.

Not for structural engineers. Maybe (only maybe) for mechanicals? I think most of the others on the webinar were architects and product designers who seemed to be excited by being able to do analysis on their models but, from their questions, they didn’t really know what they needed to know (see previous post!). Perhaps the main thing engineers need to know about Scan&Solve is that there are architects out there who may think they can do it all now without us!

The two things I did like perhaps might get used from the free version at home on some future competition. Firstly it can show the deformed shape and then export that as a mesh model. This has been done before but here it drops neatly back into Rhino and could be used interestingly. Secondly it can ‘bake’ the coloured contour plots for results back into the Rhino model. They actually showed 3D printed models with some very funky colour schemes based on the results.

Which reminds me to get the 3D printing project going sometime soon!

If you want to see a recording of the webinar it is at this link. One instead of Eastenders perhaps.

The Curse of Knowledge - Is Ignorance Bliss?

Reproduced from my Atkins blog of 24.08.2011
New Scientist magazine has just confirmed something I’ve suspected for a while.
Aged twelve I was an avid fan of the ‘Goodies Book of Criminal Records’. Tim Brooke-Taylor’s election claim was that ‘given I know nothing I can approach everything with an open mind’. This truth has strangely stuck with me.

Similarly, Rajeev Rameth and I have often mused that the most dangerous type of engineer was the one who ‘didn’t know what he didn’t know’. They would blindly design the most ridiculous of structures in complete confidence whilst those seemingly full of self-doubt could be relied on to make logical progress towards a safe solution.

Richard Fisher in New Scientist (30 July) discusses ‘The curse of knowledge’ which can hamper performance in many fields. It was first spotted in second-hand car salesmen. The sellers who knew the cars best – all the plus points and all the flaws – assumed that their customers also did, and priced accordingly. In doing so they misjudged the market and often got lower prices than the ones ignorant of all the details.

Since then psychologists have found similar problems in other disciplines. “It’s an oxymoron, but ignorance can be a virtue in education”. To teach effectively you need to be able to see things from the naïve perspective of the pupil – and the more you know the harder that becomes.

One of the key points New Scientist made was that “experts should say ‘don’t know’ in their own field of expertise more often” and this matches closely to my own conclusions. When faced by a design problem it is vital that you understand the split of things you don’t know and what you do – and then test why you have those preconceptions about the latter. Don’t allow your ego to pretend you know the answers.

Increasingly often I find it useful to pull teams right back to basics. Why are we doing this? Do we really know what we are doing? Who actually knows what we need to know? By doing this the team should become absolutely clear on what the true basis of design is. Later when new requirements, pressures and ideas arise they are in a much stronger position to steer the project through these changes.

They also probably have a rosier, more positive view of the future as they plunge into the future challenges than the all knowing expert. As David Dunning of Cornell University notes “there are usually two stages to any given task: planning and execution. Whilst you are more likely to be successful if you think through the first stage a fully realistic picture during the second could be a hindrance, not a help.”

Donald Rumsfeld evidently wasn’t far off the truth (for once): “There are known knowns. There are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns -- the ones we don't know we don't know.”

To succeed we should all doubt ourselves more!

Or should we?

Repeat after me: ‘I don’t know’.

The rest of the Excitech AEC BIM Forum 2011

Reproduced from my Atkins blog of 08.07.2011
So what was talked about during the rest of the Excitech AEC BIM Forum? The three key themes were ‘The BIM needs of contractors’, ‘BIM implementation, process and trends’ and ‘Managing Revit project data’.

1. Capturing lessons learned: this will be a key activity as we move through 3D CAD into true BIM. How was it for all the parties involved? Were Client expectations met? What were the timescales and benefits? Where were the delays? Was the BIM process effective and was clash-free construction achieved? Often we have all not been great at capturing, reflecting on and sharing lessons.

2. Key reading: I must get hold of “The Business Value of BIM in Europe” – everyone was using this as a key source. ’The Government Construction Strategy’ and ‘The Government Construction Client Report’ are also important, but are much more likely to aid insomniacs.

3. Design Process: Whilst CAD just replaced the old pen and ink tools we used, BIM changes the underlying design processes and we need to structure its use in order ensure we gain what it can give. Rapid Energy Modelling is an example of how structured data will allow new opportunities. I must find out who in Atkins is doing this now.

4. Beyond Revit: It is vital to keep aware of all the other applications that Revit plugs into. It is this interconnectedness that moves from 3D CAD to BIM. Revit alone will not deliver your BIM needs and a clear ‘Application Workflow’ must be set up.

5. Know why and what: Key frustrations to avoid are a) not being clear why models are being constructed and b) constructing them at the wrong level of detail. A project BEP and an understanding of the design process will avoid these.

6. The Client’s part: Paul Shilcock from TFL felt it was the Client’s duty to get involved, to know what it wants and finally to make active use of the BIM product (“use it or lose it”). Most of Atkins’ BIM work is currently for our own needs, but the learning curve will continue when our Clients want BIM data as a design deliverable

Final thought: Shaun and Kyla Farrell (no relation) from Zaha Hadid gave great and clear presentations on how they deliver their complex geometrical buildings through a full BIM process. Although some of their comments do not apply to the ‘normal’ rectilinear world I was again impressed how the team at ZH can communicate so much complexity effectively.

Download the presentations at this link

BIM-plementation – Do you have a BEP?

Reproduced from my Atkins blog of  01.07.2011
The key new question that all Project Directors and Design Managers need to ask before they sign up for that new project is:

“Is there a BIM Execution Plan?”
In the recent ‘CAD era’ everyone we worked with, internally and externally, knew a CAD strategy could be sorted out as the project got up and running. Several decades of development meant the industry knew its way around the standards and protocols

Welcome the ‘BIM era’! It’s all going to be more confusing for a few years.

Atkins' Ray Purvis, Anne Kemp and I attended the annual Excitech BIM Forum on Thursday 30 June. The need for BIM Execution Plans (BEPs) right at the start of a job was being clearly heard around the room. The BEP might come from the Client, or it might come from Design Team, but if there isn’t one you are heading for trouble.

Atkins has been at the forefront of developing BIM standards for the industry. The AEC (UK) BIM Standard was the work of our Global BIM Excellence Group and they are developing our own proforma BEP.

According to Excitech’s presentation typically a BEP will define:

· Project initiation
· The modelling plan
· The analysis plan
· The collaboration plan
· The technology plan

It’s not rocket science, but if you don’t have one agreed across the whole Client’s team sharing information is going to cause frustrations and delay.

For our project in Jeddah Atkins are implementing Revit modelling on a scale we haven’t done before - pan-office, pan-region. Jeddah is a key step on our journey from 3D-CAD towards BIM – there is no turning back after this! The ongoing dialogue across our CAD community (evolving into our BIM community) has been key for collaboration for a project where there is not a client sponsored BEP.

Networking at the Excitech forum we heard that BIM interfaces between some other consultants are not going quite so smoothly. Good to see Atkins ahead of the game.

So Mr Project Director, next time you are about to land your next multi-consultant mega-project, pause and ask the Client if he has a BEP in place. And if he hasn’t, sell him one.

You’ll regret it if you don’t!

Crushingly simple – the START approach from OTBconcrete

Reproduced from my Atkins blog of 30.06.2011.
Isn’t it great when something that has been quietly bugging you for years finally gets sorted out in your head?

Back in 1989 I worked on site in Newcastle using tunnel formwork to pour hotel bedrooms - the Copthorne Closegate Hotel, now you ask. The keys to the rapid reuse of this expensively hired formwork were heating of the newly poured slabs and walls using propane burners and ‘match cured’ cubes resting on top of the slab. These were crushed twelve hours after the pour and proved that we had the strength we needed for depropping.


Looking back it was all rather basic and not helped by a particularly dopey contractor (who went bust later in the project, so I’m probably safe to say that). But at least we thought it was conservative. However it has always nagged at me that there must be a more scientific way accurately establish the rate of strength gain on site.

Christer Isgren from OBTconcrete gave a lunchtime presentation to the Building Structures team in Epsom last week and spoke about their START system for monitoring the early strength gain of insitu concrete. They work closely with RC frame contractors who are looking to accelerate their programmes through rapid turn-around of formwork or early prestressing.

This is probably all old hat for the nuclear and dam boys, used to big pours, who need to control early age temperatures and cracking, but it looked like rocket science to this building engineer!

But the great thing is that, at heart, it is blindingly simple once you look past all the temperature sensors and wiring around the pour:

1. It is all based around knowing exactly how your concrete performs at 20degC. They crush lots of cubes at the start of the job for every type of concrete used – cement supplier, cement replacements, additives.....all must match.

2. ‘Setting’ is actually a chemical reaction and it relies on water. Thus when the concrete is at zero the reaction stops as the water is frozen.

3. The brilliantly simple bit is that the speed of ‘setting’ is basically linearly proportional to the temperature above zero. So if the concrete were at 10degC for four days it would have the same strength as a two day cube. If it had been at 40degC it would be the same as an eight day cube.

Of course it is more complicated than that actually, but that is enough for me to know what is going on.

The START system monitors the temperature of the concrete both on the surface and inside. It accurately measures that early period (perhaps several days) when the heat of hydration pops the temperatures up to 40degC or more. During this period the insitu concrete’s strength is actually ahead of the cube in its warm bath, and it is this period that START allows the contractor to exploit.

Christer’s background is from Sweden and Skanska, and it was interesting to hear how they had to ‘relearn’ many things in the UK due to our regular use of PFA and GGBS. He also discussed the important differences between, and impacts of, the many retarders, accelerators, etc. out there on the market.

Of course, as a building design consultant all this is ‘interesting’ but will be the responsibility of the contractor to sort out, not me.

However, I have stopped that 22 year old doubt nagging at me. No longer wilI I feel the need to I ask for the whole building to have a warm bath for 28 days.