...
D2000 system defines the term structure as a particular number of named items, to which it is possible to specify the properties as a value type, start value, saving start value, limits. Structure in the system is defined by an object Structure definition, so a specific name is assigned to it. Structure definition (holds no value) represents a particular model, which is used (by in the form way of a reference) in the definition of other objects:
...
- Possibility of duplicate connection of objects: connection of one object into several rows of a structured variable (for the value type Object).
- Anonymous rows: individual rows of the structure are addressed by a numeric index. If the rows of one structured variable belong to several groups (e.g. each row corresponds to one generator and several generators create a block and several blocks create a power plant), this is not obvious when working with numerical indices and a mistake may occur.
- Memory fragmentation: structured variables are represented in the D2000 system as contiguous blocks of memory. When using large structures (tens to hundreds of rows and columns), memory fragmentation occurs (especially in the D2000 Server process).
- Archiving problems: when using structured archives (archiving a column or possibly an entire structured variable), all values are stored in one database table, which can be large and its maintenance (reorganization of data and indexes) can be demanding in terms of disk operations and CPU. At the same time, such a structured archive object is assigned to one write archive task, so that writes cannot be parallelized. If other archive objects (computed and/or statistical archives) are built on top of such an archive object, each of them is again handled by one write archive task. If e.g. a recalc of the archive by the RECALC tell command is started, it is serialized and performed sequentially for individual rows of the structured archive.
- Editing: a structured variable can only be edited by one user at a time.
These problems are solved by the device concept brought by the D2000 in version 21. The Device can be perceived as a one-line structured variable, whereby:
- The Device definition object defines the structure of the Device type object - it is a Structured device definition.
- The Device definition supports supports all types of columns such as Structure definition, in addition, columns of Internal item type (used to connect another D2000 object to the device) and Device (used to connect another device - subdevice).
- The Device definition can alternatively be defined as an array of objects with a defined Devices that are of another Device Definition type - this is an Array device definition (e.g. let's have DD.Generator and DD.GeneratorArr derived from it).
- It is thus possible to build a "tree" of devices, while the D2000 Server process ensures a consistent naming convention for objects connected to the device items of Internal item and Device type.
Thus, in principle, the concept of devices allows the creation of tree structures with the provision of a uniform naming convention of the objects from which the trees are created.
For each column (item) at the level of an object of Device definition it is possible to define the following attributes:
...
* Attribute is defined at the level of the object of Device definition type and cannot be changed.
You can create template schemes, template eval tags, and template archives for devices. All of these object types are configured using a Device definition. Using the template pictures, the Device with the corresponding Device definition can then be displayed. Configuring template eval tags and template archives will cause instances of these objects, i.e. eval tags and archived objects for each Device with the relevant Device definition, to be created.