Metis Smart Modeling - Rules

In the Metis environment, a rule is a determinate method for performing a logical or mathematical operation and obtaining a certain result which is  the building block of the modeling part (configurator). It is based on a simple structure and logic which can be used in an endless number of cases and will suit most of the requirements for material and service configuration.  

Link to the execution process of models.

Once the rule has been saved, the ID field will automatically be completed by Metis Smart Modeling. The generated identification code is unique worldwide and can be useful for searching for a rule or debugging it, if necessary. (mandatory, but generated automatically upon validation)

A long description ca be given to all rules defined within Metis Smart Modeling.

If this checkbox is ticked, any fractions of output resulting from a rule will not be taken into account. This means that the result will only be composed of whole units. This applies in particular when using a formula based rule.

Mandatory Controls, simply by the presence of a system name, are considered to be applied on the offer level. The influence in Metis Smart Quotes is that it will still be possible to view and print offer documents for the Metis Smart Quotes end user until an external configurator control can be performed. There is no icon to represent the Mandatory Control applied on the offer level.

Mandatory Controls, simply by the presence of a system name, are considered to be applied on the order level. The influence in Metis Smart Quotes is that the ordering process will be blocked for the Metis Smart Quotes end user until an external configurator control can be performed, but it will still be possible to view and print offer documents. There is no icon to represent the Mandatory Control applied on the order level.

Mandatory Control intended for systems which do not have system names. They require Metis Smart Quotes end users to perform a mandatory control of system configuration. The mandatory controls of systems will have to be performed manually by an especially authorized user as opposed to being handled by an external configurator control like Mandatory Control. Will be applied on the offer level. It is basically the same as the Mandatory Internal Control (Order) with the added restriction that it will not be possible for the end user to view and print offer documents.

Mandatory Controls intended for systems which do not have system names. Similar to the above Mandatory Control, they also require Metis Smart Quotes end users to perform a mandatory control of system configuration. The mandatory controls of systems will have to be performed manually by an specifically authorized user as opposed to being handled by an external configurator control like White Flags. Will be applied on the order level, meaning that the ordering process will be blocked for the Metis Smart Quotes end user until a manual control can be performed. It will still be possible for the end user to view and print offer documents, however.

| Whether the Grey Flag has been placed on the order level or offer level, there will be no difference in the display in QSBW. The same small yellow icon will be displayed for either one.

| Only one type of Grey Flag can be active on a rule at a time.

| The White Flag (Offer) and a Grey Flag can be active on the same rule at the same time. However, Grey Flags will not have any influence on a system which has a system name. Systems which have a system name will only take into account whether or not the White Flag (Offer) has been applied. Conversely, the White Flag (Offer) setting will have no influence on systems which do not have a system name.

| When specifying output, you will only have the choice between “Product” and “Variable”, as it is not possible to set the value of a [[Metis_Smart_Modeling_-_Variables|group of variables]] or an [[Description_of_the_Menu_Attributes|attribute]].

4. '''Add-On's'''' : Based on the result provide by the Formula part, a rule can be set-up to add implied positions or define new values in [[Metis_Smart_Modeling_-_Variables|variables]]. Additional results from the rule based on the result of the "formula"

| When specifying output, you will only have the choice between “Product” and “Variable”, as it is not possible to set the value of a [[Metis_Smart_Modeling_-_Variables|group of variables]] or an [[Description_of_the_Menu_Attributes|attribute]].

'''Attributes'''

(input only) [[Description_of_the_Menu_Attributes|attributes]] values added over the complete offer can be used as input for rules

The value set in this field will define the lower limit for which the rule is valid and should be executed. For example, if the "Q in" value is 6 and that the "Q from" value is 5, then the rule will provide an output. The "Q from" value can also be considered as a base value for the system in which the model is used.

The value set in this field will define the upper limit for which the rule is valid and should be executed. For example, if the "Q in" value is 6 and that the "Q to" value is 4, then the rule will not provide an output.

| [[Description_of_the_Menu_Attributes|Attributes]] do not hold any values in material models.

The single selection rule tests an input and calculates the defined output based on a simple logical relation. The Input "object" can be of any type available, but the output one can only be a position or a variable. If the input is set to be a variable, its value may come directly from a field placed in a mask or a default value. The output quantity ("Q out") is determined by the input quantity ("Q in"). If they are both set to "1", then for every number of input there will be an output. On the other hand, if the "Q out" fields is set to 2, it means that for every input there will be 2 output.

| Beware that if the "Q in" field is left empty, the output will be equal to the input. The output value will always be equal to the input value, for any “Q in” value.

| If the “Q from” field is left empty, this means ‘from 0'. If the “Q to” field is left empty, this means “up to ∞” (or > 999'999'999).

Click on add. A window opens where the new rule will be created.

The goal of this example rule is to generate the number of memory modules required based on the desired quantity of memory provided in a mask.

