Skip to content
English
Go to www.deepspacesync.com
  • There are no suggestions because the search field is empty.

LOI Advanced

How to set up and use the Deep Space LOI Advanced App

Overview

The Deep Space LOI Advanced app automatically checks model data from Revit or IFC to ensure every element meets your project’s Level of Information (LOI) standards. It connects model elements to client or contractual data requirements and shows exactly where information is missing, invalid, or complete.

Why Use LOI Advanced

LOI Advanced saves time and eliminates manual checking by automatically validating your model data against project or client requirements.

Key benefits:

  • Automatic Compliance Checking: Validates Revit and IFC model data against defined project standards or client deliverables.

  • Single Source of Truth: Produces one clear validation table used by Power BI dashboards, issue logs, or reports.

  • Early Issue Detection: Identifies missing or incorrect data before deliverables are issued.

  • Cross-Platform Support: Works for both Revit and IFC models in the same workflow.

  • Audit Ready: Ensures that model data aligns with contractual obligations and ISO19650 information requirements.

How LOI Advanced Works

LOI Advanced uses a single classifying parameter to decide what attributes each element must contain.


It then compares the model data against those rules and produces a unified validation report.

Workflow Summary:

  1. Capture Data – Deep Space ingests element and parameter data from Revit or IFC model crawls.

  2. Classify Elements – Each element is grouped by the project’s unique classifying parameter (e.g., “System,” “Package,” “Asset Class”).

  3. Apply Requirements – That classification points to a matching Attribute Set, which defines all required parameters for those elements.

  4. Check and Compare – LOI Advanced reviews every element’s parameter values and checks them against the project’s validation rules (patterns, lists, or ranges).

  5. Generate Results – Each element-parameter pair receives a validation status:

    • ✅ Valid Data

    • ⚠️ Blank or Missing

    • ❌ Invalid Format

  6. Report and Review – Results are stored in a single table and visualized through Power BI dashboards or issue logs.

How To Set Up LOI Advanced

The LOI Advanced app depends on a few key setup steps to link your project configuration with your model data.

Setup Steps:

  1. Sync Your Data

    • Use Deep Space Sync for Revit to upload your project model data (Revit or IFC).

  2. Define the Classifying Parameter

    • In the Project Parameters table, set one parameter as the unique classifying parameter by turning on the unique_classifying_param flag.

    • There should be only one classifying parameter for the project (for example, “System Code” or “ELG”).

  3. Verify Parameter Name Lookup

    • Confirm that the parameter lookup (fedparam_lookup_name) has been populated via API Orchestration.

  4. Set Up Project Parameters

    • Define project parameters as you would for the LOI Report.

    • Add these parameters to a Parameter Set.

    • Map the Parameter Set to your project.

  5. Define Attributes and Attribute Sets

    • Create Attributes (the individual data checks or required parameters).

    • Create Attribute Sets, each named to match a Classifying Parameter value.

      • Example: If your classifying parameter is “ELG” and one element type has the value “ELG-MECH,” create an Attribute Set named ELG-MECH.

    • Add Attribute Set Members — these are the Attributes that belong to each Attribute Set.

  6. View in Data App / Content Manager / Super Schedule

    • Mobilise or refresh the project library to ensure all configuration data (parameters, attributes, sets) is available for validation.

  7. Run LOI Advanced

    • Refresh the LOI Advanced app.

    • The app will validate model data automatically and show results specific to your project configuration.

Minimum Requirements

  • Revit and/or IFC model crawls completed

  • One unique classifying parameter defined

  • Parameter lookup populated

  • Parameter Sets and Attribute Sets correctly mapped

  • Attributes and validation rules defined

  • Optional: Power BI dashboard configured for visualization

Output

LOI Advanced produces a unified validation table with all Revit and IFC results side by side.
The table feeds directly into dashboards, making it easy to track compliance and fix missing data before client delivery.

Here’s the same FAQ section without horizontal lines:

Frequently Asked Questions (FAQ)

Q: What is the “classifying parameter”?
A: It’s the single project parameter that tells LOI Advanced how to group and check elements. For example, “System,” “Package,” or “Asset Class.” Each unique value links to a matching Attribute Set that defines what data must be present.

Q: Can I validate both Revit and IFC models?
A: Yes. LOI Advanced automatically merges Revit and IFC data into one unified validation report with the same rule set.

Q: What happens if no classifying parameter is defined?
A: The app will skip validation because it cannot map elements to their required attributes. Always ensure one parameter is marked as unique_classifying_param.

Q: Do I need to re-run validation after updating my model?
A: Yes. Once you sync a new Revit or IFC crawl, refresh the LOI Advanced app to generate updated validation results.

Q: How does LOI Advanced handle blank or placeholder values (“–”)?
A: They’re treated as missing data and shown as “Blank” in validation results.

Q: Where can I see the results?
A: Results appear inside the LOI Advanced interface and can also be visualized in Power BI dashboards or issue logs linked to your project.

Q: Can I rename parameters between Revit and IFC?
A: Yes, but if parameter names differ, create an alias or mapping table so LOI Advanced can align IFC parameter names to the expected canonical ones.

Q: Does LOI Advanced change my model?
A: No. It only reads and validates data. You update model information in Revit or your authoring tool, then re-sync.

Q: What are the most common setup issues?
A:

  • Missing classifying parameter

  • Attribute Sets not named to match classification values

  • Parameter lookup (fedparam_lookup_name) not populated

  • Parameter Set not linked to project

Fix these, re-mobilise the project library, and refresh the app.

Q: How often should validation be run?
A: Ideally after each model update, design milestone, or before client deliverables to confirm data compliance.

Step by Step Configuration

Steps:

  1. With Deep Space Sync for Revit, sync your data
  2. Define the Classifying Parameter / attribute (do this by setting the "unique_classifying_param" flag in the Project Parameters table). There should only be 1 classifying parameter applied to your project.
  3. Ensure that the Parameter Name Lookup was populated via API Orchestration (fedparam_lookup_name)
  4. Define Project Parameters as you would for LOI Report
  5. Ensure Project Parameters are added to a Parameter Set
  6. Ensure the Parameter Set is mapped to the Project
  7. Define Attributes
  8. Define Attribute Sets. The Attribute Sets should be named to match the Classifying Parameter values. For example, if you have a Type Parameter called "ELG" that classifies your object, and that parameter has been filtered into Project Library, then you should name your Attribute Set "ELG".
  9. Define Attribute Set Members (Attributes that belong to each Attribute Set)
  10. Mobilise / Refresh Project Library for this project
  11. Refresh the LOI Advanced App and you should see your specific LOI results

How to Gain Access to the App