Defining Your Specific Levels of Detail in an MPS



I hope you saw Friday’s with Vico last week where my colleague, Marcel Broekmaat, demonstrated the MPS 3.0.  We received a few more questions after the event so I thought I would try to clarify and answer one here which I think is very important to understand.


Q. As for LOD and MPS - there are opinions that a significant gap exists between LOD 300 and 400, that I agree with. Depending on the part of the world you are in, an intermediate model is required, where not only the geometry but the actual design details of all the systems in the building are fixed. It is not at the level of the fabrication/shop drawings, meaning it is not linked to any specific supplier, provider of the service or the subcontractor, but it is exactly defined. In many regions this level of information is required for the building permit submission.


A. Those “opinions” are exactly the reason why we have evolved the MPS from v1 (which was adopted and became the AIA E202), to v2 which had a rigid pairing of aspects and classes, to v3 which is what we all saw in the webinar along with the introduction of primitives.  As we all know, Design can progress at different rates even for elements which are closely connected. As a simple example you may have agreed on the external wall spec but not on the windows.


Estimating and scheduling also progress at different rates so to have a model which is completely one LOD, while it is possible, is quite unlikely.  We found ourselves having LOD 350, 375, etc., for the gray areas!  


Instead of Vico or the AIA defining what the LODs are, we now have a framework which allows your firm and the project team to define what the LODs mean to you.


You can define one which suits all your projects or adapt them for specific projects. The key is that it suits you and your project teams.


aspects classes and level of detail for MPS


You decide what the Aspects are you need to cater for on a project or as a company standard, Model, Cost, Scheduling, Environmental, etc., and then you define the Classes of each which suit your own working practices.


Then you create a matrix which maps the likely scenarios. So you can have as many LODs as you require. Ours is purely an example of what works for us and we provide project-based workshops to guide our clients through the process of creating their own. Some clients do use the same as ours and others completely change it.


As long as it is clearly defined, everyone knows what the plan is and what they need to produce at any given project stage.  This eliminates nasty surprises and provides the means for a much more parallel preconstruction process as opposed to the traditional linear one.


What other questions do you have about the MPS - we would love to hear them.  Or take a look at our FAQs page for the MPS to learn more.


Here are some additional resources for your team:

Video: Understand the BIM Level of Detail 

Video: What Is a Purpose-Built BIM Model?

Video: Who is Authoring the BIM Model?

Video: The MPS as Sheet Music for an Orchestra

Webinar: Webcor and the MPS

Webinar: Using the Content Plan and MPS

Webinar: Understanding the Model Progression Specification

Webinar: The MPS 3.0

Blog: What Can Be Done to Improve BIM Model Fidelity?



Tags: MPS, purpose-built BIM models, model fidelity, MPS 3.0, AIA E202, BIM LOD, model progression specification, BIM for Construction, level of detail