AiN Engine is a cloud platform for automatic Bill of Quantities (BOQ) generation from BIM models connected through Autodesk Platform Services.

The primary review workflow is:

Cloud Files → APS Viewer → Model Derivative / SVF2 → BOQ generation → Excel export

Users can connect to Autodesk Forma, Autodesk Construction Cloud, or BIM 360, select a model file such as RVT, IFC, NWD, or NWC where available through Autodesk Platform Services, load the model in the embedded APS Viewer, and generate a BOQ from the viewable model data.

AiN Engine supports quantity review, model-linked BOQ workflows, live table editing, Excel export, AI-assisted classification, manual review, pricing workflows, and multi-model analysis.

Standards and formats:

• PEREK style BOQ workflows for Israel.
• CSI MasterFormat style classification for US workflows.
• NRM2 / RICS style quantity structuring for UK workflows.
• Excel export for downstream review, pricing, and reporting.

Autodesk access model:

• AiN Engine is read-only with respect to Autodesk hubs, projects, folders, and files.
• AiN Engine does not request write scopes.
• AiN Engine does not upload, delete, rename, move, overwrite, or modify Autodesk files.
• AiN Engine does not write BOQ data back into Autodesk Forma, Autodesk Construction Cloud, or BIM 360.

Authentication and permissions:

• 3-Legged OAuth, Authorization Code flow: used for end-user sign-in and read-only access to Autodesk hubs, projects, folders, and model files that the signed-in user is already permitted to access.
• 2-Legged OAuth, Client Credentials flow: used server-side for Autodesk Platform Services operations such as short-lived viewer tokens and Model Derivative status checks where applicable.
• Minimum requested scopes: data:read, viewables:read, user-profile:read.
• No data:write, account:read, or admin scopes are requested.

AEC Data Model note:

AEC Data Model support is under controlled rollout where available and is not required for the main App Store review workflow. The stable production review path is based on Cloud Files, APS Viewer, Model Derivative / SVF2, and BOQ generation.