To capture the system architecture of the MCM context model with a matrix-based modeling approach, its elements are considered different domains, which can comprise several sub-domains. Together with their dependencies, these eight domains form the general system
3 In principle, a merger of MCM and ECM is conceivable combining both change processes to a joint Engineering and Manufacturing Change Management. Thus, the increasingly strong link between product and factory system could be reflected on a process level leveraging potential synergies of both Engineering and Manufacturing Changes. In the years 2016 to 2019, two sub-projects of the CRC 768 address this topic with the development of a so-called Systemic Change Management.
Engineering Change Management Manufacturing Change Management
Change cause
Factory
Product impacts
leads to
triggers
Process support
produces
impacts leads to
identifiesidentifies requires/ demands
Manufacturing Change
Engineering Change MCM process
manages
ECM process creates / becomes
manages
creates / becomes adapts
adapts
provides information
Figure 5.1: Graphical illustration of the MCM context model
architecture and are modeled with an MDM (cf. section 2.5.4). Subsequently, the sub-domains are considered in more specific MDM models of the MCM context model (see section 5.3).
The resulting, non-modified 8x8 MDM visualizes the general system architecture of the con-text model (see figure 5.2). Starting with the domain change cause, two main sections (MCM and ECM) can be distinguished having the domain process support in between. Compared to the graphic illustration of the context model, the MDM depicts the specific dependencies between the eight domains more clearly. Also, it provides first insights into the sub-structure of the eight domains4and fosters the systemic understanding of MCM.
Based on the definitions derived in sections 2.1 to 2.4 and findings from literature and industry, the eight domains are described as domain models including their scope, their dependencies, and their relevance for the intended MCM approach.
4 On the diagonal, empty fields indicate a domain consisting of different sub-domains, while fields containing a dependency indicate a domain to consist of associated elements only.
relates to triggers leads to triggers leads to
becomes tailors affects impacts selects
becomes selects tailors affects impacts
Figure 5.2: MDM of the general system architecture of the MCM context model
Change cause
This domain includes the relevant areas, where events or triggers for either an EC or an MC potentially occur (cf. section 2.1.1). It triggers the MCM process (or the ECM process respectively). As the origin of any change, this domain is considered to have a fundamental relevance for MCM (and ECM) – i.e., it is considered a core element of MCM; its numerous dependencies to the other domains further add to this.
Manufacturing Change
This domain describes any change that occurs within a factory (cf. section 2.1.3) and comprises relevant attributes to specify an MC (cf. 3.2). These attributes are not necessarily independent and might affect each other (e.g., the duration of a change might influence the costs). MCs are subject of any MCM activity, impact the factory, and might create or become change causes themselves (this phenomenon is generally referred to as “change propagation” (cf., e.g.,
CLARKSONet al. 2004, PLEHN et al. 2016a). Also, MCs could be used to tailor the MCM process and select relevant roles based on their attributes (cf. section 4.2). Overall, this domain is highly interrelated to the other domains, especially to the MCM process. Hence, it represents one of the core elements of MCM.
MCM process
This domain substantiates the process-orientation of MCM and describes a reference procedure to manage changes in manufacturing (cf. section 2.4.3). According to the modeling approaches selected for the MCM process design (cf. section 2.5.4), the domain comprises stages and gates for a high-level understanding and controlling, and activities and deliverables for a homogeneous, detailed understanding and description through PAF.
– Stage: Section or phase that comprises a set of activities
– Gate: Closure of the previous stage and “entrance” to the subsequent stage; comprises a set of deliverables
– Activity: “Constituent element of a process system. [. . . ] packages of work to be done to produce results [. . . ]” (BROWNINGet al. 2006, p. 117; cf. section 2.5.4)
– Deliverable: “[. . . ] represent any information, data, result, material, etc. produced or required by an activity” (BROWNINGet al. 2006, p. 117; cf. section 2.5.4)
The MCM process is applied to identify change causes and to manage MCs. Also, it can be triggered by a change cause, tailored by an MC, and provides information to the ECM process if required. Due to these numerous dependencies and its inherent importance for the process-orientation of MCM, this domain represents the core of MCM.
Factory
This domain describes the grouped production factors fulfilling a defined part of the value stream to produce a tangible item – the product. For MCM, four different sub-domains are considered relevant to be subject to an MC.
– Factory system: Comprises “the spatial arrangement, relations, and properties of a technol-ogy, personnel, and infrastructure in a differentiable subsection of a manufacturing plant, where the system boundary should be drawn depending on technological or product-oriented deliberations.” (PLEHNet al. 2015)
– Manufacturing processes: Especially production and assembly procedures, but potentially also other processes in a factory, for example, maintenance activities5
– Documentation: Documents, for example, for order control or machine documentation – Factory organization: For example, composition of assembly teams, job assignments, or job
shop and order control6
These four sub-domains proposed indicate the broad range of potential change objects within a factory and provide valuable input for detailing the attributes of the domain MC (cf. section 6.2). In addition, modeling the domain factory with its various facets promises great potential for further research on, for example, the changeability of a factory or the analysis of change impacts and change propagation in manufacturing.7 For further information about this field of research please refer to, for example, PLEHN et al. (2015).
The domain factory is impacted by MCs, produces products and can become or create a change cause due to, for example, aging equipment (which could require the exchange of manufacturing resources) or complications in manufacturing (e.g., quality issues leading to an adaptation of the manufacturing process or the equipment). It supplements information for the detailed development of the domains change cause and MC, but is not considered one of the relevant elements for the MCM process design having no relation to this domain.
Process support
This domain covers the supporting elements for the other domains of the MCM context model, especially the processes. It comprises two sub-domains considered relevant for MCM (cf.
section 1.4 and 4.2):
– Role: Comprises relevant roles to conduct MCM
– Method & tool: Comprises relevant methods & tools to support the different activities of the MCM process and the roles
5 The range of relevant processes might vary from company to company depending on the organiza-tional setup of the factory and the MCM.
6 This sub-domain relates to the listed organizational aspects in a factory, but not to changes of the whole or parts of the general organization. Those changes are addressed by Organizational Change Management (cf. section 2.2.3).
7 For this case or even other applications additional sub-domains might be supplemented or exchanged, if desired.
The sub-domain role is especially relevant to guide and simplify an implementation of MCM in industrial practice and to assign responsibilities. Method & tool is not necessarily required to develop an MCM approach, but is assumed to provide valuable information to practitioners to conduct MCM. Due to this supportive characteristic, this domain is also considered a core element for MCM (as well as for ECM).
Domains of the ECM section
The remaining domains of the context model – ECM process, EC, and product – are counter-parts of the respective elements within the MCM section and can be modeled similarly with the level of abstraction chosen for this research. The EC comprises relevant attributes and has dependencies to all other domains within the ECM section (cf. section 2.1.2). It impacts the product and can become a change cause leading to further Engineering or Manufacturing Changes. The ECM process (cf. section 2.2.1) can be modeled like the MCM process with the same sub-domains and similar relations. The product is a tangible item produced by the factory, which is a simple but sufficient definition for the purpose of this research. This domain comprises sub-domains such as components and documentation (e.g., drawings, part lists) and has similar relations like the domain factory. Overall, these domains have to be considered for developing MCM, especially regarding their dependencies to the domains change cause, MCM process and process support. Beyond this, an equally detailed design (as for the other domains) is neither intended nor required for the development of MCM.8