Back
 

R12 Configurator Rules

iWare Logic > Blog  > R12 Configurator Rules

R12 Configurator Rules

R12 Configurator Rules

Introduction:
Rules are the basic programming tool in the Oracle Configurator Developer (OCD).  Rules allow you to make your model BOMs “intelligent” by selecting optional items based on conditions you specify.  Rules are also used to control the User Interface.  Rules may be constructed graphically or in a text editor using the Constraint Definition Language (CDL).


Configuration Rules can be thought of as computer-assisted selection of products, components, features, and options. These relieves user from making decisions of final components being selected in configurable product.
Technically configuration rule can be defined as an explicit definition of all valid logical relationships a collection of configurable items and compatibility relationships among items
When designing rules you need to consider:

  • Simplicity, readability, and maintainability.
  • Model structure.
  • User Interface behavior.
  • Documentation and control.

Types of Configuration Rules:

1.Logic rules are the workhorse of the Oracle Configurator and allow you to …

  • … define simple AND and OR conditions.
  • … select many options together from any level in the model BOM.

configuration Logic
Logic Rules enable you to express constraints among elements of your Model in terms of logical relationships. For example, selecting one Option A may require that Options B and C be included in the configuration.
Logic rules define item to item relationships. Logic Rules can push both ways. For example, Side A can impact the logic state of Side B, and Side B can impact the logic state of Side A Either side of the rule can contain one or more Features, Options, and so on. Configuration validity at run time is ensured by Oracle Configurator.

2.Property-based Compatibility (PBC) rules are perhaps the most powerful rule available in the Oracle Configurator and allow you to …

  • … select the options in an Option Class that match a given property.
  • … use many PBC rules on the same list of options.
  • … add / remove items in Option Classes without modifying PBC rules.

Property-based Compatibility

Property-Based Compatibility rules: Perform a comparison between property values shared by Features or Option Classes. It can include multiple comparisons among the participating Features. It Specify the Properties to be checked for compatible values .It specify the type of comparison to be made between the Property values, using standard numeric and string comparison operators
To create a Property-Based Compatibility rule, participants must be Features with Options that have Properties and All Options used in the rule must have a common property. These are easier to implement because individual options are actual inventory items which are maintained in Oracle Inventory and populated to CZ schema through concurrent program.

3. Design Chart rules are the easiest to read and maintain and can often be specified with spreadsheets by functional experts.

Design Chart

Design Chart express complex explicit compatibility relationships. It contains various features.
Primary Feature: Options define variations of the Model
Secondary Features: Defining Features: Unique combinations of options that define options of the primary Feature
Optional Features: Options can be compatible or incompatible with Options of the primary Feature. It can have multiple secondary Features.

4. Statement rules allow you to create more complex logic and numeric rules than you can create graphically.  Oracle provides a variety of functions for trigonometry, rounding, logic, property evaluation, etc.

Statement rules

You define a Statement Rule by entering text rather than building the rule interactively by selecting Model structure nodes and operators. A Statement Rule must be written using the Constraint Definition Language (CDL). Statement Rules can define a Logic or Comparison relationship, a Numeric contribution or consumption, or a Property-based Compatibility relationship. Explicit Compatibilities and Design Charts cannot be expressed using a Statement Rule
Statement Rules enable you to:

  1. Write a rule using multiple operands in a single CDL statement
  2. Include multiple abstract relations in a single rule
  3. Define both sides of a rule in a single expression

Constraint Definition Language (CDL) and some examples
The Constraint Definition Language (CDL) is a modelling language. CDL allows you to define configuration rules, the constraining relationships among items in configuration models, by entering them as text. Valid data types when defining a rule in CDL are INTEGER, DECIMAL, BOOLEAN, TEXT, Node types.

Summary

  1. Rules are the basic programming tool in the Oracle Configurator Developer (OCD).  Rules allow you to make your model BOMs “intelligent” and to control your User Interface.
  2. Logic rules are the workhorse of the Oracle Configurator.
  3. Property-based Compatibility rules operate on entire Option Classes and are insensitive to engineering changes.
  4. Design Chart rules are the easiest rules to read and maintain.
  5. Statement rules allow more complex rules to be written.

–Aditya Ghate

Share