Download PDF Where Does All This Information Belong [ DMacPJBIM08 ] to appear in the Fall 08 online version of the Journal of Building Information Modeling
COMMENT FROM JACK PARK ON THE CODE TEMPLATE CONCEPT
“I see this as a topic map question with a good query mechanism that would allow you to match patterns and bubble to the top the requisite variety of solutions to the query.
There is something you see and talk about that I rarely do, the ability to fold, twist, and reveal. I have no clue how one goes about that except along the lines I suggested in an earlier post about manifolds, intersecting them, and playing them using something like a GBG (will ask: one of these or Glass Bead Network?) as an interface.
An old (late) friend Iben Browning used to talk about using evolutionary program and “spring” metaphors to let things like this self organize. The idea is that you arrange nodes in relationship to each other and add springs between them. You can watch this happen with touchgraph - the nodes jiggle around until the dust settles. You can tweak spring coefficients until something “makes sense” – – that’s what evolutionary programming does for you.”
See the big picture of clusters and interrelations within your data, and zoom in on whatever catches your interest, by TouchGraph.
FEEDBACK FROM NICHOLAS NISBET MA (Cantab) DipArch (UNL) Director AEC3 UK Ld.
RE: “Set of data structures, or code templates, to extend semantic relationships that already exist in CSI and OCCS classifications to capture and describe building information by construction type, use group, code requirements and so on.”
I see (in the pdf below) that you are linking core concepts (Uniformat and MF2004 names) to various the classification systems and specification clauses (step 1 ,2) and related these to their usefulness for some building types (step 3-5 Looking at ICC allows you to relate some requirements to ‘core concepts’ and/or ‘building types’. COBIE exposes the classification of spaces, systems and registered types. Lastly your spreadsheet mentions standards that are relevant. Overall you have a tree of references and relationships.
Developing a set of code and classification templates to track and standardize building information modeling exchanges. See pdf for explanation.
and the following links
Building Code templates are a way of understanding the design of buildings and also what happens inside there. Some of this information is private, some is related to overall energy awareness and efficiency concerns, some are public services that could be shown on Google maps, some are simply where a person lives with preferred and ranked restaurants around them. Whatever the concerns, how do you get from all the possible information and building control system readings to the necessary and sufficient information needed for the general public to live their daily lives and participate in the governance of their local, regional, national and global community? Code templates are a stab at it. It is assumed every building type can use the same Division 01, General Conditions in their contract documents while being built. Its still unclear what happens after that in terms of the building lifecycle. Where building codes fit is still being figured out but probably in another band above Division01.