Hypermodeling infuses the project’s documentation into the 3D model, automatically.
After using BIM for 10 years myself I noticed it goes only half way (or less). To automate documents is one thing, but this does nothing at all, really, to improve the communicative effectiveness of documentation, the purpose of which is - to communicate effectively. It's about the medium of communication itself, which needs improvement. This is achieved (now) by infusing the project’s documentation into 3D, automatically. ..which is not unlike infusing synchronized audio into moving picture, because doing so elevates the effectiveness of both audio (contextualized in picture) and picture (clarified by synchronized sound).
http://en.wikipedia.org/wiki/Silent_filmWithout Hypermodeling, you're just making silent film - speechless 3D that cannot be delivered because it carries nothing but ambiguity. Now the model is clarified by exactly what the team said it wanted to say about a project in its documentation..
Regarding non-technical hurdles, this technical advance solves a major hurdle:
Have you noticed that while you are exerting yourself with BIM processes, that what you get from your effort is:
• a stack of construction document drawings that, while better coordinated, in the end are no better at communicating your design and construction than is any stack of construction drawings created by any other (non-BIM) process, and
• a 3D model limited in its utility by its almost complete ambiguity with regard to necessary limits of scope, authority and completeness (no one knows which locations in the model are reliable, nor what anyone has to say that clarifies any particular location).
The ambiguity of the latter is the reason 3D fails as a reliable deliverable; while the clarity of a set of documents is directly attributable to their ability to delineate limits of scope, authority, and completeness.
When clarity regarding limits of scope, authority, and completeness are present, communication succeeds. When these limits are not known or unclear communication fails.
Observation shows that the designation of these necessary limits is a function carried by a familiar device: the callout symbols that populate a set of documents.
What is called out is included in the document set; what is not called out is excluded from the document set.
Follow the logic of documents:
1. A team calls out what it will include in the document set.
2. The device for calling out is a "callout."
3. What is in the document set is what is called out.
4. The team is responsible for that which is included in the document set.
The essential function of a callout is to designate the team's limits of scope, authority, and completeness. (Secondarily, to allow navigation through a document set.)
There is no satisfactory logic that claims that callouts should not be present in 3D; that they should not communicate the same limits of scope, authority, and completeness in 3D as they do in documents. What logic would there be that claims that a 3D model should not be clarified by the clarifying remarks and graphics of the project's own documentation?
Some hurdles are justifiable.
When industry resists adoption of 3D models as a reliable delivery medium, it does so with just cause, because until now models have been entirely ambiguous.
No longer.
Model Documentation disambiguates 3D models.
Now you can see which locations have been called out, and you can what the team has said about those locations in the project's documentation.
The clarifying remarks and graphics of the project's documentation are infused automatically into the 3D model, on demand.
The result is a far richer medium of communication than either conventional documents or ambiguous 3D models as they have previously been known.
Now the effectiveness of project communication is truly elevated allowing everyone to better see and understand what they are doing, what the project is, and what it will be.
We serve the eggs and the ham, cooked. Extensive rework in Ss3 for usability, simplicity, performance.
The creation of views is (in Ss3) centered entirely on the placement of callouts (as it should be)
You place a callout, and you’re done. A drawing is made, and you drag it from a list to put it on a sheet.
If you do that, then what you see in the video is automatic. You do nothing – and you get that.
What do you get? A document set infused with 3D models AND a 3D model infused with document graphics.
That is where we'll lead the industry now, because that is where it obviously needs to be. Prior to this BIM did next to nothing to elevate the communicative effectiveness of the design and documentation process.
Now it does. Now there is a useful and valuable objective realized: to see and understand what you are doing better than you could have before; to put things in plain sight in order to gain insight (and deliver it).
Rob,
Thanks for the invite. Fortunately I'm really busy right now. Hopefully after the first of the year my schedule will loosen up.
I must admit I'd like to see how you are approaching this because to be honest the current stuff is quite a hogpog approach and I don't see happening without some major cleanup and streamling.
I won't argue with you about the technical possibilities of what your talking about. The gap between what is technically possible and and commonly used is huge. There are still a large amount of hurdles you have to overcome yet. Technology is the littlest one. It's not a "builded it and they will come" situation. More of a Green Eggs and Ham and you guys haven't even cooked the eggs yet.
Regards,
DavidG
I add that all of this (live documentation and live Model Documentation) works even when your project model is comprised of a hybrid of live linked models from all of these formats:
DGN
Real DWG
3DS
SHP (ESRI)
MIF/MID
TAB
FBX
IFC
OBJ
3DM (Rhino)
SKP (Sketchup)
Plus, plug-in connections to many more formats..
When using Bentley V8i SELECTseries3 design, review, construction, and operation applications, Model Documentation infuses the project’s documentation into the 3D model, automatically.
It's in beta, by invitation. If you would like an invitation, send an e-mail to rob.snyder@bentley.com