Flexible LOI Auditing Dashboards Overview

Overview

Deep Space Core Thread Technology supports maximum flexibility around Level-Of-Information (LOI) auditing.

The Deep Space LOI checking system is a flexible, automated learning framework. It responds to the current project stage, supports multiple LOI Groups, datatype verification, and provides fast visual insight. It allows you to load a MPDT (Model Production Delivery Table) direct from Excel.

Current Apps

There are three tiers of LOI data management in Deep Space:

LOI Report - minimal configuration. Only need to configure Project Parameters and set the "Include in Simple LOI" flag. Read more about LOI Report here.
LOI Advanced - use a classifying parameter to drive the LOI requirements through Attribute Sets. Read more about LOI Advanced here.
LOI Pro - considered in detail in the remained of this article. Read more about LOI Pro here.

Deep Space LOI Apps Feature Comparison

	LOI Report	LOI Advanced	LOI Pro
Project wide universal parameter checking	✅	❌	❌
Classifying parameter based checking	❌	✅	❌
MPDT (Model Production Delivery Table) based checking	❌	❌	✅
Category, Family, Type mapping to Classification	❌	❌	✅
Discipline Intelligence	❌	❌	✅
Implicit parameter based mapping to Classification via Project Library		✅
Load MPDT from Excel Template			✅
IFC Support	✅	✅
Revit Shared Parameter GUID checking	✅	✅
Uses Deep Space Project Library		✅
Link with Asset Portal		✅
Missing / Blank / Not Blank conditions	✅	✅
Data Type checking			✅
Support Extendable Metadata (link to Deep Space Forms)		✅
Support Merged Parameters such as from IFC converted to Revit	✅
Use Simple LOI flag	✅	❌	❌
Duplicate Value Checking	✅
Support Moment in Time Analysis (not Phased Delivery)	✅	✅
Support 7 Phases in MPDT with 3 degrees of Attribute Detail			✅
Uses Deep Space Attributes and Parameter Mapping		✅	✅
Uses configurable Attribute Sets		✅
Uses Deep Space Project Parameter Set only	✅

Legacy Apps

Project Parameter Report - a legacy middle tier auditing system

This article generally describes the steps required to set up and use the LOI Pro App in Deep Space.

Note: for discussion around Classification Systems, please refer to this article.

LOI Pro Configuration

Firstly, there are some key Workspace settings:

Workspace Default Classification Scheme - set this in ws settings

The system is configured as follows :

A project is created
The project stage is set (up to 7 stages currently supported)
The MPDT settings are configured

The MPDT can be configured in three main ways :

A Deep Space provided template can be loaded to the project with project automation
A custom MPDT can be loaded to the project with project automation
The settings can be configured manually

To configure manually, the following steps are taken:

The project MPDT current version is set
The custom classification list is populated
The custom class to Revit element mapping is created
The attribute list is created at the workspace level, and LOI group field is used
The attribute to Revit parameter mapping is created
The MPDT is entered with MPDT version, Project Stage, Custom Class, and LOI group
The LOI dashboard is refreshed

For details on Shared Parameter configuration in DS Command, refer to Parameter Configuration

LOI Pro Automated Setup

To improve configuration speed, you can:

Run an automation to populate Revit Category list to bda_class_custom (workspace automation name is mpdt_populate_revit_as_classes )

LOI Pro Attribute Class Filter

After configuring your MPDT, you may still find that some attributes are being checking for objects where it really isn't need.

In Deep Space, you can define an attribute-class pair and individually set whether or not that pair will be checked in LOI Pro App.

The key data entry table is bda_class_attribute_filter

We can supply an automated procedure to pre-populate if you wish to use this feature.

LOI Pro Troubleshooting

At the Project Level, you must set:

mpdt_current_version to MATCH the desired this_entry_mpdt_version in bda_class_scheme_map
the Custom Classification -> Discipline field must MATCH the File Discipline exactly