Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Preparing Your Autodesk Civil 3D Model for the ORIS Plugin

Practical guidance before connecting your model to ORIS.

The quality of your ORIS assessment depends on the quality of the data the plugin reads from your Civil 3D drawing. A small amount of preparation before connecting your model makes the extraction cleaner, reduces manual correction in ORIS, and improves the confidence of AI material matching. The same data quality principles that apply to the ORIS open BIM Module apply here. This article focuses on what is specific to Civil 3D.

General Preparation

Corridor Solids

Quantity Takeoff Mode

Property Sets and AI Mapping


General Preparation

Before connecting the plugin, review your Civil 3D drawing with the extraction in mind. The goal is to make the structure and properties as clear and consistent as possible so the plugin and the AI can work accurately.

  • Select only objects in scope for the carbon assessment, do not include objects that add noise to the extraction and increase manual mapping effort in ORIS.
  • Manage disciplines separately. Avoid connecting a federated model covering multiple disciplines in a single plugin session. Process each discipline independently to keep file sizes manageable and extractions focused.
  • Ensure your drawing is geolocated. The plugin uses the Civil 3D geolocation settings to determine the project location in ORIS, transforming local coordinates to WGS84. Check that the drawing's coordinate system is correctly set before connecting.

 

Corridor Solids

If you are using the object selection mode with 3D corridor solids, the following preparation steps help ensure clean and consistent extraction.

KEEP THE CORRIDOR-SOLID LINK

When generating corridor solids, enable the option to keep the link between the corridor and the solids. This allows the plugin to detect when the corridor has been rebuilt and the solids have changed, enabling accurate updates to your ORIS assessment over time. Without this link, the plugin cannot track corridor-driven changes.

USE CODENAME CONSISTENTLY

The Codename property is typically the most reliable property for grouping corridor elements in ORIS, as it stores the assembly name. Ensure Codename is populated and consistent across all solids of the same type. Inconsistent naming within the same element type creates multiple rows for the same material in ORIS.

 

Quantity Takeoff Mode

If you are using the quantity takeoff mode instead of 3D solids, the same principles apply but the preparation happens in the quantity takeoff structure rather than in the solid objects.

  • Define your material list clearly in the quantity takeoff before connecting. Each material entry in the takeoff becomes a line item in ORIS.
  • Use specific, descriptive material names in your quantity takeoff. The AI uses these names alongside any description properties to match materials in the carbon database. Vague names such as 'fill' or 'material 1' produce low-confidence matches.

Tip: When a material specification is missing

In early design phases, material specifications are not always defined. When this is the case, apply conservative assumptions by selecting a material likely to overestimate rather than underestimate the carbon impact. This avoids underreporting emissions and can always be updated as the design develops. Consider building a set of typical material assumptions for common structural elements used in your projects, so your team has a consistent starting point when specifications are incomplete.


Property Sets and AI Mapping

The richer the property data attached to your Civil 3D objects, the more accurately the AI can match materials to entries in the carbon database. Where possible:

  • Add a dedicated property layer or set that describes the material type and specification alongside the Codename. This gives the AI more context beyond the assembly name alone.
  • Align property naming with the terminology used in your target carbon database. Familiar terms produce higher-confidence matches and reduce manual correction after mapping.
  • Apply uniform naming conventions across all elements of the same type. Inconsistent naming within a group creates duplicate rows and reduces the effectiveness of AI mapping.

Further reading

For detailed guidance on categorisation, quantities, units, and material metadata once your data is in ORIS, refer to articles related to the open BIM module.