Examples of Product configurators and the Importance of Guided Selling

By Alex Ginsburg


In this post Alex Ginsburg, senior specialist with more then 25 years of experience in the field of product architecture and configuration, will share his personal experience when going out on the hunt for a new vacuum cleaner and the frustration he as a customer experienced. Alex will summarize his findings and what we can learn from these companies to improve their customer experience with well-designed product configurators and guided selling techniques.

Understanding customer needs

I have been working with product development all my adult life – more than 25 years. All good products stem from a profound understanding of customer needs. To develop a perfect product, a company needs to know where, how, when, why, how often the product is used, cleaned, maintained, stored, etc.

There are multiple tools and methods to capture customer needs and translate them to specifications containing functions, features and performance levels of the product. Few companies use these methods in a consistent and structured fashion, but most still manage to develop tacit knowledge within their product development teams. To a smaller extent the develop organizational structured knowledge in the form of target segmentation models with customer personas, check lists and other assets. Therefore, most companies have, if not great, at least an acceptable knowledge about their customers’ needs and have the capability to translate them into some form of product specifications.

The process from specification-to-design is often the more consistent and structured. There are documented methods in how to break-down specifications from systems to components and how to calculate, simulate and test to make sure specifications are met.


If the product and system level specification is well done, a development team only needs to verify against this specification. They don’t need to verify against the actual customer needs. An example is the customer requirement that the product must be portable. There is a clear specification for the max weight, the max distance of centre of gravity from the body of the person carrying the product, the shape and material of the handle and the max height from product base to the handle. If the development team meets these specifications the product should be portable.

If I am a professional, repetitive buyer of a certain product I have probably gained enough knowledge and experience with the product to be interested in many of the details of a very technical specification. But when I’m a one-time, novice buyer of a certain product, those details are meaningless to me. I have at least some idea about how I will use the product. I know if I want it to be easily portable. But if learn that it has an Ergo-handle covered with Tri-flex rubber and if the centre of gravity is 30 cm from my body when carrying, it doesn’t help me make a decision.

So, how come many companies are fairly successful in developing products that are fulfilling customer needs, but they are terribly bad in guiding the buyer in the purchasing situation. How come they are throwing a lot of mainly meaningless specification values, technical terms, internal brand and model names at us. Why not ask me about what I need and present the best match?

My plan is to share both mine and my colleagues’ experiences, knowledge and observations related to needs-based selling, also referred to as guided selling. I will start with my experience when buying a vacuum cleaner, but I will also discuss some more complex and industrial products. So here we go…

Example: customer experience buying a vacuum cleaner

I will start by sharing a recent personal experience when buying a new vacuum cleaner for my home. Although I actually participated in developing a new vacuum cleaner platform long time ago, I have mostly forgotten the details. Therefore, I am considering myself a regular vacuum cleaner buyer. I know the where, why and how I need to vacuum, but I am not very interested in special vacuum cleaner features or technical specifications.

My family has two vacuum cleaners. The first one is always “on display” in the kitchen to be easily at hand. It is used several times a day for small jobs. Most importantly, with this vacuum cleaner, is that it needs to look nice. An ugly product “on display” would drive me nuts. Secondly, it needs to be light and easy-to-use. It doesn’t need any exceptional high performance, and I only expect it to last 3-4 years. It definitely should not be expensive. Since it used frequently and has a short expected lifetime, the environmental aspects such as power consumption and material selections are also important to me.

The second vacuum cleaner, which this story is about, is the bigger one used every second week. It is used to vacuum the entire house and to do the occasional “big, dirty jobs” like cleaning the cars. I have destroyed one of these vacuums by cleaning the dust after having plastered a room. The last one was destroyed when my kids used it to clean an outdoor sofa from leaves. They reasoned that there could be big spiders among the leaves, and after completing the job, they left it outside in a heavy rain – game over again.

Consequently, my top priority for a replacement vacuum cleaner is that it is sturdy. At the same time, I absolutely don’t want it “on display”. It must fit into my rather narrow cleaning cupboard, preferably without half of it falling out every time I open the door. I don’t have any indoor pets and my family does not have allergies, so a normal level of cleaning performance is enough. Absolutely no extra rotating brushes or wet cleaning is necessary and, in my impression, will only jam and break down. Since it is used infrequently and I expect it to last at least 15-20 years, the previous environmental aspects and price are of less concern.

Nilfisk vacuum cleaner

I am thinking something sturdy, half-industrial, like Nilfisk , but it must be a different form factor to be stored in my small closet. I’m not planning to rebuild the closet for a vacuum cleaner.

I started to look around the internet, and almost all vacuum cleaner manufacturers had the same approach. I have included images below from the Bosch  webpage as an example. On the landing page, Bosch starts with heavy marketing of some features and innovations that do not match what I need. I start by selecting a type of vacuum cleaner and model, often with some possibility to filter on some pre-selected features or specification values such as “HighSpin motor” or cord length.  I am presented with a list of model names with some images, highlights and the specifications.

Some of these models could be a good match for me, maybe not. The issue here is that I really don’t know. What I am sure of is that none of the models presented spoke to me or my needs.

Example: when product configurators are empowered with guided selling

Out of the maybe 15 manufacturers that I looked at, Miele was the only one taking a different approach. At the start I was asked the same questions about the type of vacuum cleaner – canister with bag, bagless, upright… Afterwards, I was asked how I will use the vacuum cleaner and about some of my priorities.

At the end, I was presented with my best match (I was laughing out loud): Compact C1 Cat and dog powerline with turbo-brush and odor filter.

Miele has by far the best needs-based selection tool of all the brands I looked at. They approach guided selling in a very nice and easy-to-use manner. Unfortunately, they don’t have a product that fits my needs. I’m thinking that they have made a strategic decision to target specific segments and applications that do not include me. I fully understand that a company will not be excellent if they try to be everything to everyone.

But I was curious, so I went back and changed some of my selections. I found that my changes didn’t affect the result. I went back again and changed my selections in a more random way. It seemed that behind the nice customer-facing tool, they only have a very narrow and rigid product range. By narrow, I mean there are a few basic models to select between. By rigid, I mean that there are few possibilities to add or remove features and options per basic model.

5 insights to improve guided selling together with your product configurator

I liked Miele’s front-end, but I left disappointed with their product offering. And, when I thought about it, Miele didn’t learn anything from my interaction. They can probably track my visit, making a first set of selections followed by back-and-forth changes in more and more random ways. I don’t see how they can’t possibly guess why I left without purchasing a vacuum cleaner. They missed the opportunity for free and truly honest buyer feedback.

To summarize my insights from my vacuum cleaner purchasing experience I to:

  1. Make it easy to find the right product by explicitly asking customers about their known needs and then present the best match.
  2. Also target unknown needs by asking broader questions about how, when, where, why, how often the product is used. For example, I might have discovered that I needed a waterproof vacuum cleaner that can be forgotten outside in the rain. I never would have thought of something like that before writing this post.
  3. Don’t be afraid to ask questions even if there is a risk of not having an answers today. If buyers are asking for combinations that don’t match today’s products, the information can feed into new product development, helping to develop a better and more flexible future product range.
  4. Have one entry point for all interchangeable products. With interchangeable, I mean that they have the same basic function and a customer could replace one with the other. In the vacuum cleaner example, I don’t care if the vacuum cleaner is canister with bag or bagless. That is an annoying, irrelevant selection to me. I want the best match from all types.
  5. Finally, balance the above recommendations on asking more and wider questions with simplicity for the user. Personally, I would never spend the time to answer hundreds of questions. The solution is to expand to more detailed selections in areas of potential high interest, but the expansion into more detail must be voluntary. I would happily answer a series of questions related to max storing dimensions, because I was trying to make sure the new vacuum cleaner would fit into my small cleaning closet. On the other hand, many other buyers probably wouldn’t care and would find these questions annoying.

