17.1 - Optional vs. Alternatives Yes/NO

Typically an option of your product is set up as an optional Feature in your configuration model. But in some cases it might be more convenient to set it up as pair of alternative features, one for “no” and one for “yes”. Now you may wonder, why is this more convenient? Let's dive into this, by looking into a Example. 

This model of the Roadmaster 100 has a lot of options to configure. One of those options is to configure the rear end of the Roadmaster. You see that we've built the configuration by using a combination of Alternatives and Optional Features. During configuration, we don't want the top cap to be configured in combination with the rear doors. But when a tail lift is selected the top cap is configurable.

In this case, we need the "yes" of the tail lift for the top cap to be visible. Set a condition on the Top Cap to say that this Feature is only visible when the Tail lift is selected. In this example we use the two Alternatives as a “yes” and a “no”. These can later be used in let’s say extra options. The door retainers are set with an condition that the rear doors Feature has to be selected to make these two Feature Configurable. If the tail lift is selected, the top cap will appear and can be used as a “no”. Now the Door retainers and 270 degrees hinges respond to as they need the “yes” of the rear doors to be visible.

When other options are dependent on an option not being selected (inactive), it’s much more convenient to work with the no instead of an unselected Feature with a value of zero. In this case, yes means selected and no means not selected. Such cases may apply when you are setting up:

• Visualization
• Quotation Templates
• Dynamic Groups (That specifically filter on “no”).

To the user both methods mean the same, but for you as the administrator of the Configuration Model, it might be the difference between an easy and hard to manage Configuration Model.