Click on the add button near the “input” field. A window opens where it is possible to select positions, [[Metis_Smart_Modeling_-_Variables|variables]], and attributes. Select “[[Metis_Smart_Modeling_-_Variables|variables]]”.

In the field “Q in” enter the value “1.”

In this example the result value is also “4” because “Q in” and “Q out” were both set to“1.”

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q in

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

| <mediaplayer width='400' height='300'>File:Creating_a_single_rule_OK.mp4</mediaplayer>

The goal is to determine an output quantity within several ranges of input values. The rule allows to enter several 'Q from' and 'Q to' to determine those ranges. They each then induce a specific 'Q out' which will be used as a quantity for the output.

To create a new rule, first select an existing group of rules from the drop down list. For example, “s-basic enhancements.”

Then click on the “Add” button. A window opens where the rule will be created.

Then, an output quantity will depend upon an input value entered in a mask.

Click on the “add” button for the “filter” section.

A new window opens. It is possible to add positions, [[Metis_Smart_Modeling_-_Variables|variables]] or attributes. Select “[[Metis_Smart_Modeling_-_Variables|variables]]”.

The purpose of this rule is to determine which RAID configuration will be setup in the system based on the selection done in a mask.

To do so, click on the “add” button for the “Input” section.

Click on the “add” button for the “output” section.

The requirement for this rule is that for a RAID configuration with a value of 0 or 1, the number of disks must be 2, hence why “Q out” is set to 2. With a value anywhere from 2 to 10, the number of disks must be 3, hence “Q out” is set to 3.

Therefore, under the Q fields, in the first field, Set “Q from” to “0,” “Q to” to “1” and “Q out” to “2.”

In the second field, set “Q from” to “2,” “Q to” to “10,” and “Q out” to “3.”

Please note, that although it is not displayed the value “0” for “Q from” has indeed been saved.

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q from

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q to

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

| <mediaplayer width='400' height='300'>File:Creating_a_Table_Rule_OK.mp4</mediaplayer>

Click on add. A window opens where the new rule will be created.

Click on the add button near the “input” field. A window opens where it is possible to select positions, [[Metis_Smart_Modeling_-_Variables|variables]], and attributes. Select “[[Metis_Smart_Modeling_-_Variables|variables]]”.

Click on the add button near the “Q in” field. The same window from before opens, but it is only possible to select positions or [[Metis_Smart_Modeling_-_Variables|variables]]. In this example a position is added.

In “Q in” field for “Windows Server 2008 CAL 5x” set the value to “5.”

Click on the add button near “Q in” once again.

Enter “25” in the “Q in” field for “Windows Server 2008 CAL 25x”

The rule now states that based on the number of licences, various solutions are possible. When executed, the rule looks up the prices of the various outputs to determine the cheapest and most suitable option.

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q in

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

| <mediaplayer width='400' height='300'>File:Creating_an_optimal_rule_OK.mp4‎</mediaplayer>

This type of rule can be used when several input values influence a specific output. Each line will be used as a single criterion and Metis will return the highest result possible. It is particularly useful when the goal is to define a minimal number of one position in order to satisfy several criteria. When the input quantity is not within the indicated range (Q from – Q to), the line will not be valid, thus not considered by the rule.

Click on add. A window opens where the new rule will be created.

Click on the add button near the “input” field. A window opens where it is possible to select positions, [[Metis_Smart_Modeling_-_Variables|variables]], and attributes.  

Click on the add button near the “Output” field.

| If the “Q from” field is left empty, this means ‘from 0'. If the “Q to” field is left empty, this means “up to ∞” (or > 999'999'999).

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q in

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

| <mediaplayer width='400' height='300'>File:Creating_a_maximal_rule_OK.mp4</mediaplayer>

| If the “Q from” field is left empty, this means ‘from 0'. If the “Q to” field is left empty, this means “up to ∞” (or > 999'999'999).

On the left, in the “Groups of rules” dropdown list, select “Server Software 1.”

Click on add. A window opens where the new rule will be created.

In the “Type” field, select “Maximal” from the dropdown list. In the “comment” field, enter a name for the rule, for example “Determine number of MS licenses.”

Click on the add button near the “input” field. A window opens where it is possible to select positions, [[Metis_Smart_Modeling_-_Variables|variables]], and attributes.  

Click on the add button near the “Output” field.

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q in

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

Click on add. A window opens where the new rule will be created.

Click on the add button near the “input” field. A window opens where it is possible to select positions, [[Metis_Smart_Modeling_-_Variables|variables]], and attributes. Select “Attributes.”

Click on add again. Select “[[Metis_Smart_Modeling_-_Variables|variables]]”. Search for the [[Metis_Smart_Modeling_-_Variables|variable]] “$Shipping_Type.” Select it and click on confirm.

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q in

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

| <mediaplayer width='400' height='300'>File:Creating_a_formula_based_rule_OK.mp4</mediaplayer>

| width="20%" style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" |

| width="30%" style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" |

| width="50%" style="border-style: solid; border-color: grey; border-width: 0 0 1px 0" |

