Instead of the traditional scheme, when the terms of reference are formed from text blocks, an object-oriented approach is applied to create Technical specifications of construction sites. All sections of the terms of reference are formed from structured "objects" and an exhaustive set of "parameters" that this object may possess. Such structuring makes it possible to make transparent both the set of information contained in the document and to make the process of task formation itself manageable.

Data — management of objects and their parameters at the directory level

Processes — managing TK administration, document versioning, merging versions and branches.

Separately, you need to pay attention to three local innovations:

  • Working with branches, merging different versions of TK. The prototype here was the Git solution, when various code branches and versions merge into the repository. Similarly, in the CTP, different versions and sections are merged into one document, and all this is done in a mode controlled by the project manager.
  • Fixing the links between sections — there may be a technical or product error in the design, when one section has introduced an important point, and the other has not been notified about it. To avoid such collisions, communication between partitions and notification can be set up in case of changes in important parameters affecting the neighboring partition.
  • The division into templates/projects is more of a management technique, it makes it possible to centrally accumulate the positive experience of the entire company in templates, and then copy it into specific projects.

The technical task management process, which was not previously covered by digitalization, is being closed. This process is very important both from the point of view of cost, because it directly affects the design process (direct costs of 1.5-3% of the construction cost) and indirectly affects the process of managing materials and equipment (indirect impact of up to 20-40% of the difference in the cost of different options for one position), additionally the process of preparation and approval of technical specifications It affects the calendar schedule of the project and the formation of the qualitative characteristics of the CTP product allows for the transfer of non-formalized knowledge, which is contained "in the minds" of the most valuable specialists, into a digital format. To preserve this knowledge and reuse it on subsequent projects, which is especially valuable when there is a shortage of personnel in the market. An example of the complexity of such systems is the fact that only the trial operation of the system lasted almost a year, during which (based on feedback) improvements and product improvements were made.

All projects begin with a technical specification, and project requirements are a lever that has a multiplicative effect on all subsequent stages. Oddly enough, the industry starts digitizing this stage quite late (this is a consequence of patchwork digitalization). CTZ, as the first full-fledged An IT solution for managing requirements in design closes an important process and brings best practices from management to IT, to development. We do not multiply the pool of existing solutions from more commercially attractive segments with a high receipt, the solution is made for a complex target audience: engineers, designers, technical customers, consumers, who have very high requirements.

We use cookies to improve the operation of the website and its interaction with users. By continuing to use the site, you allow the use of cookies and agree to the cookie policy. You can always disable cookies in your browser settings.

Accept