Scania as an example on guided selling in complex product configurators

I will finalize this post by giving a good example of guided selling for a more complex product: Scania trucks. Scania’s configurator is not applying 100% perfect guided selling, they do have some steps in the configurator where you need some expertise to select items like wheel configuration. I guess most truck buyers would know what they want here. But Scania’s main approach is very good. They don’t ask to select a model or specification values such as a motor type or size. They ask how the truck will be used. For example, there are questions about max load and the type of roads the truck will travel. Based on these answers Scania proposes a complete product configuration including the correct motor size. Every truck they deliver is unique to meet a customer’s specific needs.

Try it yourself at Scania’s home page 

The strongest combination: when customer needs match an available product configuration

By far, the strongest combination is both a good front-end with easy-to-use guided selling and a truly configurable product that meets different customer needs with a perfectly matched offering.

There are two fundamental ways to get started:

  1. The Miele “front-end” way that starts directly with guiding a customer to the best matching product. In some cases, the product assortment and product flexibility doesn’t allow a good match with a customer’s needs. But please make sure to think about how you can learn and improve the matching over time. If you are interested in all aspects of Mass Customization, you should read [link to Mass Customization white paper] covering the Product Design, Information System and Supply Chain aspects of truly fulfilling unique customer needs. (PC: car config assessment)
  2. the Scania “back-bone” way that starts with a modular product, documented and handled in the IT-systems for easy mix and match and assembly on a flexible line for each customer order. Scania’s modularity has been one of their most valuable assets for decades, but it is only in recent years that they have started to offer their product range through guided selling. If you want to read more about Modularization – how to design a product that has the flexibility to meet a wide variation of customer needs, you should read [what is a good modular system].



To summarize, product managers, sales managers and sales reps should start by thinking about the principles used in selling a product. Is the product pushed to customers, or are the needs of customers pulled to align and propose the right solution?

Download Guide: How to Achieve Mass Customization
Alex Ginsburg

Alex Ginsburg

Principal, Manager & Partner



Configurability, Configuration and Mass Customization


A modular product architecture enables you to reduce complexity and accelerate value creation. In this insight you will learn more on what it is and how you can harness it for mass customization.

Customers want innovative products, fast. Companies want to make customers happy and be 21st century lean. So how does all that work? Modular Management delivers clarity, performance and customer centricity so clients can reduce complexity and accelerate value creation.



ABB Robotics

Business Transformation with Product Architecture

Executive Summary

ABB is a market leader in industrial robots and robot software, equipment and complete application solutions.

At the start of 2013, rising labour costs in key industrial markets, ever-increasing demands on quality, and cost reductions in robot design had led to an inflection point. Robots had become a very attractive alternative for many different industries.

Despite new and more aggressive competition, ABB Robotics was getting ready for a spike in the demand curve. And while it was increasingly important to protect prices, maintain market share, stay cost competitive and deliver orders faster and faster, the key question facing the executive management team was how to take advantage of the growth opportunities out there?

The answer was a modularization program and the results were significant:

  • 300% increase in the number of different controller cabinet products
  • 50% reduction in controller parts
  • 50% reduction in the size of smallest controller
  • All controllers ready for remote serviceability
  • 80 independent software development tracks – up from 1
  • < 1 month in time to market for new features – compared to 6 months before the program
  • 50% increase in robot arm assortment
  • Quadrupled production capacity.


The new product architecture had additional benefits in terms of process improvements and strategic product management, not least for the software team, where customer values and strategy could be embedded in the modules directly – for the very first time.

As software architecture can easily be circumvented by the coders, it is important to repeatedly go back and look at the reasons why certain functions were grouped into modules. We have done software modularity before, but this time we factored in customer values and strategy. I believe this makes our new architecture much stronger.

Roger Kulläng
Global Software Solution Architect
ABB Robotics


Working together with ABB Robotics on this modularization and transformation program have been challenging and as you can read, highly rewarding. The team at ABB are highly skilled when it comes to modularization and making business work. This project taught me a lot, and once again confirmed that modularization is truly powerful when done right.

Karl Bråtegren, Senior manager
Modular Management

Goals for the Modular Architectur

Strategic Goals

ABB Robotics launched a pre-study into modularity. It was initiated and conducted with the help of Modular Management, and inspired by the business success of a key customer, Scania.

This pre-study indicated that the company should be able to make strategic gains in sales as well as operations by implementing modularity. Complexity, as measured in unique parts, could be cut in half for several product lines and there would be many positive impacts on overhead, direct material and tied up capital cost. In addition, the management team concluded that with modularity it was a realistic ambition to deliver more and better products to ABB customers while improving product quality.

IRB 1100. The Most Compact and Fastest Robot Ever at Launch

Based on the promising results of the pre-study, the ABB Robotics management team initiated a modularity program covering all robot families, including software.

Yet since the competition was getting harder, ABB Robotics initiated a market analysis. The market analysis team was tasked to answer a fundamental question: which customer requirements should ABB Robotics strive to gain competitive advantages in?

A team of product and business line managers conducted over 100 customer interviews. The result was a customer segmentation model and product range specifications for the future modular products.

Product Scope and Goals

First out the gate were the robot controllers.
A cross-functional team used the findings from the market analysis and modular function deployment (MFD) method to create a conceptual modular architecture. Key product requirements were to:

• reduce the size of the controller
• deliver out-of-the-box intelligent safety and online service capabilities
• reduce direct cost
• reduce number unique parts to build the controllers
• enable controllers to be built by robots.

Modular, OmniCore Robot Controllers

Next up was the software used to program and move the robots. A team of leading software architects and system test managers attacked the structure of the current software. The ambition was to:
• move to a new software architecture that enables continuous release of features
• secure high independence from the hardware
• reduce bugs through upstream module level tests combined with fully automated tests of the most common functionality.
• improve the robot software overall to make robots more aware, smarter and connected.

Finally, two teams targeted robot arm modularity. Here the targets were to:
• create a technically more consistent robot arm architecture
• enable more re-use
• expanding the number of robot arm variants used for different applications.

Business Results

The results of the modularization program were significant.


  • Number of different controller cabinet products increased by 300%
  • Unique parts cut in half
  • Size of smallest controller cut in half
  • All controllers equipped with intelligent safety capabilities, allowing removal of fences
  • All controllers ready for remote serviceability.


  • Number of possible independent software development tracks were expanded from one to up to 80. ABB Robotics will scale to the number of development tracks that they see makes most sense for their customers and their own operations.
  • Level of fully automated tests are set to increase to over 90% of all test cases
  • Time to market of new features will be reduced to less than a month for many features compared to approximately half a year at the starting point.