Click on add. A window opens where the new rule will be created.

Click on the add button near the “input” field. A window opens where it is possible to select positions, [[Metis_Smart_Modeling_-_Variables|variables]], and attributes. Select “Attributes.”

Click on the add button near the “Output” field. The same window from before opens, but it is only possible to select positions or [[Metis_Smart_Modeling_-_Variables|variables]]. In this example a position is added. Select “[[Metis_Smart_Modeling_-_Variables|variables]]”.

A window opens. Click on the add button. The “select a file…” window opens.

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q in

! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" | Q out

| <mediaplayer width='400' height='300'>File:Testing rules and groups of rules OK.mp4‎</mediaplayer>

| Testing rules and group of rules.

The first rule will determine the number of 1 GB modules required to suit his needs. For example the input is 4 GB and the result is 4 modules of 1 GB each. The situation would be more complicated if the user had chosen 8 GB and that the machine could only hold 4 modules in total. This means that the model requires a second rule to check the number of 1 GB module against the number of slots available. In the example of a input equal to 8, the resulting number of modules is 8. The second rule could then take this value and modify the result to 2 GB modules thus making it possible to be installed on the machine.

Because in this situation the second needs to have the result of the first one available in order to use it has an input it is necessary that second be placed in another group of rules which should be executed after the one containing the first rule.

| On the main rule screen, listing all rules within a single group, they can be sorted. This functionality is only a visual help for the user. Based on the execution scheme of models, sorting rule within a group doesn't have any effect on the result of the group. If rule need to be executed a sequential order, then they should be placed in sequential groups.

* '''ID'''

Search for a rule directly by entering its identification number.

* '''Comment'''

Search for a rule by entering the "Comment" (name) of a rule.

* '''Mandatory Control'''

Refine to search to rule which enforce mandatory controls.

 

By using the ADD button [[File:MetisSmartModelingAddButton.PNG|link=]] search for rules which contain a specific position, variable or attribute. Using the '''Used as''' options it is possible to refine how this object is used in the rule looked for. Either as a filter, an add-on value or as input or output values. In the case of objects being used in the rule itself, the application allows to specify exactly where it is used in the rule.

| If modifications are applied to a rule which is used in several groups, keep in mind that changes will be have an influence on all groups or models in which this rule is used. It may be relevant to make a copy of the rule in order to test the modifications.  

In the “Modeling” menu, make sure that the “Rules” sub-menu has been selected. On the left, in the “Groups of rules” drop-down list, select the appropriate group where the rule to be duplicated is stored. Select the rule and click on the DUPLICATE button [[File:MetisSmartModelingDuplicateButton.PNG|link=]], the rule is immediately copied and placed in the selected group of rules. It is an exact copy, or duplicate, of the original one. It can then be edited to fit all requirements or moved to another group.

In the “Modeling” menu, make sure that the “Rules” sub-menu has been selected. On the left, in the “Groups of rules” drop-down list, select the appropriate group where the rule to be moved is stored. Select the rule and click on the MOVE button [[File:MetisSmartModelingMoveButton.PNG|link=]], a new window opens where the target group of rule can be selected from the complete list of groups available in Metis Smart Modeling. Once the group of rules selected, validation is required in order to save all changes made to the rule.

| Moving a rule doesn't create a copy of it, neither an additional link. It really moves it from one group of rules to another.

In the “Modeling” menu, make sure that the “Rules” sub-menu has been selected. On the left, in the “Groups of rules” drop-down list, select the appropriate group where the rule to be linked to other group(s) of rule is located. Select the rule and click on the LINK button [[File:MetisSmartModelingLinkButton.PNG|link=]], a window opens up where a target group of rules can be selected from a drop-down list to set the group of rules where the selected rule should be applied. Once selected, validation is required in order to save all changes made to the rule.  

| Linking a rule to more than one group of rules, doesn't copy the rule inside that group. It is still identified through one ID.

To check in which groups of rules a rule is used (linked), select the rule for which a verification should be done and click on the "Currently used by" button [[File:MetisSmartModelingCurrentlyUsedByButton.PNG|link=]]. A window will open displaying all groups of rules, models and systems to which the selected rule is linked. Please refer here for more information.

In the “Modeling” menu, make sure that the “Rules” sub-menu has been selected. On the left, in the “Groups of rules” drop-down list, select the appropriate group where the rule to be edited is stored. Select the rule and click on the DELETE button [[File:MetisSmartModelingDeleteButton.PNG|link=]]. This opens a small window requesting to confirm the deletion of the selected rule. Once confirmed it will be definitively deleted from the selected group of rules.  

| When the same rule is used in more then one group of rules, Metis Smart Modeling will open a window showing a list of all groups in which the rule is linked. It is then possible to either delete the rule form all groups or select the group form which it should be deleted.

| Extra care should be taken when deleting a rule which produces an output which will afterwards be used as an input for another rule in a group of rules following the current one. This will result in wrong results at the end of the execution scheme.