Decision acceptance deadline

07.10.26 (inclusive)

Form of award

Contractual

Product status

MVP

Task type

R&D Tasks

Сфера применения

Robotics

Область задачи

Neurotechnology and artificial Intelligence

Type of product

Software/ IS

Problem description

Estimates and acts often contain aggregated items without element identifiers. Linking only to the floor or type of work does not allow you to check which specific elements and volumes are taken into account, exclude duplicates and restore the calculation after changing the model.

Expected effect

Прототип учёта проектных, заявленных и принятых объёмов с проверяемой трассировкой до конечных элементов. Измерить точность сопоставления, долю объёмов с подтверждённой привязкой к ID, расхождения итогов, выявленные дубли и время сверки.

Full name of responsible person

Ormanov Marat

Purpose and description of task (project)

To investigate the recognition of estimates and acts of completed work and the comparison of their lines with the final BIM elements by area, type of work and volume. Create a prototype with two-way tracing: document and its version → line → type of work → Element ID and model version. For each relationship, save the quantity, unit of measurement, completion status, and matching basis. Select related elements in 3D by line of the document, and show the source lines and counted volumes by element. Maintain "many to many" connections, partial implementation, and the history of adjustments to documents and models.

Note

Stages and results of work 1. Data preparation · 1 week: The customer submits a BIM model, estimates and certificates for the selected type of work, as well as examples of correct binding. The customer and the developer agree on units of measurement, volume distribution rules, and acceptance criteria. Result: a set of data and prototype requirements. 2. Prototype development · 2-3 weeks: The developer creates a service that links the lines of estimates and acts with the final elements of the model and distributes the volumes. For each relationship, the document, row, element, and quantity are visible; ambiguous cases are passed on to the specialist. The result: a prototype with a transition from the document to the model elements and back. 3. Testing and refinement · 1-2 weeks: The customer's specialists check the binding and volumes. The developer measures accuracy, verifies partial completion, re-upload, and correction of acts, fixes errors, and fixes restrictions. Result: a proven prototype and test report. The architecture and methodology are discussed with the specific contractor.