A rule is defined as a boolean logical Value, beeing either TRUE (1) or FALSE (0). Rules are therefore the central component of active funtional specifications. With the help of rules funtions of facilities at each time step is defined. If every rule applies correctly, then the operation meets the designed specification. The result of a rule is available as a virtual Sensor in the PTB.
Each Rule (or Function) will be opened and defined in its own editor window. The desired sensors can directly be connected from the work space via drag & drop. Each sensor is then allocated with a reference variable ( I1, I2,…). These variable is used within the mathematical description. If you are within a stage of a project where no data is connected to a sensor you can already include identifiers by clicking “add”. The rule will only be calculated as soon as all data points are connected to the every used identifier within each rule. For the defintion of each rule the following language is used. Furthermore each rule can contain Functions, Constants, Characterisics, Time Routines and Metrics can be used but each term within a rule must result in eaither TRUE or FALSE.
It should be noticed that each term has to have one component which contains a time-stamp.
The time routine timeroutine_1 is defined.
I1 in this example is the outdoor air temperatur, which also could be any other data point.
The rule shoud result in a TRUE value as long as the time routine is valid. Here the definition is:
path.xyz.timeroutine_1 && I1 == I1
This rule is always TRUE because I1 is equal to TRUE if the time routine is valid.