Using DatuAI (Beta) to Query and Update Design Data

Using DatuAI (Beta) to Query and Update Design Data

Introduction

DatuAI (Beta) is a natural-language design assistant that allows project teams to query and update supported information stored in a DatuBIM design. 

Within the selected design, DatuAI can find and highlight objects, review properties and schedule relationships, perform calculations, and update supported values without requiring users to manually navigate object lists and property panels.

Beta Note: DatuAI is currently being released as a Beta feature and is identified as such within DatuBIM. The capability is still being refined. 

Before You Begin

DatuAI works with the information available in the design where the chat is opened. Before using it, confirm that the data needed for your question already exists in DatuBIM.

Depending on the request, this may include: 

Design Objects

DatuAI works with structured design objects rather than raw CAD geometry. IFC elements are already object-based; applicable 2D CAD elements must be prepared as DatuBIM objects. 

Learn More: See Preparing Design Objects for Progress Tracking. 

Object Properties

If you want to search, filter, calculate, or update a particular property, that property must already exist and contain the applicable information. 

Learn More: See Linking Design Objects to Gantt Activities.

Schedule Relationships

Questions involving planned dates, delay, or activity relationships require the applicable project schedule to be imported and the relevant design objects to be connected to activities. 

Learn More: See Importing Your Project Schedule for Progress Tracking and Linking Design Objects to Gantt Activities.

Open DatuAI

Open DatuAI from the design you want to work with.  From the Designs panel: 
  1. Locate the applicable design.
  2. Open DatuAI for that design.
           
      3. Enter your request in the chat. 

The chat opens beside the site view so the design and conversation can be reviewed together. When DatuAI selects or highlights objects, the result can be reviewed directly in the model.

Helpful Note: DatuAI works with one design at a time.  To work with a different design, open DatuAI from that design.

Query and Explore Design Data

DatuAI can search structured design information using natural-language requests. You can use it to: 
  1. Find or count objects by name, type, layer, or property
  2. Filter objects using property values or dates
  3. Identify an activity connected to an object
  4. Identify objects connected to an activity
  5. Calculate the sum, average, minimum, or maximum of numeric properties
Example requests include: 
  1. How many objects of type Pile are in this design? 
  2. Find object H-10.
  3. Show objects with volume greater than 100. 
  4. Which activity is object H-10 connected to? 
  5. What is the total volume of all foundation elements?

Select and Highlight Results

DatuAI can also visually select or highlight objects that match a request. For example: 
  1. Select all foundation elements. 
  2. Highlight the matching objects. 
  3. Highlight late objects in red and the remaining objects in green.

Review and Update Supported Information

DatuAI can read and update supported information stored on design objects. Supported activity-related fields include: 
  1. Planned Start
  2. Planned End
  3. Actual Start
  4. Actual End
  5. Inspection
  6. Approved

DatuAI can also update custom Text, Number, date, and True/False properties defined for the design.

Update Multiple Objects

Any number of objects can be updated in one request when they should all receive the same value.  For example: 

"Set the Actual End Date of all objects of type H to 23 July 2026."

DatuAI can also update several supported fields on the same object in one request. If different objects require different values, group the objects by value and send separate requests.

Clear Supported Values

DatuAI can clear supported custom properties, Actual dates, and inspection information. Planned Start and Planned End cannot be cleared. They can be changed to another valid date but cannot be left empty.

Confirm Large Updates

For very large updates, DatuAI may show the proposed change and request confirmation before anything is written. When prompted: 
  1. Review the proposed update. 
  2. Reply yes to begin.
  3. Ask status to check progress.
  4. Use cancel if the update needs to be stopped.
Changes completed before a cancellation remain in place and are reported. An unanswered confirmation expires after approximately 15 minutes. 

After the operation, review DatuAI's response to confirm what was updated, verified, failed, or skipped. If a request stops part-way through, objects reported as already updated do not need to be resent.

What NOT to Do - and What to Do Instead

DatuAI works most reliably when requests clearly identify the objects, field, and value involved. 

Don't
Do Instead
Paste a large table where every object has a different value.
Group objects by the value they should receive and send one message per value.
Combine many different changes in one message.
Use one field and one value per message when updating multiple objects.
Repeatedly resend the same failed large request in the same chat.
Open a new chat after a failed large request and continue there.
Ignore a clarifying question and repeat the original request.
Answer the clarification directly, such as "the activity field," "the custom property," "both," or the applicable activity name.
Resend objects DatuAI reports as already updated.
Resend only the objects that were not already updated.
Use ambiguous slash dates such as 7/23/2026.
Use an unambiguous format such as July 23 2026 or 07-23-2026.
Ask for activity progress percentages, amounts, quantities, or other activity-management information.
Use the applicable Tracked Activities, Gantt, or Progress Dashboard workflows instead.
Assume an update succeeded without reviewing the reply.
Review DatuAI's response to confirm what was updated, verified, failed, or skipped.





Current Beta Scope

Keep the following current scope in mind as DatuAI is in Beta: 
  1. One design per chat: DatuAI cannot search across multiple designs in the same conversation. 
  2. Text input only: Files, spreadsheets, screenshots, charts, and images cannot currently be provided to the chat. 
  3. 5,000 character-input limit: Longer content should be divided into smaller requests.
  4. Complex requests may exceed the processing limit: Requests that combine many different changes may stop before completion. Split complex work into smaller requests and review which objects were already updated before continuing. 
  5. One value per multi-object update: Multiple objects can receive the same value, but different values must be split into separate requests. 
  6. Planned dates cannot be cleared: Planned Start and Planned End can be changed but cannot be emptied. 
  7. Activity-management data is outside the current chat scope: Progress percentages, amounts, quantities, and similar activity-management information should be reviewed through Tracked Activities, Gantt, or the Progress Dashboard.
  8. Recent changes may require time to refresh: Wait for the design to finish updating or start a new chat before checking recently changed information.

Example Requests

A few examples of supported request patterns include: 

Inventory and Selection

  1. How many objects of type Foundation are in this design? 
  2. Show all objects assigned to subcontractor ABC. 
  3. Select all Foundation elements.

Schedule and QA/QC

  1. Which Foundation objects started later than their Planned Start? 
  2. Which objects are still not finished but their Planned End has passed?
  3. Which elements are finished but not yet approved?

Updates

  1. Set responsible subcontractor to ABC for all objects of type Pile.
  2. Set the Actual End of all objects of type H to July 23 2026.
  3. Clear the description for all objects of type H.
The ability to answer each request depends on the required objects, properties, dates, and relationships already existing in the selected design.

Need More Help? 

If DatuAI does not return the expected result, first confirm that the design objects, properties, dates, and schedule relationships required for the request exist and are populated.  For common error messages, failed or partial requests, refresh behavior, ambiguous fields, and additional considerations, see DatuAI (Beta) FAQ and Troubleshooting.

If additional help is needed, reach out to your Datumate Customer Success Manager.