Purpose of LOD Framework & Key Terms in ALICE Pro


This LOD framework guides customers on best practices for selecting the appropriate BIM level of detail and schedule levels for planning in ALICE. This LOD framework helps customers accelerate time to value with ALICE during schedule development depending on the project phase, available data, and value objectives.

Learning objectives

  1. A standardized approach for communicating 3D model LOD and schedule levels in ALICE
  2. Enable project teams to plan and control projects with ALICE from concept to construction
  3. Enable project teams to build rapid prototype models for planning in ALICE 
  4. Provide users with downloadable template Visual WBS 3D Models they can easily use for planning

Key Terms

Important definitions in the ALICE universe 

ALICE is a Dynamic Level of Detail system 

  • Contractors and owners work with limited information to guide projects from conceptual design through construction, using historical data to budget and forecast future costs, duration, and delivery milestones. The ALICE platform helps contractors and owners make data-driven decisions from the early stages through detailed coordination, pull planning, and production control.
  • ALICE supports planning from conceptual level 1 schedule (1-2 hours to develop) to fully coordinated level 4 schedules (several days or weeks to develop for more complex projects).
  • By digitizing building methods and best practices into Recipes in ALICE, templates can be created to automatically generate cost and resource-loaded level 2 schedules using your recipe database. 
  • Development of level 3 and 4 schedules will generally require additional data and coordination with the project team (typical of a well-planned project). These details may be developed in the preconstruction, buyout, and construction phases depending on the project delivery methods.
  • Legacy CPM software is limited in its ability to manage Level 4 detail schedules, which is why field execution schedules are often managed outside of the master CPM schedule (as a different CPM schedule or in excel.) ALICE makes managing execution-level schedules significantly easier and provides a bridge in communication between the field, project management, and scheduling departments.  

BIM Level of Detail (LOD)

  • Defines how much detail is included in the model element
  • BIM LOD is often thought of as input to the element

Template 3D Model Files



Level of detail (LOD)



Time to develop:

LOD 100

Model element represented in the model with a symbol of other generic representation. Not geometric representations. Non-graphic information can be attached to the model element as user-defined fields (UDF)

1-4 hours for commercial

1-2 days for infra/industrial

LOD 200

Model element is represented within the model as a generic system, object, or assembly with approximate size, shape, and location. Non-graphic information can be attached to the model element as user-defined fields (UDF)

1-2 days for commercial

1-5 days for infra / industrial

LOD 300

The quantity, size, shape, location, and orientation of the element as designed can be measured directly from the model

6-12 months depending on size & complexity 

LOD 400

Modeled with sufficient detail and accuracy for fabrication of the represented component

1-2+ years

Depending on size & complexity  

Important note:

Please don’t let waiting for a 3D model stop you from starting your project planning with ALICE. We have preloaded templates by segment and conceptual planning models that can be used to Quick Start your project and accelerate time to value. Your Customer Success team is also available to help you quickly develop the models required to meet your project objectives.


  • Notes on BIM Level of Development 
    • The degree to which the element's geometry has been thought through
    • Usually used for construction coordination, shop drawings, and fabrication
    • ALICE eliminates the requirement to develop expensive and time-consuming LOD 400 models (typically used for fabrication).
    • We recommend starting with rapid prototype LOD 100 models and not taking your ALICE model beyond LOD 350 for ease of use and adaptability (don't worry, you won't miss the essential details we'll add in the recipe)

Schedule Level Definitions 

  • This refers to the details of activities in an issued schedule
  • See the table below for a summary of schedule-level definitions 

Schedule Levels


Time to develop in ALICE

(for a complex project over $500M)

Level 1: 

Milestones & key dates

Executive Summary, Major Milestones, one pager highlights major milestones and key deliverables

1-2 days

Level 2:

Systems Summary

Summary Master Schedules (SMS), major project components broken up by area or major item of capital equipment, should demonstrate the driving path for structures and major systems at the CSI division level.

1-2 weeks

Level 3: 

Project Coordination

Project Coordination Schedule (PCS), consists of integrated level 4 schedules based on CPM, developed with detailed input from the project team in planning. 

Suppose the Level 4 schedules are primarily developed by trade/sub-contractors during the initial phases of the project. In that case, the Level 3 schedule provides the schedule framework and constraints used by the subcontractors to develop their tenders. 

During the project's execution phase, this schedule defines the overall critical path and is the primary coordination tool for the overall project. Audiences for this type of schedule include but are not limited to program or project managers, CMs or owner's representatives, superintendents, and general foremen.

2-4 weeks

Level 4: 

Project Execution

Execution Schedule or Project Working Schedule developed by the project management team and with subcontractor input fully cost and resource-loaded (labor, equipment, materials)

1-2 months


User Defined Fields in ALICE (UDFs)

  • UDFs in ALICE are used to import or create metadata that can be assigned to model elements and used in recipes 
  • UDFs are used to import project data instead of modeling exact geometry or quantities in 3D.
  • Examples of UDF metadata that can be imported to elements in ALICE
    • All relevant metadata
    • Material quantities (sf, lf, cy) 
    • Length, height, width, etc
    • Production rates
    • Cost codes
    • Resources




Was this article helpful?
1 out of 1 found this helpful