Question 1

How do you auto-triage RFIs across thousands of Procore project documents without hallucinating answers?

Accepted Answer

RFIs are routed through a retrieval pipeline grounded in the project's own corpus: contract drawings, specifications (CSI MasterFormat divisions), submittals, prior RFI threads, and the Autodesk Construction Cloud document set pulled via the Forge Data Management API. Each suggested answer cites the exact spec section, sheet number, and revision — if the retriever cannot ground a claim above a confidence threshold the system escalates to the design team rather than guessing. Industry baseline of 14–21 days drops to 24–72 hours on the answerable subset, which is typically 55–70% of incoming RFIs.

Question 2

Can you do quantity takeoff directly from Revit and IFC models?

Accepted Answer

Yes — IFC4 and IFC2x3 are first-class inputs. We parse via IfcOpenShell for the open path and Autodesk Platform Services Model Derivative API for the Revit path. Quantities are reconciled against the CSI MasterFormat division and the estimator's assembly catalog, with explicit handling for IfcWall / IfcSlab / IfcBeam / IfcColumn and the WBS rollup. Variance against the prior-revision model is reported per element-GUID so the estimator sees exactly what changed between issues.

Question 3

How do you build OSHA-aware safety computer vision without becoming a surveillance liability?

Accepted Answer

Models run on edge devices (NVIDIA Jetson or AWS Panorama at the trailer) so raw video never leaves the jobsite. Detection is restricted to PPE categories (hard hat, hi-vis, harness, fall protection) and OSHA 29 CFR 1926 hazard classes (struck-by, caught-in, fall-from-height, electrical proximity). Detections are aggregated into anonymised incident counts that feed TRIR (per 200,000 hours) and the OSHA Form 300 / 300A / 301 recordable workflow — individual identification is off by default and gated behind a written labor agreement when on.

Question 4

Do you integrate with Autodesk Construction Cloud and BIM 360, or do we have to migrate?

Accepted Answer

We integrate with both. ACC is the strategic platform via Autodesk Platform Services (Forge) — Data Management for files and folders, Model Derivative for geometry / properties, Issues API in BIM Collaborate Pro, and Webhooks for events. BIM 360 remains supported via its v1 API where the customer has not yet migrated. The same connector exposes a unified document and issue model upstream so downstream RFI / submittal / punch-list AI works identically across both.

Question 5

How does schedule-risk forecasting actually work against the published P6 or MS Project schedule?

Accepted Answer

We ingest the baseline schedule (Primavera P6 XER / XML or MS Project MPP), then join daily reports, sub progress percentages and weather data per-activity. A gradient-boosted survival model estimates the probability of slip per activity at the next look-ahead window and rolls up to a Schedule Performance Index (SPI) trajectory. The output is not "the project will slip 14 days" — it is the top-N activities driving the slip, ranked by counterfactual recovery, so the superintendent has a fightable list rather than a verdict.

Question 6

Can you automate submittal review against the specification?

Accepted Answer

Yes. The submittal PDF is parsed (Bluebeam Revu Studio Prime export or direct PDF + OCR), field values are extracted, then matched against the relevant spec section pulled from the project manual. Common checks: manufacturer / model against approved-manufacturer list, performance values against spec minima, color/finish against architect selections, ASTM / UL test references against required standards. The output is a markup ready for the architect — accepted-as-noted, revise-and-resubmit, or rejected — with citations to both the spec section and the submitted page.

Question 7

How do you handle the ADA Title III and LEED v4.1 / WELL evidence trail design teams have to produce?

Accepted Answer

The BIM model is the source of truth. We run automated checks against ADA Title III dimensional requirements (clear floor space, turning radius, reach ranges, threshold heights, ramp slopes) on IFC geometry, and against LEED v4.1 BD+C credit pre-requisites (daylight, low-emitting materials documentation, water-use reduction baselines). Failing checks generate an issue in BIM Collaborate Pro or ACC Issues so the design team works inside their existing tool, with a COBie 2.4 export feeding the operations handover at substantial completion.

Question 8

Why not just use Procore Copilot or the native Autodesk AI features — what do you add?

Accepted Answer

Vendor AI is broad and shared across customers; it cannot be tuned to your spec library, your prior RFI corpus, your standard-detail set or the way your project engineers actually answer. We build customer-tenant models on customer data inside the customer VPC, with retrieval over your historical projects (not a generic crawl) and explicit citation to your specs. We also span the seams between vendors — Procore for project management, ACC for design coordination, Bluebeam for markups, Sage 300 CRE for cost — which no single vendor copilot does.

Field-grade AI for GCs & Trades

What You Get

Inference Systems for Construction

RFI Auto-Triage (Procore + ACC)

Submittal Review Automation

Punch-List Image Recognition

Schedule-Risk Forecasting

Quantity Takeoff (IFC / Revit)

OSHA-Aware Safety Vision

Equipment-Utilisation Optimisation

Data Infrastructure Capabilities

BIM Pipeline: IFC4, COBie, Forge

Project Data Fabric: Procore, ACC, Sage 300 CRE

Field & Supply Chain Telemetry

Deployed in your VPC, not ours

Frequently Asked Questions