Robot Arms

  • Product assortment expanded by over 50%
  • Number of unique parts reduced by more than 30%
  • Entire range of industrial robot arms built around only a handful of main layouts compared, which is less than half compared today.


  • Number of production lines reduced by 50%
  • Factory footprint of the new production lines to be cut in half compared to today
  • Production capacity quadrupled from 2013 level
  • Robots will be produced by robots assisted by humans in a mostly collaborative fashion.

And there were additional benefits.

According to Roger Kulläng, Global Software Solution Architect, ABB Robotics, “As software architecture can easily be circumvented by the coders, it is important to repeatedly go back and look at the reasons why certain functions were grouped into modules. We have done software modularity before, but this time we factored in customer values and strategy. I believe this makes our new architecture much stronger.”

If you are inspired by the ABB Robotics case and  interested in understanding  how your product architecture can benefit from a modularity program, please fill in form below and our specialist team will contact you to.

Contact us


When the Product Architecture is a System of Modular Systems

By Tobias Martin


This is my second post in a series of blogs around modular systems. The first post, called What makes a Good Modular system is found here… 

In this post, I will move beyond the idea of good, balanced module systems into how they can be leveraged across multiple product platforms to generate even greater profitability. I will continue with the same example company who started with independent module systems and transitioned to ones that are broadly shared.

What is a Modular System?

A modular system is a collection of building blocks that can be configured in different ways, adapting for different customer needs. Over time, some modules will be developed to serve new purposes or to improve performance in some aspect. Optimization and cost-cutting can be done within modules without the typical ripple effect throughout the product and, when done well, without reducing the value to customers. Many companies use modularization as a tool to reduce product complexity or to make the customer order process more efficient by configuring-to-order rather than engineering-to-order.  

If you are interested to know how a Modular design differs from traditional design, feel free to download this explanatory guide Modular Design VS Traditional Design

The most obvious and traditionally known way to create modular systems is to group a number of product platforms that share technical properties (technology and sizing) and supply chain properties (factory footprint and supplier base) into a systems. The system, in this case, is scoped as end-to-end products. Functions that exist across other platforms are not typically evaluated or shared.

This inevitably leads to sub-optimization where functions are customized and re-evaluated towards the specific platform, rather than optimized from a holistic point of view. In the worst case, the customizations are not necessary from a performance perspective and may even decrease customer value. In all cases, they become a barrier for supply chain and aftermarket efficiency improvements that would benefit from greater commonality

High-Level Product Architecture and Shared Modular Systems

Some leading companies have taken it to the next level by defining a wide-scope product architecture. They have a  system of modular systems that can be shared across multiple product platforms. Actually, the product architecture is a configurable system of modular systems, enabling massive benefits for scale and flexibility.

One example of such a leading company is Volkswagen Group (VW), the world’s largest auto manufacturer. VW has consistently pushed the boundaries of product platforms and architecture, marking the direction of the whole industry. I often use them as an example of all sort of benefits connected to modular systems. In this blog post I will use VW to explain the concept of high-level product architecture and shared modular systems.

1997 Volkswagen Golf

1997 Volkswagen Golf

In the early 1990’s VW pioneered the use of shared platforms in the auto industry. VW had acquired AUDI in the mid 1960’s, SEAT in 1986 and SKODA in 1991 and was manufacturing more than 20 different car models. By sharing the base platform between multiple models and brands, economies of scale could be reached for component such as drivelines, interiors and chassis. Over time, the approach was criticized for limiting the ability to adapt the product to different brand images. This hurts the status of premium brands, but also increases the risk of not reaching low enough cost levels for value brands.

2011 Volkswagen Golf

2011 Volkswagen Golf

The second generation of VW’s platform concept came in the mid 2000’s. There is a clear switch from standardization to modularization, enabling wider platforms with increased economies of scale. All Audi production cars were now being built from the same platform – a dream for the supply chain. They enabled huge increases in efficiency, fewer assembly lines and greater purchasing leverage.

2017 Volkswagen Golf

2017 Volkswagen Golf

One decade later, mid 2010’s, the bomb dropped, and it is called MQB (german for Modularer QuerBaukasten, roughly translated as Modular Transversal Engine Building System). VW was now aiming to build cars of practically any size from the same product platform. In the end of 2020, the MQB platform encompasses more than 80% of the VW production volume.

A Modular System does not have to span a product End-to-End

I will use Volkswagen to explain what is a product architecture, what is a modular system and how modules relate to both concepts. As already mentioned, I define modular product architecture, as a system of modular systems that is configured on all levels. Here, I illustrate it in relation to an end-to-end-product, showing that each modular system spans only a portion of the full product:

To date, VW has a number of (Modulare Baukästen or Modular Building Systems.) They have MQB, as already mentioned, but also MLB for longitudinal engines and MMB for mid-engine cars. For electric drivelines, we have the MEB and PPE platforms. In actuality, these additional platforms only exist because VW has many premium, high-performance cars in their portfolio, especially under the Porsche and Audi brands.

As mentioned earlier, the bulk of VW’s volume today is covered by MQB. What is especially interesting to note is that this platform and all of the others are instances of the same configurable product architecture. What I mean is that the different platforms can be built by the same underlying configurable modular systems. To explain this concept, I will use the electric MEB platform:

The MEB is VW group’s first all-electric platform, built completely around the electric drivetrain. Obviously, one of the most important parts of any battery-powered electric platform is the battery. And here comes the point… the battery is actually a modular system of its own. A modular system that can be shared with the other electric platforms, including the PPE for premium high-performance electric cars.

The important factors for configuring a battery are how much space you have at hand and how much energy you need to store. If the different platforms can share the same high-voltage interface and battery footprint logic, there is no reason why this modular system could not be shared.

This is a modular system that can be configured to deliver different levels of battery capacity, charging performance and available footprint. Many of the modules inside the system can be standardized for an enormous volume consolidation. This includes, for example, the cell module, cell management controller and high voltage connector. It creates huge benefit when setting up the new battery supply chain. VW has even hinted they want to sell their electric platform to other car makers, further expanding the consolidated volumes and making the investments in development and supply chain even more profitable.

Shared Modular Systems

To add clarity, let me put some words from the VW Electric car platforms on the boxes in the earlier modular product architecture illustration. This is only illustrative, not facts:

Finally, you see modularity on different levels and an extremely systematic approach that can be leveraged across the functions of the company, e.g. Production, Strategic Product Planning, and Sales.

Product architecture and shared Modular Systems in other industries

The very same thinking can be applied in many other product segments in both industrial and consumer goods: appliances, machinery, equipment, etc.

For example, in the home appliance industry the tradition is to see different types of appliances as different modular systems. They would say that there is one modular system for washing machines and another modular system for dryers. While this makes sense from a functional perspective, it lacks the perspective of industrial design and production.

Shared styling and user interface across product types

Since the washers and dryers are typically used in combination and located together in our homes, you clearly want them to have a common design for both the aesthetics and the user interface. From a modular system standpoint, it makes a lot more sense to see the front panel and user interface as a shared modular system rather than parts that must be aligned within the washer and dryer modular systems. This way, you can introduce updates to both the styling and user interface simultaneously across the two product lines. This also matches the expectations for customers who are looking for consistency in the look and operation.

Flexible line assembly

A driving factor in the home appliance industry, just as in the car industry, is to produce many products on the same flexible assembly lines while keeping them efficient. An enabler for this is the harmonization of the approach to structural design, enabling the use of the same tools, assembly order, etc.

