You can create rules which can check between all logical (Yes/No) and numerical (digits) fields in RDS and the Item specification. The type is automatically determined when you choose the fields between which you want to set up the rule. Table 1 illustrates the correlation between field type and the type of rules which can be created.
RDS field: | Item field: | Can be counted down: | Result: |
Logical | Logical | No | Under-specified
If the Item field is "Yes", the RDS field must also be "Yes".
Example: If the Item is flagged for vacuum, the RDS field "vacuum" must also be flagged.
Over-specified:
If there are no Item in the room with the "Yes" field, neither shall the RDS field have "Yes".
Example: If no Item in the room require vacuum, the RDS field "vacuum" shall not be flagged. |
Numerical | Logical | Yes | Under-specified
The RDS field must be equal to or greater than the number of Item in the room where the Item field is flagged.
Example: If the Item is flagged for power supply, the number of sockets in the room must be greater than or equal to the total of all these Item which require power supply.
Over-specified:
The RDS field must not be greater than the number of Item in the room where the Item field is flagged.
Example: The number of power sockets in the room must not be greater than the number of Item which require power. |
Logical | Numerical | No | Under-specified
If an Item in the room has a field greater than 0, the RDS field must be flagged.
Over-specified:
If no Item in the room has a field greater than 0, the RDS field must not be flagged. |
Numerical | Numerical | No | Under-specified
You can choose an operator with which to compare values. If you choose '>', the value of the Item field must be greater than or equal to the value in the RDS field. If you choose the '<' operator, the Item field must be less than or equal to the RDS field.
Example: The minimum temperature for the Item must be greater than or equal to the minimum temperature in the room.
Over-specified:
Reverse the operator selected (for under-specified).
For example: The minimum temperature for the Item must not be less than the minimum temperature in the room.
Check whether over-specified for this type of rule actually has any practical significance. |
Numerical | Numerical | Yes | Under-specified
The sum of the Item field for all Items in the room must be less than or equal to the value in the RDS field.
Example: The number of data connections for all Item in the room must be less than or equal to the number of data outlets in the room.
Over-specified:
The value in the RDS field must not be greater than the total of the Item field for all Items in the room.
For example: The number of data connections for all Items in the room must not be greater than the number of data outlets in the room. |
Table 1
Go to Project-> RDSto Home → Rooms → Room Data<-> Item check to to create and delete rules. This provides you with an overview of all rules defined. Click on "Add" to add a rule. There is a tree on the left-hand side of the screen with all the RDS fields and one on the right-hand side with all the Item fields. Choose one field in each of these by double-clicking on the field you want. Depending on the type of field you have selected, you will have options as to whether the resource is to be counted down and the operator you want to use. Once you have completed defining the rule, its definition will be shown in the text fields for under-specified and over-specified respectively. You then select a priority and click OK.If you want to delete a rule, select the rule and click Delete.
Image Added
