SCRUG 2/2/2017 LODPlanner

Through the miracles of changing schedules, I was able to attend this month's SCRUG meeting - the first in a long while. I estimate that about 60 people showed up.

It was announced on LinkedIn.
It was announced on Meetup.
It was detailed on the SCRUG blog.

After introductions & pizza, it went like this...
The main speaker Clive Jordan gave a bit of personal and BIM history.

In essence models progress over time. Like a painting that starts with one stroke & then becomes recognizable as more are added, a BIM begins with little geometry, accuracy, & information & becomes recognizable as a building information model.

Clive described how the terminology of BIM formed. Some familiar terms like... Level of *. Where the * could be any number of terms. Development, Definition, Information, Accuracy. While this LOD was meant to help in understanding, the splintering of terms has scattered meaning.

The goal of BIM and LEAN construction is to get information where it is needed ASAP. To this end, the BIM Execution Plan & lists of contract obligations were created. Level of Development spreadsheets & lists of who does what by when are created.

The current process of creating the Level of Development (LOD) Plan is a long and brain wracking process. Clive is working on a web based solution to shorten the FIVE day process to create the LOD Plan with Presently the site is a bit slow and it is in Beta testing till about 7/2017.

LOD planner is a question based tool to help one create the LOD document to add to design & construction contracts. Why should one adhere to a rigid set of deliverables or an arbitrary schedule. One may customize what is needed by when the next chunk of design information is needed to meet the next deadline. One can prioritize based on the goals of the owner, contractor and/or design team. Why have super detailed geometry when no renderings are required? Why load up the model with data that will never be accessed? Why have accuracy to 1/16" when accuracy to 1'-0" is all that is necessary? In short, do what is necessary & pay what is needed to get the desired results.

Now the document that the website spits out is not "set in stone". It may be altered over time and the website tracks changes. Who changed what and when. The LOD plan is a starting point in contract negotiations which may lead to changes in what is desired by when and at what price.

The requirements are divided into three chunks.

  1. Geometry - what elements are modeled (visual)
  2. Accuracy - what level is acceptable to move to the next designer's input (reliability)
  3. Information - what date needs to be embedded in the objects (quantification)
The Process
  1. Project definition and information - name, type, region default, classification, & team.
  2. Create the desired milestones for deliverables. 
  3. Add requirements for each milestone. 
    1. Why create the model? What is necessary? What are the concerns that are addressed?
    2. It is a drag & drop interface. Pull information into the timeline to create tasks. Bits of design are represented with a typical LOD illustration & industry standard definitions. 
  4. The software processes your input into a milestone plan, Gantt chart.
The project plan can be constructed in reverse order. I want this result, what inputs will give me the result? One builds the project in reverse. The software can track tasks, so when one bit of design is done or information is gathered it can email the next person in the process to notify that their required source is ready. Like going into a factory & the conveyor belt delivering a part for installation. 

What is missing?
A human being, a professional needs to check the deliverables to verify that they meet standard. 
The security part is still being worked out. Presently there are two layer of access (Admin, & Team member). One can fine tune the Team member login to grant additional rights to edit. 
Import & Export to MS Project or similar management tools are not available. 
Straight LOD numbers can be misunderstood. You may need LOD 500 data but only LOD 200 geometry. 
API - the API is private.
Integration into management systems like Trello.
Revit Data Link.

What is coming?
Machine Learning - the website tracks the choices made in creating the LOD Plan across all users. The company may then add stuff is that is often added to LOD Plans. 

My Opinion
It will save large chunks of time creating these LOD documents. The LOD document is available on a project basis for team members to see graphically what is required and therefore it will raise the industry's collective knowledge base of LOD & reign in the confusion of terms like LOD 100, 
Post a Comment

Popular posts from this blog

SCRUG 9/21/2017 Making Money with Revit, Delivering the Promise of BIM

History of Accessibility