Blog entry by Phil Martin

Phil Martin
by Phil Martin - Tuesday, 12 June 2018, 8:43 AM
Anyone in the world

Have you considered how flexible your VC models are - or need to be?  Have you ever been asked to use your model in a new plant or country?

Recently for a new global rollout for SAP and VC, planning workshops were considering this point.  

Many companies are global and have VC Models for products that are similar. The challenge is to keep a global approach to the modelling, but provide flexibility to enable localisation for each region, country and plant.  The idea is to not reinvent the wheel in each location, but instead be able to plug and play with the design.

It is not easy to do, but good VC design approaches can enable a flexible model that promotes consistency and reuse.

By identifying what is common - no matter where the model is used, can be captured in the Type 300 class design.  By using multiple classes to define global characteristics and design, classes that define localisation aspects etc, this can provide a flexible structure to then hook the configurable materials.  

In this simple example there is a shared Global Class, and then for a region, a Local Class. 

Glabal and Localisation with classes.

This keeps a common design approach - no matter where the model is used.  Combined with a flexible multi-level BOM design (another topic) this provides a solid approach to make models flexible into the future.

In our Radiant Think VC Essentials course, we incorporate this approach in our lessons.  Many VC Courses, including those by SAP, do not implicitly incorporate design approaches as the foundation of their course materials.  The same applies to most "free" Youtube courses that you will find.  Other courses may teach you various techniques...but our course teaches the good practice approaches.

[ Modified: Tuesday, 12 June 2018, 9:34 AM ]
 

  
RSS