Specific models and options can be mapped to individual activities. The concept of Model-Option Mapping allows Assembly Planner to have a generic process routing that applies to a family of products, with the differentiating tasks (activities) mapped specifically to models (or options). This mapping is helpful when there are many shared activities across multiple models and/or options, because that activity must only be documented once but can be included multiple times in work instructions and in line balancing across all models and options to which it is required. For those activities that are unique to specific models and/or options, the mapping will define for which configurations the activities should be included and for which they should be left out. This model-option mapping can be done automatically through Automatic Model-Option Mapping or manually through Manual Model-Option Mapping.
When considering whether an activity applies to one or more models and/or options, consider what the task encompasses. If the task is the same process in terms of description, work steps, and duration, no matter where or when it is performed, it can be mapped to multiple models and/or options. Note: different part IDs can be consumed and different resource IDs can be mapped for different models and/or options, and the activity can still be considered the same activity.
Example: Manufacturing a Car.
A car can be a diesel model or a gas model or an electric model or a hybrid model. Each of these need different engines, different kind of fuel tanks, different kind of seats (simply, different options), etc. Based on the parts consumed in each of the activities (e.g. assembling a fuel tank) at a station, we map models and/or options to that activity (like a hybrid model needs both gas tank and battery as options) using this feature.
A few system preferences applying to this topic are important to note. These preferences cannot be changed manually within Assembly Planner, but your Proplanner Representative can help you determine which preference settings are best for your business practices and make sure the appropriate settings are applied to your Assembly Planner application.
Autobuild Preference: This affects which activities the Autobuild routines (see Automatic Model-Option Mapping) will perform the model-option mapping on. The default preference is set to 'True.'
If True, the Autobuild routine will ignore any activities with either no parts mapped in consumption or parts alone (without their parent parts) that have been mapped in consumption. This allows clients who want to do a combination of automatic and manual model-option mapping to retain the existing manual mapping, while automatically mapping models and options for the remaining activities.
If False, the Autobuild routine will clear all existing model/option mapping for every activity before remapping, which is based on the routine specifications. This preference option should be set if only automatic mapping will be used.
Process Configuration Preference: The inclusion of an activity in Line Balancing or reports with model/option filters is based on a preference setting. If the model/options in Line Balancing or report filters match the models/options on an activity, then that activity is included. Otherwise, that activity will be ignored.
The configuration preference determines the selection criteria.
If None is set, then all activities will be considered, irrespective of models and/or options being mapped to them. This follows the assumption that if no models/options have been mapped to an activity, that activity is performed on all models and options.
If Model or Option is selected, only activities that have a model and/or an option mapped will be included in a balance or report. This follows the assumption that if neither models nor options have been mapped to an activity, that activity is never performed. The data will be filtered further based on models and options selected in the line balance or report filters.
If Model and Option is selected, only activities with both model and options mapped will be included in a balance or report. This follows the assumption that if both models and options have not been mapped to an activity, that activity is never performed. The data will be filtered further based on models and options selected in the line balance or report filters.