AI and DWG: work with objects, units and drawing evidence

Choose a route to the drawing's objects

An engineer asking for the distance between two boundaries needs coordinates, geometry and units. A text list of layers cannot answer that question. An architect reconciling door marks may only need a table of block attributes. Decide what data the operation requires before uploading the file.

There are four useful routes: export selected data from CAD, process a supported interchange file with a checked script, use a configured CAD connector, or use a service with a drawing reader. An ordinary chat attachment does not establish object access. Ask the system to identify a known object and report its properties before assigning a larger task.

Autodesk documents a Revit public MCP server as a technology preview. Connectors are therefore a real category, but availability depends on the installed product, configuration and exposed actions. A connector for one environment does not imply the same access in another chat or in ARAI.

Inspect blocks, dimensions and curves

A block definition and a placed block instance are different things. Count placements when they represent physical items; apply each instance's position, rotation and scale when measuring geometry inside it. Nested blocks need the combined transformations. A legend symbol or repeated detail view can otherwise inflate a quantity.

Treat attributes as data requiring validation. A door block may have an empty mark or reuse an old identifier. Adjacent text may look like an attribute without being attached to the block. Require the selection and matching rule, including how dynamic or unnamed blocks are handled.

Separate displayed dimension text from geometric measurement. A number can have been overridden manually or drawn as loose text. Curved polylines also need proper handling: joining vertices with straight segments changes the boundary. Ask which entity types were measured and which were excluded; an unsupported curve must not quietly become a chord.

Establish space, references and units

Model space contains geometry; sheets arrange views for issue. A physical object shown in two viewports is still one object. State whether the task concerns model quantities or sheet visibility.

Request an external-reference inventory. A missing linked services drawing prevents a coordination check; it does not establish that no services exist. Retain the links' insertion transforms and the file revisions used.

Confirm declared units with a known distance. A coordinate difference of 6000 could represent millimetres or another convention. Record whether the requested distance is horizontal, vertical or three-dimensional. For site work, preserve the coordinate and elevation reference rather than moving the geometry to an unexplained origin.

For Revit-originated material, export the required views to supported DWG or PDF. Autodesk's DWG/DXF export settings distinguish units and coordinate basis. Verify the exported control geometry; this workflow does not promise native RVT processing.

Worked example: geometry and annotation disagree

Suppose two parallel faces overlap along their length and are 6000 mm apart in the confirmed drawing coordinates. A nearby annotation reads 6500. These are illustrative values, not a design requirement.

In revision C, measure the shortest horizontal distance between the two marked boundary objects. Confirm millimetres using the supplied control distance. Return object IDs, endpoints and the measurement method. Report nearby dimension text separately. Do not move geometry or replace annotations. List missing references and unsupported objects.

The expected geometric result is 6000 mm, or 6 m. The reviewer then checks whether the 6500 annotation belongs to those same faces, has an override or refers to another condition. Choosing the more plausible value would conceal the issue.

Repeat the measurement in CAD and retain the marked endpoints. If the boundaries are curved or skewed, use a method suited to them; success with parallel faces does not validate every geometry type.

Accept a result you can reproduce

A drawing report should identify the input revision, included objects, units, method and unresolved exclusions. For edits, require a new file and a change list, then open the output in the receiving CAD workflow. Check geometry and plotted presentation separately.

ARAI can inspect supported DWG/DXF files and prepare reviewable engineering outputs. Prepare an object-based inspection request. Review the unsent draft, attach the drawing and specify a control distance. For reading scans instead, see drawing recognition.