Let’s say that you want to produce washers and dryers on the same assembly line. This would be a clear motivation to include them in the same product architecture, sharing as many of the underlying module systems and interfaces between them as possible.

Using the same way of illustrating the product architecture for washers and dryersA shared system for control and communication could also be used across other home appliance products, including hardware and software for IoT, controls, etc.

Final Words

In this blog post I have defined product architecture as a system of modular systems. To me, this is one of the most important realizations a company must have to enable the maximum efficiency of modularization. In my previous post, What makes a Good Modular System, I have suggested a schematic model to understand how to scope profitable modular systems. I will soon continue this series of blogs with a discussion around how to design a winning modular system based on customer values, applications, and supply chain strategy.

Why Modular Design?


Tobias Martin

Vice President & Partner


Volkswagen pictures courtesy of Volkswagen Group AG.

Why module design?

Why Modular Design?


Does your product design methodology support your company strategy​?

Most companies today are operating in multiple market segments and regions where customers demand unique products customized to their preferences with a steady stream of new features and performance.

Companies are also looking across their established internal silos to find ways to improve the performance for their organization. 

The challenge is to simultaneously meet the market demand of mass customized products while cutting internal costs, complexity, lead times and time to market.

In this insight paper Luther describes the difference between Traditional Design and Modular Design methods, with suggestion on how you can implement modular design in your product development process.

Luther Johnson

Customers want innovative products, fast. Companies want to make customers happy and be 21st century lean. So how does all that work? Modular Management delivers clarity, performance and customer centricity so clients can reduce complexity and accelerate value creation.


More readings

Guide To Agile Line Production

Guide How to Design for Fast Service


Edscha Trailer Systems


Product Architecture Power

In order to reduce the number of part numbers, while maintaining and growing the number of product variants, the team at Edscha Trailer Systems paid special attention to the primary mechanical system of the sliding roofs. 

They optimized the interfaces and modules that make up the hinges, rollers and rails. 

The result? 

What used to take 108 different component variants was reduced to 32 module variants connected through standardized interfaces.

The consistent implementation of modular platforms is one of our major strategic concepts for the future. The competence and know-how that Modular Management offers has been a great support for us when implementing changes of vital importance in the areas of R&D and manufacturing processes.

Anders Birgersson
Edscha Trailer Systems

Company Description

VBG, now part of Edscha Trailer Systems, was started in 1951 by an engineer, Herman Krefting, who had a passion for making improvements to traffic safety. He designed and patented a new truck coupling that greatly improved the attachment of trailers to heavy trucks. The business he started to manufacturer these couplings grew rapidly during the 1950’s and continued to grow over the years with the addition of new coupling products and new sales offices across Europe.

Today, the VBG Group is in the business of developing and manufacturing many different components for the heavy vehicle industry. It is comprised of four divisions that total $ 375M USD in annual revenue. Sales are direct to OEM vehicle manufacturers or to specialty truck body builders, and there are also retail outlets for aftermarket purchases.

The VBG Truck Equipment division is a leading supplier of coupling equipment for truck and heavy trailers. It has more than 50% market share for coupling equipment through VBG and Ringfeder brands. Customers are truck and trailer manufacturers and aftermarket body builders who assemble specialty vehicles from chassis they purchase from the manufactures.

The Edscha Trailer Systems division is a leading supplier of moveable enclosures for trucks and trailers. It has just below 50% market share for sliding roofs through the EdschaTS and Sesam brands. Customers include European trailer manufactures Krone, Wielton, Tirsan, Kässbohrer, Fruehauf und Berger along with truck body builders and aftermarket retailers. 

The Ringfeder Power Transmission division is a global market leader in mechanical power transmission niches within and energy and shock absorption for widely differing industries including construction, machinery, power and mining.

The Mobile Climate Control division is active in the market for climate control systems for buses, off-road, utility and defense vehicles. The division is focused on customized solutions in small to medium-sized series. Its solutions include heating, ventilation, air conditioning, and controls, as well as a wide range of associated components.

Business Description

Up through the 1980s, the company focused on improving and delivering the core set of trailer coupling products under a single brand name. In addition to the original couplings, they developed high quality fifth wheel attachments for semi-trailers and tow-bars for automobiles. Sales grew steadily over the years and they expanded with in northern Europe with new sales offices and more advanced manufacturing facilities.

In the 1990s VBG started acquiring other small companies to add to products and brands to their portfolio. They added complimentary products and new products to go after different markets. The complimentary products were aligned with existing products and they strived for synergy across the businesses and bottom-line cost savings.

With growth and acquisitions, VBG was faced with having to offer a large assortment of products into a relatively small market where the flow of orders was highly varied. Costs and lead times were on the rise due to the large number of different products and they had little to no ability to gain scale. The production of drawbar couplings was customer-controlled, and variations in the number of incoming orders were managed by re-allocating resources, working overtime, employing temporary personnel and maintaining high volumes of inventory to cover the peaks. VBG was having trouble keeping up with their competitors with offering the product features demanded by customers.

In 1993, VBG began a relationship with Modular Management. An initial modularity project was completed for the original truck couplers, and it succeeded in lowering total costs and reducing the number of unique parts and article numbers by 42%. A series of modularization projects were some of the major contributors to raise net profits. There was also a considerable reduction in lead-time that made it possible to deliver products to customers in Scandinavia within 24 hours

In 1997, VBG acquired Ringfeder who was a direct competitor for trailer couplings and also offered machine elements for power transmissions. By leveraging the Modular Product Architecture that was previously developed, VBG was able to quickly integrate Ringfeder couplers into the VBG product family gaining the efficiencies of a single product platform.

Edscha Trailer Systems

In 2005, the company increased its product diversification with the acquisition of Edscha Trailer Systems  and Sesam sliding roof systems for trucks and trailers. The company is the inventor of the sliding roof system for trucks and trailers with products that enable easy cargo loading from either the top or sides of a truck. The Sesam included the same types of products with lower price and performance. 

In 2009, the global economy reduced the overall demand in the truck market. Edscha Trailer Systems and Sesam were the hardest hit in the VBG portfolio when OEMs were unable to move inventory of trucks and trailers. Many fewer sliding roof systems were being installed. The lower demand had exposed the inflexibility of the product costs to the volume of production. 

Having been a recent VBG acquisition, sliding roof systems had not yet benefited from the creation of a Modular Product Architecture. Past success with implementing modular platforms gave VBG the confidence that this approach would be a viable solution for the cost challenges of this division. Edscha Trailer Systems ’s journey will be the subject of the remainder of this case story.

Typical Trailer Sliding Roof System offered by Edscha

Product Marketing & Management

For Edscha Trailer Systems it had become increasingly difficult to differentiate trailer systems products from competitors. On average, the market was conservative, and innovations required real changes in customer value and extra time for customers to adapt.

The marketing team at Edscha Trailer Systems identified a unique product offering for each model year. They decided what features and options would be offered to customers as standard products while special features could be developed upon request. The team was also balancing the two brands, Edscha Trailer Systems and Sesam, and inevitably they were offering some products with overlapping performance. 

Product Design & Engineering

