Deliveries in Interaxo BIM Data – gain control over who delivers what and when

Without control over data deliveries, the same problems arise repeatedly: missing parameters, data errors, and delayed deliveries. The result is that design and construction are carried out on an uncertain basis – leading to more rework, delays, and higher costs. This often leaves the project team with the same question:

What do I actually need to deliver right now – and who is responsible?

Deliveries is a new feature in Interaxo BIM Data that solves exactly this.
Here, you clearly define who is responsible for delivering what, and when it must be delivered – directly in the system where you work with the data. This provides visible requirements, clear ownership, and continuous overview – right inside Interaxo BIM Data. The result is less time spent searching and clarifying, and more time spent actually designing.

The challenge: many requirements, little focus

ISO 19650 and LOIN (Level of Information Need) make it easier for clients to describe their information requirements.
In practice, however, projects often end up with:

• Extensive BIM Execution Plans, manuals, and delivery schedules
• Hundreds of parameters (typically 200+ in Interaxo BIM Data projects)
• Limited support for distinguishing critical data from everything else

When timelines tighten, designers must prioritize. Without clear focus, all fields appear equally important – increasing the risk of errors, missing information, and incomplete deliveries.

What is “Deliveries” in Interaxo BIM Data?

With Deliveries, LOIN becomes tangible in everyday work. Instead of having requirements existing only “outside” the system, you can:

• Define data deliveries as part of the project’s status and milestone settings
• Link each delivery to:
  • Who: which user group is responsible
  • When: the milestone or status by which the data must be ready
  • What: which parameters and object categories the requirement applies to

The goal is not to create deliveries for every parameter, but to identify the data that is critical for project progress and sound decision-making.

Who is this for?

Design managers and model managers
– who need overview, predictability, and traceability of what is to be delivered and when.
Architects and consulting engineers
– who work hands-on with models and data and need to know exactly which fields they are responsible for at each milestone.

From requirements to actionable deliveries

In the Status & Milestones → Deliveries tab, you set up data deliveries:

1. Delivery name
   Give the delivery a clear name – preferably including theme and purpose, for example:
   “Fire rating – walls – MMI 300”
2. Who: responsible user group
   Select one or more user groups responsible for the delivery
   (e.g. Architect and Structural Engineer if both model walls).
3. When: milestone/status
   Link the delivery to a milestone – think: “this data must be ready by the next milestone”.
4. What: parameters
   Select which parameters are included in the delivery – these are the core data you expect to be delivered.
5. What: object categories
   Define which object categories the delivery applies to
   (e.g. walls, doors, or windows).

As you define deliveries, the list of available parameters in the delivery setup will gradually be reduced, helping you maintain a clear focus on the most important data.

Contact us if you would like help getting started with Deliveries!