One of the big BIM benefits has to be persistent and consistent data. We come across persistent data every day of our lives, we expect individual ATMs to be able to access our bank accounts and produce money regardless of who we bank with (well we do in the UK). We also expect to be able to log in to our email on our phones, at home or on the move. There's a lot of underpinning work that supports all of these things. Now let's compare with a landscape specification.
Assuming that the specification is complete, works done and handed over, but remedial work needs to be done. You're a temp working for the company doing the remedial work and it's your job to find out what plants it is you need to replace some recently deceased one. You will need to find out who holds the landscape design documentation, not generally, not usually, but actually, who holds it, for this project, right now. Then you will need to go to them or have them sent to you, you might need permission to access their physical files and you might then be required to physically go to the archive and dig out the document. Of course, back then we didn't have a filing system so it's in one of those boxes... you get the picture. Things get lost very easily and it gets chaotic.
So that's clear. Now, what if, following these remedial works the specification needs to change? I think you can see the difference.
Product Data Templates are the first step to creating a consistent and persistent store for your project's specifications and other data. These PDTs indicate what can be stored and how. Once these have been complete, the job will be to create databases that hold this information for people to easily create, view and edit specifications in a fraction of the amount of time it currently takes.
For more information on PDTs check out.
http://bimtalk.co.uk/
No comments:
Post a Comment