Storing objects in a tabular format

[shamimhasan07]

Building information modeling technology (BIM) has become a de facto standard in the design of civil facilities and discrete manufacturing enterprises - mechanical engineering, instrument making, light industry, etc. In these areas, the use of classical BIM approaches is more than justified, since the objects are primarily buildings, and production differs from housing only in the amount of equipment and often less detailed architectural solutions.

Complex, rich patterns
Continuous-cycle enterprises — oil and gas, chemical and petrochemical industries, nuclear and phone number search philippines thermal power engineering, metallurgy and mining — differ significantly from discrete industries. It is the technological solutions (equipment, installations and pipelines) that come first here, while buildings and architecture may be completely absent — for example, in the petrochemical industry. Such projects are characterized by very complex and rich models of technological objects — non-standard/non-standard equipment, long pipelines with a large number of pipeline elements and supports, as well as auxiliary structures. Widely used BIM programs (for example, Autodesk Revit, nanoCAD, etc.) are a stretch to solve the design problems of such objects; Plant Design class solutions are used here. Such solutions appeared back in the 80s and have been actively used by many large industrial customers in Russia in recent years.


A distinctive feature of Plant Design systems is the "object-oriented" approach to storing model data. Due to the large size of the project, the huge number of elements and their high level of detail, it is not possible to store such models using traditional geometric kernels. Plant Design systems use catalogs of process plant components and store parameterized objects of the 3D model in a regular database or even XML files (usually both approaches are used simultaneously). The rejection of geometric primitives and curves makes it much easier to work with models, reduces the volume of stored data, and makes it possible to work with this data outside the graphics engine and in different design systems. In addition, it is easier to create 2D drawings and specifications from such models.

"Another feature of Plant Design is the creation of "intelligent" diagrams and drawings (primarily process diagrams). The "intelligence" of such diagrams implies a natural and simple search for objects in diagrams by the name of the object ("pump No. 25") or the object tag formalized in accordance with the classifier - its unique identifier. The object tag is used in "intelligent" diagrams, and in three-dimensional models, and in the common data environment (CDE). "Intelligent" today can be process diagrams (P&ID diagrams), electrical diagrams, instrumentation diagrams, isometric drawings and, so far quite rarely, orthogonal drawings" - OOO "PlantLinker"

The common data environment in Plant Design class solutions is called the Engineering Data Management System — EDMS (also SUPRID). It is similar to mechanical engineering PDM/PLM systems, but supports different parallel structures. Various viewers are used to view models, capable of visualizing tabular data from XML or DB.

Import Substitution Tool - PlantLinker CAD
Until 2022, there were no Plant Design class systems on the Russian CAD market that would allow modeling industrial facilities for continuous-cycle enterprises. Design organizations were forced to purchase Western solutions, usually Intergraph Smart3D and AVEVA PDMS/E3D. After foreign development companies began to leave the Russian market, there was an urgent need for a solution that could completely replace them and meet a number of requirements: modeling, documentation release, integration with existing IT systems, ease of licensing and management. Domestic developers are trying to implement this request, primarily by saturating existing products with the necessary functionality. The first and so far the only Russian Plant Design class CAD system was the PlantLinker complex ․