TIM · BIM · Estimate

Tangl (Value, Control): volumes directly from IFC — and when Larix is needed instead

Tangl Value calculates volumes, work breakdown structure, and cost indices directly from the IFC model, while Tangl Control verifies the federated model for clashes — both without a classifier inside the project file. We don't sell or implement Tangl — we integrate its data to estimate and 1C.

Tangl requires a well-populated model: without it, Tangl Value won't calculate volumes and Tangl Control has nothing to verify. If working documentation is in 2D or the technical information model is maintained formally for approvals — that's not Tangl's scenario. Larix.EST is better then, which calculates volumes from both the model and designer specification in Excel when there's no model yet.

Our clients

Clients and partners

Capital Group
FSK Group
SMLT
Tochno
Dogma
Sber City
FM Logistic
Danone
Relief Center
Pandora
Tangl or Larix: What to Choose for Your BIM Model
Saint-Gobain
Askona
FIX PRICE
Snezhnaia Koroleva
Muztorg
TVOE
Greenway
Polaris
Campari
Yandex
Lenta
International perfume and cosmetics brand
Tangl or Larix: What to Choose for Your BIM Model
RAEC
EKF
L'Etoile
Inventive Retail Group
ROI growth for the estimating department per project — per Tangl Value data
85%work volumes can be extracted from the TIM model — Ak Bars Dom case
14×less labor to check the model — per Tangl Control data
MinDigital registryTangl is registered in the domestic software registry — according to tangl.cloud

Selection

Larix or Tangl: which to choose

CriterionLarixTangl
Source of quantitiesLarix.EST — by model (Revit/IFC/Renga) or by designer specification in Excel if no model yetTangl Value — model only (IFC/Revit), no fallback to specification
Classifier — inside the modelRequired — Larix.CDB codes are entered in the modelNot required — per vendor FAQ, classification codes are not entered into design programs
Working documentation still in 2DWorks — Larix.EST accepts the designer's specification as a standard scenarioDoesn't work — Tangl calculates only from a properly populated model
Tenders and contractsYes — Larix.Tender and Larix.Contract, CIS software registry #14076Tangl's product line has no procurement and contracting module
Result destinationTo GRAND-Smeta, 1C:Smeta TIM CORP or equivalent — a volume schedule is not an estimate in itselfTo Excel and estimating software via export — integration with 1C is built separately by the customer (TDSK case)

Capabilities

Tangl capabilities

Model (IFC / Revit)Tangl Value — volumes, work breakdown structure, cost indicesTangl Control — model verificationExcel / estimating software1C — estimate and accounting layer (our seam)
Data comes from the IFC model — without intermediate specification, unlike Larix. Tangl Value calculates volumes, resource schedules, and TEP from it, while Tangl Control simultaneously checks the model for clashes and parameter completeness. The result exports to Excel and estimating software. Then the product boundary begins: Tangl does not handle tenders, contracts, or 1C entries — KT.Team designs and delivers this integration to 1C.

Tangl Value — volumes, work breakdown structure, and cost indices from IFC

Calculates volumes, resource schedules, estimate line items, and technical and economic indicators directly from the model in open IFC format — per vendor data, 'volumes in minutes' at any project stage.

Classifier — not in model

Per vendor FAQ, Tangl's approach 'eliminates the need to work with classification codes in design programs' — unlike Larix.CDB, codes are not entered into model elements in Revit or IFC.

Tangl Control — federated model verification

Automatically checks geometric clashes, information completeness, and compliance with product and regulatory requirements, covering up to 90% of EIR checks per vendor data; reports accumulate by model version.

Export and open API

Calculation and export of schedules to Excel with integration to estimating software and external ERP; an open API synchronizes Tangl with Revit, 1C, and Pragmacore — per vendor data.

No tenders or contracts

Tangl's product line (Space, System, Control, Value, SDK) has no procurement or contracting module — the procurement cycle remains outside Tangl.

Model required

Tangl calculates from the model, not specification: if there's no model yet or working documentation is in 2D, Tangl Value and Tangl Control won't provide volumes.

Approach

How Tangl data reaches the estimate and 1C

We don't sell or implement Tangl

The customer selects and deploys the platform. KT.Team works with what's already in place and doesn't substitute for the vendor.

The market already shows this integration point

TDSK (Tyumen Construction Company) piloted Tangl Value from March 2022: the generated works volume statement was uploaded to 1C. Source: ComNews, 29.05.2024, comnews.ru/content/233431.

Integration from model to estimate and 1C is our work

Tangl exports volumes to Excel and estimating software; connecting this export to the customer's estimate and accounting system is separate work, discussed on this page integrating TIM/BIM with 1C, and the full scope of developer tasks is in the development digitalization. When you don't have a model yet or it's too early to implement a classifier — comparison with Larix.

AI compatibility

Tangl in the AI workflow

Structured input for the AI estimator

The volume schedule from Tangl Value is tied to the model, not formatted as free text — this is exactly the input KT.Team's AI estimator needs to suggest line items and coefficients instead of parsing PDFs.

Model versions without manual reconciliation

Tangl Control stores verification reports by model version. Volume deltas between versions can be tracked automatically if connected to the accounting system — that's our integration workflow, not Tangl itself.

Anonymization in the LLM pipeline

If Tangl data passes through KT.Team's integration layer on its way to an external model, contractor and counterparty personal data can be anonymized before transmission and restored on return at that same layer.

Agent on top of open API

Tangl has an open API for synchronization with Revit, 1C, and Pragmacore — according to the vendor. An MCP wrapper reads volumes and verification status without replacing the estimator interface or modifying the product core.

Honestly

Pros and cons

Pros

  • Volumes are calculated directly from the model in open IFC without transferring classification codes to design programs — per vendor FAQ
  • An open API synchronizes Tangl with Revit, 1C, and Pragmacore without proprietary formats
  • Registered in the CIS software registry — per tangl.cloud data
  • Tangl Control covers, according to the vendor, up to 90% of EIR checks and stores model version history

Cons

  • Works only with a model: without it or with 2D working drawings, Tangl Value and Tangl Control won't produce volumes — you need Larix.EST with the designer's specification here
  • Tenders and contracts are not included — procurement workflow remains a separate task
  • A volume schedule and Excel export are not a finished estimate: calculation by FER/TER/GESN is performed by a separate system
  • Integration with the customer's accounting system must be designed separately each time — the vendor doesn't provide a connector to an arbitrary 1C configuration

Projects

Cases

All cases

Discuss Tangl (Value, Control): volumes straight from IFC — and…

Send via: