Tuesday afternoon. Yes, I splitted tuesday in two because of the length. And as I just woke up from a good night's sleep! Read on. Paul Anderson: information overload
Well, the talk was good, but it was a lot of statistical data, so just two quotes. Lets say that there is too much information going around.
She just got her PhD last week, so congratulations!
There are many assumptions or stereotypes associated with resistance to IT:
Her research tried to find whether these stereotypes could reliably predict people's resistance to IT technologies. Her research focused on people, not the technology. The focus was also on individual people, not on organisations as a whole.
A survey at 50 local firms lowered down the number of criterea found in literature (67...) to just 9. A second, bigger, survey allowed her to compare those 9 possible criterea to the surveyed people's characteristics. Some of the results:
So from the list of stereotypes:
I missed some, only one: you can identify resistors to IT change and then try to bring them around.
In responce to Martin Betts: The biggest message for AEC it research is that people have to accept your work, so look at it from that angle.
There is a difference between an architect and an engineer. The engineer's work with information is structured, complete, integral. The architect's work with information is unstructured, incomplete and inconsistent.
Most building industry software promisses you total control, total information, to the 10th of a millimeter. Just look what archicat, nemetschek and autocad promise...
Now we have, just as one of the examples, a drawing that specifies the location of the corner of a brick wall to the 10th of a millimeter. Well, you cannot make a brick wall to that precision. Anything under a 2 cm difference is good.
So take a few decimal places off. It helps cut down the amount of information.
We have to allow for Unknown Stuff.
In Germany they have a database with "stocks". Basic standard things with statictical data associated with it. Like "a school building has normally 0.3 m^2 of glass per 1m^2 of floor area". That's a beginning. Order of magnitude.
Who generates the information? Who needs it? And for both: what, when, why, how?
Much information has to do with things that need doing: tasks. Tasks can be in two modes:
If somebody recieves information, he filters and processes the information and adds to it. An electrical installer will only use the basic information from the architect's drawings and add his info to that basic drawing info.
From the preliminary conclusions: *the level of complexity of the design and construction process is significantly more complex than reflected in the normally available construction documents.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):