Configuration Groups and Routes for Dimension-Based Products

In the world of manufacturing and supply chain management, the ability to offer variety without drowning in administrative complexity is a competitive necessity. Imagine you are a furniture manufacturer. You sell a standard office chair, but that chair comes in five different fabrics, three types of armrests, and two types of casters. If you were to create a unique product number (SKU) for every single possible combination, you would quickly find yourself managing hundreds of individual items for just one basic chair design. This is where dimension-based product configuration becomes a lifesaver.

Dimension-based configuration allows you to maintain a single "Product Master" while using dimensions—specifically the "Configuration" dimension—to define the specific variations of that product. At the heart of this system are Configuration Groups and Configuration Routes. These tools act as the logic engine that guides a user through the process of selecting the right components for a finished good, ensuring that the final product is both buildable and compliant with your company’s engineering standards.

In this lesson, we will explore how to structure these groups and routes to create a streamlined, error-proof configuration process. We will look at how they interact with the Bill of Materials (BOM) and how you can use selection rules to enforce product compliance at the point of order entry.

Understanding the Dimension-Based Philosophy

Before we dive into the technical setup, it is important to understand the philosophy behind dimension-based configuration. Unlike constraint-based configuration, which uses complex mathematical solvers to determine what is possible, dimension-based configuration is more linear and structured. It relies on a pre-defined sequence of choices.

When you use this method, you are essentially telling the system: "To build this product, the user must first choose an item from Group A, then an item from Group B, and finally an item from Group C." The system then looks at the items associated with those choices and automatically constructs the Bill of Materials for that specific configuration.

Callout: Dimension-Based vs. Constraint-Based Configuration

Dimension-Based: Best for products with a manageable number of variations and a clear, step-by-step selection process. It is easier to set up and maintain but less flexible for highly complex products with thousands of interdependent rules.

Constraint-Based: Uses a logic engine (like the Product Configurator in many ERPs) to handle millions of combinations. It allows for "if-then-else" logic across any attribute, regardless of the selection order. It is more powerful but requires significant technical expertise to build and debug.

Defining Configuration Groups

Configuration Groups are the fundamental building blocks of your product logic. Think of a group as a category of components or features that a customer must choose from. For example, if you are configuring a mountain bike, your groups might include "Frame Material," "Gearing System," and "Tire Type."

Each Configuration Group contains a list of specific items or sub-assemblies. When a user selects a group during the configuration process, they are presented with the options you have linked to that group.

How Groups Interact with the BOM

The magic happens when you link these groups to your Bill of Materials. Instead of listing every possible part on a standard BOM, you assign a Configuration Group to specific BOM lines.

For instance, if you have three different types of tires (Tubeless, Standard, and Studded), you don't put all three on the BOM as "required." Instead, you create a Configuration Group called "Tires," add all three tire items to that group, and then add a single line to your BOM that points to the "Tires" group. When the user selects "Tubeless" during the order process, the system knows to pull that specific item into the production order.

Best Practices for Group Creation

1. Use Logical Naming: Name your groups based on the functional area of the product (e.g., CAB_FINISH for Cabinet Finish) rather than internal part codes. This makes it easier for sales staff to navigate the configuration.
2. Granularity Matters: Don't make groups too broad. If a choice affects two different parts of the product, consider if they should be in separate groups to allow for more flexibility.
3. Standardization: Use the same Configuration Groups across similar product families. This allows you to reuse logic and makes reporting much cleaner.

Mapping the Configuration Route

If Configuration Groups are the "what," the Configuration Route is the "when." The route defines the sequence in which the configuration groups are presented to the user. This is not just about user experience; it is about establishing a logical flow that respects the physical assembly of the product.

A route consists of a series of steps, each linked to a Configuration Group. Each step is assigned a sequence number. The system will process these steps in order, starting from the lowest sequence number.

Why Sequence Matters

The order of selection is critical because early choices often dictate the availability of later choices. If a customer chooses a "Small" frame for their bike, the "Water Bottle Cage" group might need to be restricted to only small cages, or perhaps the option for a dual-bottle setup should be removed entirely. By placing the "Frame Size" group early in the route, you set the stage for the rules that will follow.

Step-by-Step: Creating a Configuration Route

To set up a route, you generally follow these steps within your system's product configuration module:

