Inheritance principles - for your growing energy management
The inheritance principle is based on the desire to simplify the editing of settings that have already been made.
The same settings are managed centrally and automatically passed on to lower levels. Your advantage: You make both the original settings and later changes in one place. Therefore, such central settings are valid until a new setting is made at a lower level or the existing one is changed.
Like a tree
Your real meter and building structure is represented in the system in the form of a reversed tree structure. Starting from a root element located at the top, all other buildings below are treated as branches, to which other branches can branch. This tree structure forms the basis for the inheritance principle: Settings made at the top of the trunk are usually passed on to all subsequent branches until a new, separate definition is made there. This definition is then inherited downwards in the own branch.
No matter how large the tree grows over the years, the amount of maintenance you need remains low.
The effects of inheritance
Inheritance initially means that you do not have to make general settings for each individual object. You also have the advantage that you can define exceptions to a defined "rule". For example, this is helpful when setting user rights. This allows you to define the visible area as far as possible from the root and a specific set of rights for a user. At the same time it is possible to withdraw or assign rights for certain elements successively downwards.
The inheritance principle applies to user calculations, report and evaluation templates as well as extended settings (e.g. start of fiscal year, public holiday calendar, sorting, reference value, etc.).
The central management of the reference period is illustrative: when the system is set up, it is often clear which reference period should apply to the monthly energy reports, as these depend on a specification. It is now possible in IngSoft InterWatt to centrally define and maintain this reference period at the highest hierarchical level (organizational unit). It then initially applies to all energy properties under this organizational unit. Unless there is a new reference period for a particular property due to a new construction - in this case an exception can be defined for this. The inheritance principle still applies to all others.
Long story short
|The reference period is defined...||Advantage||Disadvatage|
|Central, valid for all objects||No unintended deviations, easy to change centrally||No exceptions possible (e.g. for new buildings)|
|Individually for each object||Individually for each object||Errors likely, subsequent modification very complicated|
Central, inherited / may be overwritten (The solution in IngSoft InterWatt by inheritance!)
|Can be maintained centrally and individual deviations are still possible||none|
What's in it for you?
While the inheritance principle is of little importance in smaller applications, it is a great help even with a handful of objects. Scenarios with a large number of buildings can only be handled in energy management without such mechanisms as long as there are no subsequent changes. The latter is unrealistic. Therefore, IngSoft InterWatt offers you a solution that makes your application easier, saves annoying click work and reduces possible sources of error.