Sliding roofs are a mature product line and there have only been incremental changes over the years. The engineering team was small and had never completed a large product development project. The annual change in product offering required only small design changes, and the team spent the rest of the year fulfilling customer requested options. They also spent a large amount of their time on solving quality issues. 

Product Operations

Portions of the products we assembled at the Edscha Trailer Systems  factory in the Czech Republic where purchased components for the sliding roofs were cut and riveted together. Other components were delivered directly to OEMs or to the retailers for assembly on the vehicles. Most components are sourced exclusively for the company from 140 different suppliers. In 2011, they produced approximately 30 000 to 35 000 sliding roof systems.

The consistent implementation of modular platforms is one of our major strategic concepts for the future. The competence and know-how that Modular Management AB offers has been a great support for us when implementing changes of vital importance in the areas of R&D and manufacturing processes.

Anders Birgersson
Edscha Trailer Systems (formerly VBG)

Modular Architecture Goals

By creating a Modular Product Architecture for sliding roof systems, Per Ericson sought to significantly reduce their overall costs and make the business more robust to downturns in the market. 

Per looked to combine Edscha and Sesam branded products into the same product platform. He was confident in the fact that VBG had realized many benefits in 1997 doing the same with the VBG and Ringfeder trailer couplers.

We are acting in a mature market with hard competition from both local and international players. Through a modular concept, we can increase our completive edge and work more efficient with a good profit level. Modular Management supported and guided us through the process from being a company with a large assortment with unique components to a modular structure with drastically fewer components. My opinion is that we would not been in the position to work through this process by ourselves. Modular Management’s support and guidance was needed and necessary to bring the project to a successful ending.

Per Ericsson
Formerly Edscha Trailer Systems, retired 2017

The Himalaya project was launched in January 2011, and the investment would all be paid back within 4-5 years after the product launch. The company looked to develop the underlying product architecture and then implement specific products via smaller projects that reduce risk and increase speed to market. The key performance indicators for the project included the following:

  • Meet customer´s various demands via increased configurability
  • Increase barrier for competitors by being an undisputed market leader
  • Be agile with faster time to market and reduced time to delivery
  • Reduce the number of unique components.

Revenue Growth

Edscha Trailer Systems sought to maintain their market share defending it from a new and growing competitor. This would be accomplished by offering additional, desirable product variants and a substantial reduction in average lead time to the customer.

Profitability Improvement


The downturn in the market was a harsh awakening for the company. They needed to make drastic changes to their product costs basis in order to remain solvent in the future. The overarching goal was to reduce the number of unique parts by 70%. These are parts that needed to be designed and managed within the supply chain system. With part number reduction, it was estimated that the number of different suppliers could be reduced by 70% and inventory costs would be reduced by 45%. Direct material costs would be reduced as well.

Business Results

By the end of 2013, Edscha Trailer Systems was already seeing the impact of their modularity efforts with trailer sliding roof systems. Even though the product had not yet officially launched, they were seeing the impact of decisions and efficiency improvements that had been made along the way. Backward compatibility allowed new components to work in old systems. 

Edscha Trailer Systems – enhanced profitability in continued weak market

Heading into 2013, the division expected the trailer business to perform positively and that demand would increase in the second half of the year. However, the market remained weak for much of 2013 and it was only toward the end of the year that an improvement could be seen. Despite this weak market, where growth in turnover for the division only amounted to 1 percent, Edscha Trailer Systems improved its profitability and its operating margin rose to 9 percent. Lower costs and more efficient processes contributed to this and the division expects to further improve profitability as a result of the launch of the newly developed generation of sliding roofs in the market in 2014. However, it is principally the result of the anticipated increase in turnover volumes due to the improved market situation that Edscha Trailer Systems will also produce the necessary growth. The main market driver over the next two to three years is primarily the clear need to exchange or replace the existing trailer stock in Europe.

I hold great hope and expect Edscha Trailer Systems, with its strong market position and newly developed products, to have a solid basis in 2014 to continue its journey towards long-term profitable growth

Anders Birgersson talks about the financial impact in the 2013 Annual Report

Future cost savings were also being booked as new contacts
were being negotiated with the smaller set of suppliers. Overall cost
reductions were zeroing in at 15%. This was very close to the initial estimate
by the team and Modular Management. Upon these early successes, the Edscha Trailer System division has already launched the development of another Modular Product Architecture
for the line of sliding roofs that are installed on tipper trailers. 

Product Marketing & Management

The market launch of the new product range will be coordinated with each customer and should be implemented within one calendar year.

In addition to key customers, the team performed a market study of 20 truck body builders and 130 end customers. They confirmed with customers that increased product variety and reduced lead time would be the key to maintaining their market share. They also discovered that product reliability, safety and fast open and close are the critical customer experiences they needed to deliver.

Through the development of the Modular Product Architecture, the marketing and product engineering teams have developed new ways of working together. They have created a strong connection between customer needs and the technical solutions provided within the product. They know very clearly what modules and components deliver significant customer value and prioritize their product development efforts accordingly.

Product Development Engineering

The clear product priorities allowed the engineering and design team to spread out the development effort over time. With limited resources and funds, the team could not develop the entire range of module variants in one large program. They first developed the underlying product architecture that would last over time and then some of the key common module variants. Then, they could space out the introduction of additional modules over time. In fact, the product could be launched while the team was still developing new modules variants. They planned to keep introducing new ones to support the ongoing need for product variety in the market.

Development time for new module variants was set to the following:

  • New module or important module variant is 12-18 months (requires prototype and field test)
  • New product update (module variant without prototype of field test) in 6 months
  • Customer adaption: hole pattern of minor change will take 1 month.

A long-term focus around modularity has been implemented in Edscha Trailer System’s design department. Specifically, the team is much better at designing for production and supply chain and is saving money down the line. Even if it makes the design effort a bit more complex, they are developing and maintaining interfaces that enable efficiencies within operations.

Product Operations

The impact to product operations could be estimated early on as the team negotiated new deals with their suppliers. With reduced part numbers they could plan for higher volumes, fewer suppliers, less inventory and lower costs. At the start of the project, the team predicted a certain reduction in direct material costs, and after the initial planning with suppliers, they were achieving a reduction very close to the original predicted figure. The number of suppliers was reduced from 140 to 40.

The benefits of a more efficient supply chain were being extended to the retailers. Many were planning to keep less stock on hand because they were getting shorted lead times from EdschaTS.


Modular Architecture in Action

In order to reduce the number of part numbers while maintaining and growing the number of product variants, the team at Edscha Trailer Systems paid special attention to the primary mechanical system of the sliding roofs. They optimized the interfaces and modules that make up the hinges, rollers and rails. 

What used to take 108 different component variants was reduced to 32 module variants connected through standardized interfaces.

39 Hinges Reduced to 4. 23 Rollers Reduced to 5.

44 Rails Reduced to 8

Anders Leine

Anders Leine



Business Transformation with Product Architecture



In the face of increasing complexity and aggressive competition, Sidel CEO Mart Tiismann decided to invest in a modular product architecture program. The results were remarkable.

Executive Summary

Sidel is the leading global provider of PET solutions for liquid packaging 

The company is market leader in blowing, filling, labelling, material-handling and line-engineering solutions for the beverage, food, home and personal care industries.

In 2010, Sidel was struggling with a complex assortment and high costs for order engineering.