1. Navigate to the Product Master: Select the product you want to configure and ensure the "Configuration" dimension is active.
2. Open the Configuration Route Form: This is where you will define the steps.
3. Add a New Line: Create the first step in the process.
4. Assign a Sequence Number: Start with 10 (it's a good habit to leave gaps like 10, 20, 30 in case you need to insert a step later).
5. Select a Configuration Group: Link this step to one of the groups you created earlier.
6. Add a Description: Provide a clear instruction for the user (e.g., "Select the primary frame material").
7. Repeat: Continue adding lines until all necessary groups are included in the route.

Note: Some systems allow you to assign the same sequence number to multiple groups. This usually means those choices will be presented on the same screen or at the same time to the user. While this can speed up the process, be careful not to overwhelm the user with too many choices at once.

Implementing Selection Rules for Compliance

This is where we move from simple selection to "Product Compliance." Selection rules are the "guardrails" of your configuration. They prevent a user from selecting a combination of components that cannot be built, are unsafe, or are not offered by your company.

Selection rules are typically applied at the Configuration Route level. There are three primary types of rules you will encounter:

1. The "Include" Rule

This rule forces the selection of a specific item in a later group based on a choice made in an earlier group.

• Example: If the user selects "Electric Motor" in the Power Source group, the "Include" rule can automatically select the "Lithium Battery Pack" in the Energy Storage group.

2. The "Exclude" Rule

This is perhaps the most common rule. It prevents certain combinations.

• Example: If a customer selects a "Carbon Fiber Frame," you might have an "Exclude" rule for the "Heavy Duty Rear Rack" because the frame isn't designed to support that much weight at the mounting points.

3. The "Mandatory" Rule

This ensures that a selection must be made. While most configurations require a choice for every group in the route, mandatory rules can be conditional.

• Example: A "Safety Certification" selection might only be mandatory if the "Industrial Use" option was selected in a previous group.

Warning: Be careful with "Circular Rules." A circular rule occurs when Group A requires an item from Group B, but Group B excludes the very item in Group A that triggered the requirement. This will cause the configuration engine to crash or enter an infinite loop, preventing the order from being saved.

Practical Example: Configuring an Industrial Pump

Let's walk through a real-world scenario to see how these elements come together. We are configuring an "Industrial Fluid Pump."

The Groups

• GRP_HOUSING: Cast Iron, Stainless Steel, Plastic.
• GRP_MOTOR: 5HP, 10HP, 20HP.
• GRP_SEAL: Standard Nitrile, High-Temp Viton, Chemical-Resistant PTFE.

The Route

1. Sequence 10: GRP_HOUSING (The material of the pump body).
2. Sequence 20: GRP_MOTOR (The power required for the application).
3. Sequence 30: GRP_SEAL (The type of seal needed for the fluid).

The Compliance Rules

• Rule 1 (Exclude): If GRP_HOUSING = "Plastic," then Exclude GRP_MOTOR = "20HP." (The plastic housing cannot withstand the torque of the 20HP motor).
• Rule 2 (Include): If GRP_HOUSING = "Stainless Steel," then Include GRP_SEAL = "Chemical-Resistant PTFE." (Stainless steel pumps are almost always used for corrosive chemicals, so we default to the best seal).

How the User Experiences This

When the salesperson opens the configuration screen, they first see the housing options. If they click "Plastic," and then move to the motor selection, the "20HP" option will either be greyed out or hidden entirely. This ensures that the salesperson cannot accidentally sell a pump that will fail in the field, maintaining product compliance and customer safety.

Technical Implementation: Data Structure

While most of this is managed through a graphical user interface (GUI) in an ERP system, it helps to understand how this data is structured on the back end. If you were to represent a configuration route and its rules in a structured format like JSON, it might look something like this:

{
  "ProductMaster": "PUMP-001",
  "ConfigurationRoute": [
    {
      "Sequence": 10,
      "GroupID": "GRP_HOUSING",
      "Description": "Select Pump Body Material",
      "Options": ["CAST_IRON", "ST_STEEL", "PLASTIC"]
    },
    {
      "Sequence": 20,
      "GroupID": "GRP_MOTOR",
      "Description": "Select Motor Power",
      "Options": ["5HP", "10HP", "20HP"],
      "Rules": [
        {
          "Type": "Exclude",
          "Condition": "GRP_HOUSING == 'PLASTIC'",
          "Target": "20HP"
        }
      ]
    },
    {
      "Sequence": 30,
      "GroupID": "GRP_SEAL",
      "Description": "Select Seal Type",
      "Rules": [
        {
          "Type": "Include",
          "Condition": "GRP_HOUSING == 'ST_STEEL'",
          "Target": "PTFE"
        }
      ]
    }
  ]
}

Explanation of the Code Logic

• ProductMaster: Identifies the base item.
• ConfigurationRoute: An array of objects, each representing a step in the process.
• Sequence: Controls the order of operations.
• Rules Array: Each group can have an array of rules that evaluate the state of previous selections.
• Condition: A logical statement that must be true for the rule to trigger.
• Target: The specific item or option within the current group that is affected by the rule.

Comparison Table: Group vs. Route vs. Rule

Industry Recommendations and Best Practices

When building out your dimension-based products, keep these professional standards in mind:

1. The "Default" Strategy

Always set a default value for your Configuration Groups where possible. This speeds up the entry process for standard orders. If 80% of your customers order the "Cast Iron" housing, make that the default. The user only has to change it if they need something special.

2. Version Control

Configuration logic changes over time. Engineering might discover that a certain combination is no longer viable, or a supplier might stop providing a specific component. Use versioning on your BOMs and Configuration Routes so that you can maintain historical accuracy for old orders while enforcing new rules for current ones.

3. Testing the "Negative Path"

When testing your configuration, don't just test the combinations you want people to pick. Try to break it. Try to pick the most expensive motor with the cheapest frame. If your rules don't catch the error, your configuration isn't ready for production.

4. Modular BOMs

Keep your Bill of Materials modular. Instead of one giant BOM with 500 lines and 50 configuration groups, use sub-assemblies. A sub-assembly can have its own BOM and its own configuration logic. This "nested configuration" is much easier to manage and troubleshoot.

Callout: The "Phasing" of Configuration

Configuration happens in three distinct phases:

1. Sales Configuration: The customer or salesperson chooses the options.
2. Technical Validation: The system checks the rules to ensure the build is valid.
3. Production Generation: The system creates a unique "Configuration ID" and generates a specific BOM and Route for the shop floor.

Skipping the validation phase is the leading cause of "unbuildable" orders reaching the warehouse.

Common Pitfalls and How to Avoid Them

Over-complicating the Route

One of the biggest mistakes is creating a route with 50 different steps. This leads to "decision fatigue" for the salesperson and increases the likelihood of a logic error.

• Solution: Combine related choices into a single group or use sub-assemblies to break the configuration into smaller, manageable chunks.

Ignoring Lead Times

Sometimes, a specific configuration choice significantly impacts the lead time. For example, a "Custom Paint" option might add two weeks to the production schedule.

• Solution: Ensure that your configuration groups are linked to items that have accurate lead-time data. Some advanced systems can even calculate a dynamic "Available to Promise" (ATP) date based on the specific configuration selected.

Forgetting the "Non-Stocked" Items

In dimension-based configuration, we often focus on the big parts (motors, frames, etc.). But what about the small things, like the specific manual or power cord that changes based on the country of destination?

• Solution: Create a "Regional Compliance" group that is automatically triggered based on the customer's shipping address. This group can pull in the correct manual, labels, and power cables without the user having to remember them.

Circular Dependencies

As mentioned earlier, circular dependencies are the bane of configuration logic.

• Solution: Always map your logic on a whiteboard or in a flowchart before entering it into the system. If you see arrows pointing back and forth between two groups, you have a potential circularity issue. Logic should generally flow in one direction: forward through the sequence.

Step-by-Step: Validating a Configuration

Once you have set up your groups, routes, and rules, you must validate them. Here is a standard procedure for validation:

1. Open the Product Configuration Simulator: Most ERPs have a "Test" or "Simulate" function.
2. Select a Base Product: Choose the product master you just configured.
3. Run a "Standard" Configuration: Select the most common options and verify the resulting BOM is correct.
4. Run a "Boundary" Configuration: Select the most extreme options (e.g., the largest motor with the largest frame) and verify compliance.
5. Test the Rules: Intentionally try to select an "Excluded" combination. The system should stop you.
6. Check the BOM Output: Look at the generated BOM. Are there any missing items? Are there any duplicate items?
7. Final Approval: Once validated, activate the Configuration Route version to make it available for live sales orders.

Frequently Asked Questions

Q: Can I use Configuration Groups for services, or just physical parts? A: Absolutely. You can use groups to include "Extended Warranty," "Installation Services," or "Special Packaging." These are treated as "Service Items" on the BOM and will be pulled into the sales order just like a physical part.

Q: What happens if I change a Configuration Group after it’s been used in an order? A: This is why versioning is important. If you change a group, it usually won't affect existing orders that are already "Configured." However, if you delete an item from a group that is currently being used in an open production order, you may run into errors during the "Explosion" of the BOM. Always use "Effective Dates" to phase out old options.

Q: Is there a limit to how many rules I can have? A: Technically, no. But practically, yes. The more rules you have, the slower the configuration screen will respond. If you find yourself needing hundreds of rules, it is a strong sign that you should move from a Dimension-Based model to a Constraint-Based model.

Key Takeaways

To master the setup of dimension-based products, remember these core principles:

• Logic Precedes Data: Always map out your configuration flow on paper before touching the software. Understand the physical constraints of your product first.
• Groups are Containers: Use Configuration Groups to categorize choices. They are the bridge between the user's selection and the physical items on the Bill of Materials.
• Routes are the Workflow: The Configuration Route defines the user experience. Use sequence numbers to create a logical, step-by-step path that respects engineering dependencies.
• Rules are the Guardrails: Use Include and Exclude rules to enforce product compliance. This prevents the sale of unbuildable or unsafe products and reduces the need for manual order review.
• Keep it Simple: If a product is too complex for a linear route, consider breaking it into sub-assemblies or moving to a constraint-based configuration engine.
• Test Thoroughly: Use both positive and negative testing to ensure your rules are working as intended. Validate the final BOM output to ensure no parts are missing.
• Focus on the User: Name your groups and options in plain language. The goal is to make it so simple that a new salesperson can configure a complex product without needing an engineering degree.

By effectively utilizing Configuration Groups and Routes, you transform your product catalog from a rigid list of SKUs into a dynamic, flexible system that can meet diverse customer needs while maintaining strict operational compliance.