Internals
On correct terminology practically applied
For the mutual mapping concept a special terminology is used.
However, since dia$par is intended for a wide range of business users, this terminology comprises well known notions like "documents", "results", "reports", etc.
Though, the familiarity with terms used in dia$par should not mislead.
The meaning of these terms is much wider in the context of dia$par.
Some key notions regarding the managing meta-system are presented below.
Terminology of mutual mapping
mchain
Meaning in mutual mapping
The process within the enterprise cybernetic model which is determined by all possible changes pertaining to this process.
Business meaning
The value chain notion is used in its traditional meaning.
dia$par.Matrix source code
"document type"
mstep
A basic feature of an individual change determining the current status of the delta of the process.
A value chain stage is also used in its common meaning.
"document subtype"
mpack
It is a structured minimal and sufficient package of changes in measurable indicators for the cybernetic model for a specific process.
It is a small container unit of logically connected objects (that can be empty as well) which are moving along the value chain (mchain), through its stages (msteps), and transforming their nature up to becoming objects of another nature. These objects are a raw material at the input of the value chain and finished products at its output (from the local value chain point of view). An mpack can contain any amount of information about any objects which are simulated in the dia$par.Matrix cybernetic model. Likewise, the rules of business logic applied to mpacks at every stage (mstep) of the value chain (mchain) can use values of any parameters and features of cybernetic model objects. A shipping list is a primitive example of the mpack (hence the name of dia$par has been chosen).
"document"
mface
The hyper-plain is a projection of the cybernetic model in a space with a less number of dimensions.
The mface is a sample container containing the current values of a random number of numeric parameters of an individual section of the cybernetic model along with the history of their evolution. The number of mfaces which the cybernetic model can run simultaneously is theoretically unlimited. The population of mfaces of the cybernetic model contains all up-to-date data about the state of all enterprise parameters measured in real time.
"total"
equant
It is a structured atomic package of changes for one or two mfaces representing the delta of the state which is set by the mface.
It is a quantum of the state of the cybernetic model. They are generated by traflexes (they are kind of conditioned reflexes of mutual mapping, please see below). An accounting transaction is a primitive example of equant.
"transaction"
xface
It's random relational algebra functions projecting a subset of the model into the calculated hyper-surface.
Aggregated data sets generated by low-level tools of mmizer by inquiry from developers applying data transformation techniques for a random number of basic mfaces. They are used in certain situations.
"complex total"
mflex
Functions to completely transform the state of the model.
Mutual mapping prescribes eight types of model responses which are similar to reflexes of a biological organism. It's interesting that all mutual mapping reflexes are, on the one hand, conditioned, i.e. they can be (and are expected to be) changed. At the same time, they are unconditioned. Because, from the point of view of the current model layout, these reflexes are 'inherent'. In other words, they were embedded by the programmer 'Creator' at the time this very model layout emerged.
"script"
deflex
On-DEmand mFLEX.
It's the model response to actions performed by a human user using visual interfaces of dia$par client applications.
"command"
sheflex
SHEduled self-executing mFLEX.
The model's response to regular events.
"task"
oflex
From the Outside calling mFLEX.
The model's response to inquiries from external cybernetic systems transmitted via digital interfaces (which are mainly web services and binary protocols).
"webservice"
speflex
SPEcified mFLEX.
A particular model's response to changes in the mpack state which depends on the mchain and mstep within which the changing mpack is located.
"event handler"
baflex
BAsic mFLEX.
An unconditioned model's response to random changes.
"common event handler"
traflex
TRAnsaction mFLEX.
The model's response to removing an mpack to another mstep (mchain) which describes the process of structuring and data projecting for the removing mpack container into a set of mfaces.
"transaction script"
rflex
Remotely executable mFLEX.
The model's responses are carried out by meta-system duplex effectors through different client applications, as well as unmanned dia$par functions which operate manufacturing equipment.
"client script"
Mfaces and mpacks in their totality are similar to computer's RAM memory and its hard drive.
The data loaded into RAM to some extent duplicates the data stored on the hard drive, but RAM memory is intended to provide the CPU with data in real time. The data stored on the hard drive is much more exhaustive, while the access time is not that critical for it.
If different access time for data stored in RAM and on a hard drive results from a structural differences of the two devices, in case of dia$par the difference between mfaces and mpacks is determined by different data packing methods (the starlike data storage model).
Mface analytic sections can be generated in any amount based on any data set from the cybernetic model, but in practice mfaces are usually based on actively used facilities of the enterprise or groups of counterparties.
An mface has its own structure, measures and indicators of any complexity in terms of their number.
For example, an mface with data on warehouse capacity usually has two indicators — the physical capacity (in items, kilograms, liters...) and capacity in terms of money.
Thus, any equant is measured within such mface in terms of both its quantity and cost, otherwise it will just not be replicated by the mmizer.
Now the mutual mapping terminology is recommended to be used by both dia$par integrators in their descriptions of target models and process engineers of companies dealing with changes in value chains.
