TIM · BIM · Estimate
Larix.Manager validates the model, Larix.EST calculates volumes and costs using the Larix.CDB classifier, and Larix.Tender and Larix.Contract handle bidding and contracting. We don't sell or implement Larix — we route its data to 1C.
Start with the classifier: without Larix.CDB's corporate work and rate handbook, Larix.EST can't calculate volumes. The bill of quantities itself comes from the model or the designer's specification — if there's no model yet or it's incomplete, that's standard procedure, not an emergency fallback.
Our clients
Capabilities
Proprietary clash algorithm (7 types of checks) and automatic element parameter validation in IFC, Revit, Renga, and Bentley. Reports in Excel and Power BI, data access via API. This module does not calculate volumes and cost — that's Larix.EST.
Automatically generates bill of quantities and cost of works from Revit, IFC, or Renga models using the Larix.CDB corporate classifier — per vendor data, instead of weeks of manual recalculation.
When there's no BIM model yet or it's incomplete, Larix.EST accepts designer specification data from Excel and treats it as model elements — per the vendor's FAQ, this is standard procedure, not an exception.
Maintains a registry of work types, resources and costs by period and region — reference data required for Larix.EST to calculate anything. The classifier is passed to Larix.EST as the rate source.
Lot formation, tender distribution to contractors, collection and comparison of commercial proposals, winner selection protocol — the complete procurement cycle in one module.
Contract and amendment management, contractor accreditation, volume control per contract, automated generation of cost change orders (KS-2, KS-3, KS-6) — digital document workflow instead of paper.
A single data hub moving information between Manager, EST, CDB, Tender, and Contract — no manual reassembly at each module junction.
Per the vendor's own FAQ, Larix.CDB and Larix.EST do not replace estimating software: the bill of quantities with work codes and descriptions goes downstream to GRAND-Smeta, 1C:Smeta TIM, or equivalent for FER/TER/GESN-based calculation.
Approach
The customer or Aibim partner selects and deploys the platform. KT.Team works with what's already in place and does not replace the vendor.
We route exports from Larix.EST and Larix.CDB to 1C via the integration bus and API without modifying the core product.
Each developer has a unique accounting landscape. We break down the data flow from Larix through estimating, procurement, and 1C on this page integrating TIM/BIM with 1C, and the full scope of developer tasks is in the development digitalization. If the model is already consistently populated and there's no need to create a classifier — comparing with Tangl.
AI compatibility
The bill of quantities from Larix.EST is classifier-bound data, not free text. KT.Team's AI estimator needs exactly this type of structured input to suggest line items and coefficients, not guess from PDFs.
Larix.Manager marks element statuses during model revalidation. Volume changes between versions can be tracked automatically if routed to the accounting system — that's already our integration layer, not Larix itself.
If Larix data passes through KT.Team's integration layer en route to an external model, contractor and counterparty personal data can be anonymized before transmission and restored in the response at that same layer.
An MCP wrapper over Larix.EST and Larix.Manager APIs allows the agent to read validation status and volumes without replacing the estimator's interface or modifying the core product.
Honestly
Projects