Since the company sells both complete lines and individual subsystems, a relatively high degree of product complexity and order engineering can be expected. Yet the situation was made worse by a Sales culture of saying ‘yes’ to all market requests for customization, and this was more than a question of culture. The market needed more configurable solutions. 

While Sales was saying yes, Engineering and Supply were having a hard time delivering what was sold and the competition was heating up. Margins were under pressure, not least as the competition ate into the most lucrative customer segments, geographies and solutions. 

In the face of increasing complexity and aggressive competition, Sidel CEO Mart Tiismann decided to invest in a modular product architecture program. The results were remarkable:

  • 60% of solutions sold were now configure to order – up from 33%
  • 40% reduction in part numbers
  • 50% fewer new part introductions
  • 10% in reduced cost
  • >300% in product assortment configurations
  • 30% reduction in total cost of ownership
  • 50% shorter order to delivery lead time
  • 30% shorter time to market
  • 80% reduction of engineer to order hours.
Mart Tiismann

As CEO of Sidel, I learnt that it’s possible to transform a business by connecting products, customers and organizations. Modular product architecture and information management tools made it possible.

Mart Tiismann, Former CEO of Sidel Group

Full Case Story


In 2010, Sidel had 5 300 employers and a turnover of EUR 1 400 million. 

The company ran engineer-to-order operations at many of its 26 plants for liquid bottling, blowing, filling, capping, labeling and conveying solutions.

Sidel’s product portfolio includes both entire lines and subsystems, with all the products needed for packaging liquids: blow molding machines, fillers, conveyors, labellers, pasteurisers, palletisers, depalletisers, robotic equipment, end–of–line operations, service and spare parts. 

Sidel’s systems are innovative, large, complex and high precision. They are built from expensive materials, demand big and costly spare parts, and run at high speed with high tolerance.

In 2010, the high degree of order–engineered custom products was resulting in lots of customization in production. In fact, every third product had some type of new feature or design.


In ‘The Discipline of Market Leaders,’ Treacy and Wiersema present three value disciplines: Operational Excellence, Customer Intimacy and Product Leadership. This is the transformation model Mart Tiismann focused on together with Modular Management’s Alex von Yxkull and Alex Ginsburg.

Both challenges and targets for the Sidel modularization program were structured according to the value discipline model with the goal of reducing costs, increasing market share and increasing price premiums.

Sidel’s business challenges were analyzed and summarized as reasons why the company wanted to initiate a modularization program. Each challenge was allocated to a specific value discipline.

Treacy and Wiersema's Value Disciplines

Product Leadership

  • Need to focus more on innovation – and less on redesigning parts – to regain market leadership.
  • Cross–fertilization and use of innovation partners will demand a modular product architecture and defined interfaces
  • A solution range based on derivates of a standardized base model will leave too many holes and unpredictable complexity costs.

Operational Excellence

  • Too many parts and too many suppliers make systematic improvement impossible
  • Unstable designs make a truly global supply chain impossible
  • Complexity costs are much higher than understood.

Customer Intimacy

  • Standardization of the product offering does not work
  • Order engineering is too slow and expensive.

The next step was to set clear goals.

Goals for the Modular Architecture

Goals for the architecture development program were set according to the same value framework as the challenges.

Product Leadership

  • Improve technology leadership
  • Reduce time to market 
  • Improve performance, primarily speed of new product introduction and improved total cost of ownership.

Operational Excellence

  • Reduce lead times 
  • Reduce complexity costs through fewer parts needed
  • Enable the splitting of design, sourcing and assembly across different geographical locations
  • Enable increased reuse and reduce customer–specific engineering
  • Improve quality.

Customer Intimacy

  • Enlarge the product offering
  • Better serving the increasing variety of customer requirements
  • Enable the development of services.

Liquid Packaging Line

Program Scope

The scope of the modularity program was Fillers, Blowers, Conveyors and Labellers and focused on:

  • Need for market-driven variance and development
  • Complete line configurations, harmonization and balancing of performance
  • Equipment internal modularization and compliance to complete line interfaces
  • Additional focus on control systems (complete line and equipment)
  • Process and information management for maintaining modular products
  • Process and information management for configure-to-order.


Product Configurations

Sidel’s new modular product architecture included the building blocks, or module variants, needed for a better and bigger product assortment. Product–specific results included:

  • More solutions on offer, including triple the number of blower products
  • More options available on more products, thanks to standardized interfaces
  • Aligned product ranges, with specifications defined at complete line level
  • Three conveyor ranges were moved to one architecture, leading to better performance and a higher degree of configurability – without increasing complexity – and 30% fewer new part numbers.

Previous Conveyor Range

New Modular Matrix Conveyor Range

Business Results

The business results were even more remarkable:

  • 60% of solutions sold were now configure-to-order – up from 33%
  • 40% reduction in part numbers
  • 50% fewer new part introductions
  • 10% in reduced cost
  • >300% in product assortment configurations
  • 30% reduction in total cost of ownership
  • 50% shorter order to delivery lead time
  • 30% shorter time to market
  • 80% more engineering hours available for new product development.

As CEO of Sidel, I learnt that it’s possible to transform a business by connecting products, customers and organizations. Modular product architecture and information management tools made it possible.

Mart Tiismann, Former CEO of Sidel Group

Configurable Construction Systems


How to Improve Productivity in the Construction Industry?

By Måns Ridzén & Tobias Martin

Construction has a hard time to match the productivity of other industries. 

Although there have been multiple phases of industrialization, these changes have had varying degrees of success. And despite efficiency gains, the construction industry remains relatively traditional. 

For example, despite the promise of prefabrication to deliver higher quality at lower cost, there’s an evident risk that product quality is sacrificed for process efficiency. And even these process benefits can be questioned compared to improved on-site production methods.

What’s clear is that construction companies are looking for ways to improve productivity. 

What’s also clear is that there’s not a one-size-fits-all solution. 

Configurable Construction to Meet Stakeholder Needs

Industry stakeholders want different things and these differences are driven by location and climate, regulations, respect for local traditions and the balance between the needs of construction companies, real estate owners and consumers.

This variety of needs is well suited to a modular approach, where different modules can be interchanged and rearranged thanks to standardized interfaces. The result is a construction system that can be configured to meet the needs of the market and provide solutions to satisfy all stakeholders.

Configurable construction systems can add value for construction companies and end customers through increased productivity, reduced lead-times and improved quality and product performance. This article looks at how companies can move from more traditional, custom-crafted construction to a configurable, truly industrialized system that meets all stakeholder needs.

From Custom-Crafted to Configurable

Start With What Delivers Value

Before starting out on a journey to create a configurable system, it’s important to set clear targets and plan how to reach them. These targets must be set specifically for your organization and will depend on company strategy, legacy and starting point.

Some companies see competence limitations in construction design as one of the biggest risks, and therefore set design re-use and CAD-automation as one of the main targets for their construction system. Others focus on direct material savings, quality improvements, value add for customers or digitalization. Successful companies understand what to focus on, how to set targets and how to connect them to actionable KPIs.

If the scope is wide, there will be reason to question whether it’s possible to select one technical or process solution for the whole range. For example, in a high-value segment a standardized kitchen setup might be used to enable a high degree of prefab. But in a high-price segment, the end customer wants more freedom to design the kitchen, including cabinet interiors, pushing the variance point later in time, pushing down the possible prefab degree.

