Hydraulic Calculations

A substantial portion of the same data needed for solving different tasks by different programs. A simple example – the length of any particular section of pipeline thermal network. This value should be: for the calculation of hydraulic calculation of heat loss, accounting for depreciation accounting for accounting and planning of planning preventive maintenance, to determine the buffer zone, logging and dispatching orders etc. If the solution of each of these tasks using a separate program (and it is, usually is), then the length of the site is stored in a data format of each of these programs – that is, many times, how many programs use this value. Change the value of the length of a site-specific pipeline within the data set one of the programs does not affect this value in all the other data sets. It is clear that very soon there comes a complete mismatch of data on the same object in different sets, and oversee this process is quite impossible. This kind of "multipurpose" data about objects of any of engineering communications – at least hundreds, perhaps thousands. In such circumstances, meaningless to talk about any reliability data arrays.

Based on information received technical and management solutions. Decisions adopted on the basis of erroneous or inaccurate information, as generally ineffective, but that is much worse – in a complex engineering system, they could be disastrous. The same, of course, applies to "paper" information. Information about the same objects stored "in Wardrobe different services businesses tend to suffer even greater degree of mismatch.