3DEXPERIENCE – Using Expression Rules (SYNTAX) on the Platform

Within the Product Manager Role on the 3DEXPERIENCE Platform, you can create complex Expression Rules that dictate configuration validity as well as default values. One way in which this is possible is through an interactive expression editor that uses syntax to link values together, representing different scenarios. Expressions can specify requirements, co-dependencies, exclusions, and incompatibilities that drive product rules to further streamline your Product Plan Portfolio. The language used is laid out using logical operators like [AND], [OR], and [IMPLY] to link values and options together in a simplified format. The order in which the operators are linked with combinations of values and options dictates the rules set forth. Expression Rules can only be created at the version level of a Project Plan Portfolio.

Below is a list of language operators and examples you can find as helpful aids on the platform. As an added benefit, I’ve included more thorough explanations of the situational examples provided. Hopefully, this further emphasizes best use cases so that you can be more efficient in your day-to-day.

Expression Rules Criteria

Feature:
A feature without any option refers to all options associated with this feature.
Example: [Color]
Explanation: We’ve previously established the feature ‘color’ as a variant for a Model Version. This Variant is the beginning piece of a Rule Expression.

Feature/Option:
A feature with an option is a valid expression.
Example: [Color] [Blue]
Explanation: We’ve previously established the feature ‘color’ as a variant for a Model Version. Here, we assign the feature ‘blue’’s definition, a Variant Value, as a ‘color’ by arranging the expression in this order.

Feature/Several Options:
A feature followed by a list of options is equivalent to an OR in between all listed options.
Example: [Color] [Blue] [Green]
Explanation: We’ve previously established the feature ‘color’ as a variant for a Model Version. Here, we assign the features ‘blue’ and ‘green’’s definitions, both Variant Values, as ‘color’s by arranging the expression in this order.

Standard Operators for Expression Rules

NOT: [NOT] expression1
An expression preceded by a NOT is the logical complement of this expression.
Example: [NOT] [Color] [Blue]
Explanation: We’ve previously established the feature ‘color’ as a variant for a Model Version. Here, we assign the feature ‘blue’’s definition, a Variant Value, as a ‘color’ by arranging the expression in this order. Beginning this expression with the ‘NOT’ operator, we define this arrangement to be ‘false/not allowed’, for the associated Model Version.

AND: expression [AND] expression2
AND between two expressions express the logical conjunction of the two expressions.
Example: [Color] [Green] [AND] [City] [Paris]
Explanation: We’ve previously established the feature ‘color’ as a variant for a Model Version. Here, we assign the feature ‘green’’s definition, a Variant Value, as a ‘color’ by arranging the expression in this order. Additionally, we establish the feature ‘City’ as a variant for a Model Version. Here, we assign the feature ‘Paris’’s definition, a Variant Value, as a ‘City’ by arranging the expression in this order. Placing the operator ‘AND’ between these two expression segments links them ‘both’ in the same rule expression for the associated Model Version.

OR: expression1 [OR] expression2
OR between two expressions express the logical disjunction of the two expressions.
Example: [City] [London] [OR] [Country] [France]
Explanation: We’ve previously established the feature ‘city’ as a variant for a Model Version. Here, we assign the feature ‘London’’s definition, a Variant Value, as a ‘City’ by arranging the expression in this order. Additionally, we establish the feature ‘Country’ as a variant for a Model Version. Here, we assign the feature ‘France’’s definition, a Variant Value, as a ‘Country’ by arranging the expression in this order. Placing the operator ‘OR’ between these two expression segments links them as ‘one or the other’ in the same rule expression for the associated Model Version.

Conditional Requirement

IMPLY: expression1 [IMPLY] expression2
A conditional requirement – if (expression 1), then (expression 2) – uses the IMPLY operator.
Example: [City] [Paris] [IMPLY] [Country] [France]
Explanation: We’ve previously established the feature ‘city’ as a variant for a Model Version. Here, we assign the feature ‘Paris’’s definition, a Variant Value, as a ‘City’ by arranging the expression in this order. Additionally, we establish the feature ‘Country’ as a variant for a Model Version. Here, we assign the feature ‘France’’s definition, a Variant Value, as a ‘Country’ by arranging the expression in this order. Placing the operator ‘IMPY’ between these two expression segments links them as ‘one as well as the other/so long as’ in the same rule expression for the associated Model Version.

Co-dependency Statement

EQUIVALENT: expression1 [EQUIVALENT] expression2
Equivalent makes expression 1 and expression 2 have the same logical content.
Example: [Citizen] [French] [EQUIVALENT] [Country] [France]
Explanation: We’ve previously established the feature ‘citizen’ as a variant for a Model Version. Here, we assign the feature ‘French’’s definition, a Variant Value, as a ‘Citizen’ by arranging the expression in this order. Additionally, we establish the feature ‘Country’ as a variant for a Model Version. Here, we assign the feature ‘France’’s definition, a Variant Value, as a ‘Country’ by arranging the expression in this order. Placing the operator ‘EQUIVALENT’ between these two expression segments links them as ‘synonymous’ in the same rule expression for the associated Model Version.

Incompatible Statement

You may want to create two incompatible statements. You can do this with existing operators.
Example: [City] [London] [IMPLY] [NOT] [Country] [France]
Explanation: We’ve previously established the feature ‘city’ as a variant for a Model Version. Here, we assign the feature ‘London’’s definition, a Variant Value, as a ‘City’ by arranging the expression in this order. Additionally, we establish the feature ‘Country’ as a variant for a Model Version. Here, we assign the feature ‘France’’s definition, a Variant Value, as a ‘Country’ by arranging the expression in this order. Placing the operators ‘IMPLY’ and ‘NOT’ between these two expression segments links them as ‘if so, then not allowed’ in the same rule expression for the associated Model Version.

Additional Examples
Example Scenario: Include a bottle holder whenever we release a bicycle in France.
Example Syntax: [Country] [France] [IMPLY] [Accessories] [Bottle Holder]

               Example Scenario: Exclude a GPS Unit for a bicycle whenever a customer selects 26-inch tires or a basket option.
Example Syntax: [Tire] [Wanda 26] [OR] [Accessories] [Basket] [IMPY] [NOT] [Accessories] [GPS]

Expressions that specify invalid scenarios will automatically prevent certain scenarios from being chosen when creating Configurations.

Wrap Up

By using logical expression rules in your Project Plan Portfolio, you can ensure consistent results across your team. This means everyone always follows the same rules every time. This also makes it easier to manage going forward, as you set these rules up front and become the standards going forward.

Gabriel Rodriguez
Application Engineer II
Computer Aided Technology