One of the biggest long-term effects of utilizing a construction system is to be able to improve it continuously over time. Project-based businesses traditionally have a hard time to close feedback loops and continuously improve the product over time. Instead, there’s a risk that the wheel is reinvented in each new project. Construction is project based by nature, but this does not stop the central definition and governance of a construction system.

From Project Based to Configuration Based

Avoid Pitfalls

While the potential value is great, if you approach a new construction system from the wrong angle it can lead to big problems. Even when interfaces are in the right position and module variants are specified according to market demands, value will not materialize unless your processes, IT-systems, suppliers and company culture are adapted and aligned.

If strategies are not aligned properly, and not incorporated into the construction system itself, there will be a gap between company vision and implementation. 

Experience suggests that many companies fail to properly assure that the construction system is flexible enough to be used in construction projects with different needs, thereby forcing projects to depart from set interfaces. Other companies risk focusing more on internal needs than the needs of end users, resulting in poor product performance. If you don’t attack these issues head on, your investment in productivity improvements is likely to fail.

Configurable Construction Systems and Prefab

A common misconception is that moving to prefabricated construction elements is the same thing as implementing a construction system. 

The choice whether production should be located onsite or offsite is part of the construction system’s supply chain strategy, and it’s not clear that a bigger prefabricated share will help realize productivity improvements. For example, market requirements, such as flexibility and late customization, may drive production activities to onsite. 

It’s important to carefully match product flexibility with process capability and customer value. For example, customization that generates significant customer value can be be made onsite, while other elements should be optimized for efficiency and prepared offsite.

A construction system should rather be defined as a system prepared for configuration. 

The first step is technology selection, i.e. standardizing on a specific frame system or multiple systems depending on market requirement. The second step is to have predesigned parts that are configured into a building. The higher the degree of centralized preparation, the less work needed in the design of each building. In reality, different parts of the building system will have different levels of preparation depending on the market challenge. Following this, the level of prefabrication can be optimized for each part to reach efficiency and configurability targets.

How Prefabricated Construction and a Construction System Work Together

How to Start?

Construction has some of the most complex and extensive products of any industry, varying from large buildings to huge infrastructure projects. One of the earliest and most important decisions is how to scope the construction system.

A building is a complex system made up of numerous sub-systems structured in multi-layered hierarchies. Dependencies between sub-systems and variance of execution between projects drive complexity in the design, production and maintenance of a building.

Even if the long-term vision is to have all or at least most of the building’s sub-systems as part of a construction system, it makes sense to slice things up in bite size pieces. Before digging into each sub-system, you can benefit from analysing the current state and identify which sub-system has most potential in relation to investment needs. This enables you to plan the overall journey to a configurable system and materialize that potential in iterative steps, starting with the part of the product that will give most return on investment.

Industry Disruption: Risk or Opportunity?

New actors tend to disrupt markets and leave established actors behind if they fail to adapt. The construction industry is likely to see an increasing level of disruption in the coming years, especially in some markets.

Decentralized production, complex permit processes, exposure to economic cycles, competence shortage and a multifaceted legacy are just some of the challenges facing the industry. What has been considered efficient before is no longer good enough. Industry specific conditions has held the industry back from some of the technological and organizational advances seen elsewhere.

As innovation continues at speed, we’ve reached a threshold where systems, technologies and processes can deal with the needs of the construction industry, and we’re seeing how leading organizations are adopting. Companies that find the balance of when and what to invest in will be greatly awarded, even if it’s a fine line and there are several uncertainties going forward. Whatever the right path is, you will have to be fast, flexible and efficient, which makes an investment in a configurable construction system important. Configurable construction will enable you to meet different stakeholder needs, stay on top of market trends and keep your organization together.

In the near future we’re likely to see new constellations of vertical integration. Larger construction companies will take a life cycle management approach to buildings, where the second and third tenant is a new customer. And this places new requirements on the construction system, with stable interfaces for future upgrades, and on the information management systems needed to handle the lifecycle perspective of the buildings.

The construction industry is changing fast and a construction system that can be configured to meet changing needs could well be a prerequisite for success. Either you adapt as competitors set the framework for the future or you lead the change.


Configurable construction systems can add value for construction companies and end customers through increased productivity, reduced lead-times and improved quality and product performance.

Måns Ridzén,
Modular Management


This is the world-class solution for product management.

Standing for Product Assortment Lifecycle Management, PALMA is cloud-based strategic software to create, document and govern modular product architectures. With this unique structured approach you can design and document product architectures. You can also connect enterprise systems and secure business goals.

Built on an in-memory database platform, PALMA is faster and more capable than anything else on the market, so you can create configuration rules without coding, govern product architecture life cycles and create a business advantage.


Governance and Modular Transformation


How to Transform Your Organization?

Susanne Flyckt Sandström, President of Modular Management Sweden, looks at how to transform your organization and realize the full value of modularity. 

By focusing on key success factors  such as roles and responsibilities, decision models, core processes and information management  you can align your organization, reduce complexity and accelerate value creation.

Susanne, How do You Look at Governance?

For me, governance is crucial to realize and sustain value.

The challenge with modularity is not only to create the product architecture, but to live modularity and that starts at the top. Top management already understands the importance of governance, but needs to adapt leadership skills, decision models and communication in order to connect the organization.

We know that companies that focus on governance early on in the modular journey will be more successful. If you don’t, the sad thing is that even with the best product architecture in the world, you may well lose control and see complexity start to increase once more – and then your investment will be eroded.

What are the Main Challenges?

It’s quite easy to see the value of going modular and to imagine what the product architecture will look like. You also often know which people and resources you need. 

A trickier question is: “How can I get my management team knowing and living the modular way?” 

This includes how knowledge can be spread throughout your organization in terms of roles and responsibilities and decision making – as well as softer areas like collaboration, communication, ways of working, new domains of responsibility and lost domains where individuals feel like they’ve been dethroned.

It’s a lot about empowerment and alignment.


What’s Your Personal Experience of Doing This?

I’ve led many organizations through transformation journeys and change programs. 

It’s more about doing what you need to do, rather than saying what you need to do. It’s more legwork than management meetings; but you also need to have a governance model in place before being able to walk the talk.

You also need to have patience, and in big organizations you need to say and communicate things thousands of times before you can start to see change happening. I think it’s crucial to start thinking at the very beginning about how you can make this journey with the organization directly; and not just by putting together a small group of people to create a theoretical model.

How Can Structured Governance Reduce Complexity?

If you’ve taken the decision to go more modular, you need to build a governance model. 

If you don’t, or try to fit your existing model to this way of working, all the creation and implementation effort and impact will be diluted. This means you’ll see complexity starting to increase again, and you won’t be able to realize the value that you know is in the product architecture.

At Modular Management we offer a structured method for Governance and Modular Transformation. It involves assessment and improvement in key focus areas.


What Opportunities Does This Represent?

Structured governance enables you to realize and sustain value creation, but it also creates a culture of cooperation in the company, necessitating cross-functional teams and creating a common language for all units. 

Lots of people will meet new colleagues, which in itself speeds up the creation of the architecture, and people start to communicate with each other in a new and structured manner. This really generates a lot of positive energy inside and outside of your organization.

