To: | "Considine, Toby (Campus Services IT)" <Toby.Considine@xxxxxxx>, "BSP Forum" <bsp-forum@xxxxxxxxxxxxxxxx> |
---|---|
Cc: | Finith E Jernigan AIA <finith@xxxxxxxxxxxxxxxxxx>, Ric Jackson <jackson@xxxxxxxxxxx>, Allan Chasey <achasey@xxxxxxx> |
From: | "Deborah MacPherson" <debmacp@xxxxxxxxx> |
Date: | Thu, 29 May 2008 23:30:58 -0400 |
Message-id: | <48f213f30805292030x3146555etc7e83b93856884a2@xxxxxxxxxxxxxx> |
Thanks everyone for pinning this down. It can be a narrow scope. I've CC to the list because we are losing ideas and information offline. I had brief meetings with a couple architects at WDG today. We are going to meet next week to evaluate the models provided by OPS and they do not fully understand the context of BPS. A clear, concise mission statement is needed for our organization to participate. Nevertheless, enough is understood to say the approach will be to apply a checklist that is a hybrid of our 7 checklists to the building models, questions and evaluation criteria the state of California and NIST fire research lab might have. Its lucky the examples being looked at and considered are not our own buildings or contractors so liabilities of the right design and what the contractor actually delivered are irrelevant. We know there will be failures. We do not know how to pre-answer, pre-format or prioritize parts of the construction documents to be reliable and accurate for local jurisdictions or Owners in the future. We don't know how to write future QA/QC into the construction documents for the Contractor to deliver at substantial completion or another set deadline when documents change their state. Our task is to try and figure out what decisions should to be automated versus thought through by a person. We will not and cannot leave everything up to automated checking because every building is brought out from thin air. People might make errors instead of taking readings which is where the whole judgement and expertise part comes in. Put plainly, its important for certain kinds of information to expire from the construction documents because relying on real time computer reports might not be correct or as intended.
WDG will not take a stab at the explaining the red arrows in the museum design process in time for Vancouver because these are uncapturable human ideas, not construction documentation or the project delivery process outside of face to face meetings. Capturing, explaining, or recording what the red arrows mean is the realm of Accuracy&Aesthetics.
The FLIPP explainers could be used for BSP purposes right away if the group can provide input, output and sets of basic criteria to David Cox to run them through his logical structures. Toby, Michelle, and Bob have seeded this field with rich material to work with. The place and time to collaborate and make things happen with SMARTcodes and ICC could be BIMstorm, it wont get done at Vancouver but holes and weaknesses could be made evident.
The questions from Huntington Beach, NIST, and Toby are really hard. WDG will stick with separating fact from fiction in the documents themselves. There is a lot we cannot see to evaluate these buildings properly, for example set backs or height limits that normally determine how to establish the proportions and locations of fire rated partitions and exit paths. We get the use groups from the Owner when a project starts and comply with local jurisdictions and their code modifications, everything proceeds from there, these are upper level performance requirements the design conforms to. That set point is probably all that needs to be known for most purposes of future building service performance requirements.
I think we should all clearly and publicly state our motivations for working on this on the wiki. I am confused by the reaction to OOR on Slashdot. If BSP was to work there would also need to be an architecture of ontologies to get the information to work together in certain ways. I don't think these are big brother type operations, exactly the opposite. We should produce statements and reports that the reasons and results are not to take over the world. Personally, the motivation at WDG is to create a relational database for everything since 1938, much which is not digitized (I am the first museum designer to work there),every single detail and checklist entry is a subject of intense discussion ala Ontolog Forum but most people don't know how to find anything. At Accuracy&Aesthetics the simple is wish for a new computer and Archicad.
Talk tomorrow On Thu, May 29, 2008 at 8:43 PM, Considine, Toby (Campus Services IT) <Toby.Considine@xxxxxxx> wrote: *************************************************
Deborah L. MacPherson Projects Director, Accuracy&Aesthetics Specifier, WDG Architecture PLLC ************************************************** _________________________________________________________________ Message Archives: http://ontolog.cim3.net/forum/bsp-forum/ Subscribe: mailto:bsp-forum-join@xxxxxxxxxxxxxxxx Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/bsp-forum/ Shared Files: http://ontolog.cim3.net/file/work/BSP/ Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?BuildingServicePerformance (01) |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [bsp-forum] BIM and O&M, Considine, Toby (Campus Services IT) |
---|---|
Next by Date: | [bsp-forum] Mission Preamble, Considine, Toby (Campus Services IT) |
Previous by Thread: | Re: [bsp-forum] BIM and O&M, Considine, Toby (Campus Services IT) |
Next by Thread: | [bsp-forum] Mission Preamble, Considine, Toby (Campus Services IT) |
Indexes: | [Date] [Thread] [Top] [All Lists] |