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........