Approach for the MC-specific adaptation

MCM process. The PAF provides three attributes for deliverables dedicated to process tailoring that are described in this section: modes, deployment, and tailoring guidance (cf.

section 2.5.4 and the appendix, table A.5). Each deliverable is defined to have up to three modes (available variants of a deliverable) – standard, optional, and extended. Also, any deliverable can be eitherindependent and fix ortailorable, which is described by the term deployment. The tailoring guidance covers instructions regarding tailoring – i.e., the process of selecting a suggested mode of a deliverable with respect to the values of the related MC attributes. For this research, the tailoring approach is designed as being conservative. That is, only simple MCs tailor deliverables to the modeoptional, more complex MCs tailor them to the modeextended.²⁰ Examples for simple changes are a correction of an assembly documentation,

19The focus of the proposed adaptation approach is on an enterprise-independent approach. It might be adjusted to account for company specifics and depending on the respective application scenario if needed.

20Optional: the deliverable is not required for this MC, but can be created;extended: a more detailed version of the deliverable is required for this MC (e.g., a more detailed impact analysis, a more detailed change plan).

or the installation of a new computer monitor for a work-station without further impact on the production. In contrast, more complex MCs like the installation of a new manufacturing resource or a factory layout change might have a high impact on the production process and on logistics.

Note, that the activities possess the same attributes for tailoring (modes, deployment, and tailoring guidance) and the same values of these attributes. Due to the one-to-one relationship of deliverables and activities, activities are considered to always be tailored the same as the deliverables are.

Roles.The roles are distinguished in MCM roles and department functions. MCM roles (e.g., change manager, change agent) are selected by default for any MC, because these represent the basic roles required to conduct MCM and process an MC. The involvement of roles for an MC depends on the tailored MCM process, as the roles are linked to the MCM process activities and deliverables (cf. figure 6.3.4). In contrast, the selection of department functions depends on the values of MC attributes. For example, if an MC is caused by a previous EC, the department functions Product Development, Product Life Cycle Management (PLM), and ECM should be selected to be involved during the MCM process; if an MC has an impact on the customer, the departments Sales and Marketing as well as Legal should be engaged.

Similar to the tailoring approach, also the selection of roles is designed as being conservative.

Roles are eitherstandard roles(the MCM roles), or selectable asrequiredor optional, but recommended(the department functions).

MC attributes. For both process tailoring and role selection, only selected MC attributes with their different values are required. The relevant attributes are all part of the category Characterization. The remaining either specify an MC in terms of achange IDor achange description, or relate to the MC and cross-MC comparison, coordination, and evaluation (see also section 6.2.2). Most of the characterization attributes are used for process tailoring and role selection; however, the attributecauseis linked to the department functions only, because the MCM process is considered independent from the change cause. In contrast, the attribute localization, which describes the change object (e.g., a manufacturing resource, a tool, or a document), relates neither to roles nor to the MCM process. However, it is considered to aid the selection of specific employees, teams, or responsibles within the different department functions. For example, an MC to a certain manufacturing resource might require the selection of a specific, but different person within the department functionProductionthan an MC to an assembly documentation.

Dependencies within the DMM.The dependencies between the MC attributes, the deliver-ables, and the roles finally describe the information necessary for process tailoring and role selection. Each dependency is modeled by providing the actual value required for a deliverable

h: high; m: medium; l: low; n: no a,b,c: different change causes

s1 _g1 s2 _g2 s3 _g3 s4 _g4 s5 _g5 … _…

n+

n+

Attributes

n+

a3.1 d3.1 a3.2 d3.2 a3.3 d3.3 a3.4 d3.4 a3.5 d3.5 a3.6 d3.6 a3.7 d3.7

n+ n+

di.j standard ^di.j optional ^di.j extended Deliverable modes:

Figure 6.21: Concept for the DMM of an MC and the MCM process deliverables (exemplary)

to be tailored or a role to be selected. A generalized version of the model is visualized in figure 6.21, complemented by the relevant rules and the notation. For the detailed DMM model please refer to the appendix, figure A.13.

The detailed information about the deliverables regarding modes and deployment is supple-mented to the PAF (cf. appendix, tables A.7 and A.6).²¹ Additional information about the roles can be found in section 6.3.4. The proposed modes, deployment, tailoring guidance, and dependencies between attributes and roles are intended to create a profound basis for a situation- and company-specific adaptation of the concept and might be supplemented or further detailed if required.

Rules and notation for process tailoring

– There is only a dependency considered between an MC attribute and a deliverable if the respective field in the DMM is filled. All deliverables are in mode standard as long as

21Note, that the relevant information on the tailoring guidance is provided within this chapter with the rules for process tailoring and role selection. If needed, this can be directly supplemented to the respective PAF attribute.

there are no values of MC attributes determined during the MCM process. If no entry exists within the DMM, a deliverable has solely the modestandard.

– If a deliverable is tailorable to the modeoptional,extended, or both, the required values of the MC attributes are specified in the column of the deliverable. If both are applicable, there are two columns provided for a deliverable. The left one relates to the modeoptional, the right one to the modeextended.

– Values marked byn,l,m, orh(abbreviation for no, low, medium, high) represent a sufficient condition and solely tailor the deliverable. They are applicable and valid for the respective or higher value levels of the attribute for tailoring toextended(e.g.,mis applicable for the attribute and valid in case the actual value of the attribute is eithermorh). For tailoring to optional, they are valid for the respective or lower values (e.g., lis applicable for the attribute and valid in case the actual value of the attribute is eitherlorn).

– Values marked byn+,l+,m+, orh+represent a necessary condition, and only a combination of attributes with these values tailors the deliverable.

– A deliverable remains in modestandardas long as the values of the MC attributes do not match the proposed entries within the DMM. Once a value of an attribute (or a combination of them) matches the entry within the DMM, the deliverable is tailored according to the aforementioned rules.

– In case an MC-specific tailoring causes an activity to have no dependencies to subsequent activities anymore, either a temporary dependency to the next non-tailored activity is to be supplemented or theoptionaldependencies apply.

For a detailed DMM model of the tailoring approach please refer to table A.13 in the ap-pendix.

Rules and notation for role selection

– There is only a dependency considered between an MC attribute and a role if the respective field in the DMM is filled. Only in this case, the role is selectable based on a value of an MC attribute; otherwise, the role is always a standard role.

– If a role is selectable asrequiredoroptional, but recommended, the required values of MC attributes are specified in the column of the role.

– Any values of an MC attribute other thanno– i.e.,l,m, orh– represent a sufficient condition for selecting roles. Relevant dependencies are marked byxfor selecting a role asrequired, or byopfor selecting it asoptional, but recommended. In any column, a dependency withx overrules other dependencies withop.

– More specific values of MC attributes are marked withxl,xm, orxhwith the same applica-bility and validity as regularx, but only applicable for values of the same or higher levels (for example,xmis only applicable, if the value of the attribute is eithermorh).