For example, in a situation where you’ve bought and merged companies, there are probably many different entities that don’t ever meet or work together. A well-governed modular product architecture is an excellent arena for connecting a company. You start to think about how innovation and new features from engineering will impact sales; how production will impact R&D; and so on. This is very, very positive, not least because it’s driven by your strategy and the needs of end customers.

Contact me via the button below if you’re curious to find out more.


If you’ve taken the decision to go more modular, you need to build a governance model. If you don’t, or try to fit your existing model to this way of working, all the creation and implementation phase effort and impact will be diluted.

Susanne Flyckt Sandström,
President, Modular Management Sweden

PALMA® Software

This is the world-class solution for product management.

Standing for Product Architecture Lifecycle Management, PALMA is cloud-based strategic software for you to create, document and govern modular product architectures. With this unique structured approach, you can design, document and configure products. You can also connect enterprise systems and secure business goals.

Built on an in-memory database platform, PALMA is faster and more capable than anything else on the market, so you can create configuration rules without coding, govern product architecture life cycles and create a business advantage.



By Karl Bråtegren


How to Avoid Roadblocks?

Karl Bråtegren, Senior Manager at Modular Management in Stockholm, shares some thoughts on software modularity and how to avoid roadblocks.


What is Software Modularity?

Software modularity is the decomposition of a program into smaller programs with standardized interfaces.

Microservices is a hot trend right now, and it’s essentially about small modules that are built into a whole software system. Spotify and Netflix talk about how they work with microservice architectures, and before this there was a similar trend called Service-Oriented Architecture (SOA) that targeted bigger modules.

Software modularity pretty much shares the same definitions as hardware modularity, with strategically- and functionally-clean modules that are driven by customer needs and share standardized interfaces. You basically allocate different functions to software modules and then implement them in source code.

A common way of referring to interfaces between software modules is Application Program Interfaces (APIs). For example, Google and PALMA expose APIs to the external world, and when you create software modules it’s like creating APIs within the product.

Why is This a Hot Topic?

The main driver is that software is rapidly becoming a bigger part of many products.

Software is delivering on the most important customer values and companies need to be much faster in development to stay ahead of competition. With modularity you can secure product leadership with separate modules that can be developed quickly without being locked into a complex web of other software functions. Basically, you can avoid roadblocks.

A second driver is ‘hardware portability’, a topic that many clients are looking at right now.

Hardware portability means that you want to be able to move the software solution from one hardware to another, enabling you to easily change hardware supplier. Electronics like PCBs, for example, can reach end-of-life quickly and you need to replace them. You also want to take advantage of better and cheaper hardware when it becomes available. If you have inflexible, over-dimensioned software that doesn’t scale well with the hardware, it makes it very hard to move the solution to a lower performance piece of hardware. With the right modules in place, you can isolate hardware impact to specific modules and enable hardware scalability and portability.

A third driver is that you can’t do everything on your own.

You want to make use of open source and leverage third-party specialist expertise. It’s much easier to plug in third-party software, for example navigation and vision processing, into a modular architecture than a monolithic one. You would in this case aim to create modules with the aim to source them from a strategic partner.

What’s Your Personal Experience of This?

We’ve recent client experience, but an older example is when I worked as Product Manager at Siemens Mobile Networks. This was back in the old days of Wireless Application Protocol (WAP), General Packet Radio Services (GPRS) in mobiles and slow networks.

At Siemens we didn’t have a WAP proxy to sell to operators and wanted to launch our own product. What we did was to partner with an American company that had a proxy server with compression technology, and they then made their APIs available to us. Using these APIs we could develop services aimed at the cell phone service providers and make a viable and attractive solution. We also discovered that we needed a WAP protocol stack, so we found a Finnish company with a commercially available WAP-stack that we could plug into.

This is a practical application of our strategic sourcing driver from the Module Indication Matrix (MIM), but at Siemens we didn’t think much about it back then. We just bumped into challenges that had to be solved and found a way to solve them with strategic partners.

What are the Opportunities for Companies?

There are many reasons to invest in software modularity, but it’s basically about being fast and flexible. By developing new features faster, and more frequently, you can provide new software and hardware products that better meet customer needs.

You can also work with the continuous release of new features, while maintaining quality and not putting product reliability at risk. In an integrated or monolithic architecture, there’s a risk that when you introduce a new feature update the whole product goes down. If it’s a robot, for example, this means the whole line stops. Even if the update feature is quite small, like a nice new Graphical User Interface (GU), customers will be scared – or won’t even dare – to update if it’s in a big monolithic package. This has been a real issue and in some cases it still is.

Without a flexible, modular software you have a slower development pace, more bugs, more testing issues and more time to release. You’re also forced to live with old and expensive hardware and run end-of-life hardware projects, often in panic mode.


What is Modular Management Able to Offer?

We’re able to offer a unique approach in Modular Function Deployment® (MFD) which solves many of the challenges mentioned earlier.

I haven’t seen any other structured approach that explains how you should think if you want to move to microservices or a more modular software architecture. There are rules of thumb in the software world, like separation of concerns, but there is no real method like the one we have.

MFD is unique because it takes customer values into account. This is extra important for software, because for a lot of modules you don’t need parallel variants of the source code, you just need to increase speed in delivering on certain customer values. In other words, you need to rapidly bring out new versions of these modules.

With MFD you can also consider company strategy up front, for example hardware portability, strategic sourcing, carry over and technical specification. One scenario is that when you offer integration capabilities to the external world you may need different protocol stacks. An example of this is to offer many different industrial Fieldbuses (ProfiNet, EtheNnet/IP, DeviceNet…). They will typically come with their own variants of the code. This is an example of when we would apply technical specification as a strategic driver. In the end, this could be enough reason to create a module for the Fieldbuses.

Many of our clients typically have good technical software architects. Architecture is a skill that’s important when you work with software because it’s so abstract. You don’t have brackets and pumps to touch and feel, so software architects are typically comfortable in talking in functions and working with architecture diagrams. But they often overlook customer values and strategies, or at least don’t have a systematic method to approach these critical drivers and how to reflect them in the architecture.


Any Final Thoughts?

I’ve heard software architects say that it’s more difficult to describe exactly what you mean when it comes to software, just because it’s so abstract. You also have a very high degree of freedom in implementation since you’re not bound by physics.

This level of freedom makes it easier to circumvent the architecture during implementation, so it’s always important to go back to why you defined a module and make sure it’s implemented accordingly. That’s where we come in. 

For more information, contact me via the button below.


As software architecture can easily be circumvented by the coders, it is important to repeatedly go back and look at the reasons why certain functions were grouped into modules.

We have done software modularity before, but this time we factored in customer values and strategy. I believe this makes our new architecture much stronger.

Roger Kulläng
Global Software Solution Architect ABB Robotics

There are many reasons to invest in software modularity, but it’s basically about being fast and flexible. By developing new features faster and more frequently, you can provide new software and hardware products that better meet customer needs.

Karl Bråtegren
Senior Manager
Modular Management


This is the world-class solution for product management.

Standing for Product Assortment Lifecycle Management, PALMA is cloud-based strategic software to create, document and govern modular product architectures. With this unique structured approach you can design and document product architectures. You can also connect enterprise systems and secure business goals.

Built on an in-memory database platform, PALMA is faster and more capable than anything else on the market, so you can create configuration rules without coding, govern product architecture life cycles and create a business advantage.