scholarly journals Externalizing tacit overview knowledge: A model-based approach to supporting design teams

Author(s):  
Tomás Flanagan ◽  
Claudia Eckert ◽  
P. John Clarkson

AbstractSuccessful realization of large-scale product development programs is challenging because of complex product and process dependencies and complicated team interactions. Proficient teamwork is underpinned by knowledge of the manner in which tasks performed by different design participants fit together to create an effective whole. Based on an extensive industrial case study with a diesel engine company, this paper first argues that the overview and experience of senior designers play an important part in supporting teamwork by coordinating activities and facilitating proactive communication across large project teams. As experts move on and novices or contractors are hired, problems are likely to occur as tacit overview knowledge is lost. If informal, overview-driven processes break down, the risk of costly oversights will increase, and greater management overhead will be required to realize successful product designs. Existing process models provide a means to express the connectivity between tasks and components thus to compensate partially for the loss of tacit overview. This paper proposes the use of design confidence, a metric that reflects the designer's belief in the maturity of a particular design parameter at a given point in the process, to address the limitations of existing models. The applicability of confidence-based design models in providing overview, as well as their shortcomings, will be demonstrated through the example of a diesel engine design process. Confidence can be used to make overview knowledge explicit and convey additional information about the design artifact, thereby informing communication and negotiation between teams.

Author(s):  
C J Barnes ◽  
G E M Jared ◽  
K G Swift

An assembly-oriented design system has been developed which includes several analysis tools to improve product assemblability during product development. One of these tools supports the parallel development of the product design and the assembly sequence, thus exploiting the benefits of concurrent consideration of product and process. However, this approach requires some method for evaluating the sequence against requirements. Previous work on assembly sequence evaluation has concentrated on identifying the best from a set of ranked alternatives. When a single sequence is constructed, as with this tool, another method is needed. This paper reports the development of this novel methodology for evaluating individual assembly sequences. A review of the relevant literature has found several measures for identifying good assembly sequences from a ranked list and the fundamental sequence attributes extrapolated and aggregated. This leads to the proposal of four new indices: insertion index, stability index, difficulty index and complexity index. A large number of assembly sequences have been analysed to define limiting values for the indices such that they can quantify the potential of an incomplete sequence resulting in a satisfactory solution. The application of these indices in concurrent design and assembly planning is illustrated through an industrial case study.


Author(s):  
Nicole Zero ◽  
Joshua D. Summers

Abstract Current research and literature lack the discussion of how production automation is introduced to existing lines from the perspective of change management. This paper presents a case study conducted to understand the change management process for a large-scale automation implementation in a manufacturing environment producing highly complex products. Through a series of fifteen semi-structured interviews of eight engineers from three functional backgrounds, a process model was created to understand how the company of study introduced a new automation system into their existing production line, while also noting obstacles identified in the process. This process model illustrates the duration, sequencing, teaming, and complexity of the project. This model is compared to other change process models found in literature to understand critical elements found within change management. The process that was revealed in the case study appeared to contain some elements of a design process as compared to traditional change management processes found in literature. Finally, a collaborative resistance model is applied to the process model to identify and estimate the resistance for each task in the process. Based on the objective analysis of the collaborative situations, the areas of highest resistance are identified. By comparing the resistance model to the interview data, the results show that the resistance model does identify the challenges found in interviews. This means that the resistance model has the potential to identify obstacles within the process and open the opportunity to mitigate those challenges before they are encountered within the process.


2018 ◽  
Vol 49 (6) ◽  
pp. 64-77 ◽  
Author(s):  
Torgeir Dingsøyr ◽  
Nils Brede Moe ◽  
Eva Amdahl Seim

Software development projects have undergone remarkable changes with the arrival of agile development approaches. Although intended for small, self-managing teams, these approaches are used today for large development programs. A major challenge of such programs is coordinating many teams. This case study describes the coordination of knowledge work in a large-scale agile development program with 12 teams. The findings highlight coordination modes based on feedback, the use of a number of mechanisms, and how coordination practices change over time. The findings can improve the outcomes of large knowledge-based development programs by tailoring coordination practices to needs over time.


AAPS Open ◽  
2021 ◽  
Vol 7 (1) ◽  
Author(s):  
Madalena Testas ◽  
Tiago da Cunha Sais ◽  
Leonardo Piccoli Medinilha ◽  
Katia Nami Ito Niwa ◽  
Lucas Sponton de Carvalho ◽  
...  

AbstractThe use of a Quality by Design (QbD) approach in the development of pharmaceutical products is known to bring many advantages to the table, such as increased product and process knowledge, robust manufacturing processes, and regulatory flexibility regarding changes during the commercial phase. However, many companies still adhere to a more traditional pharmaceutical process development—in some cases due to the difficulty of going from a theoretical view of QbD to its actual application. This article presents a real-world case study for the development of an industrial pharmaceutical drug product (oral solid dosage form) using the QbD methodology, demonstrating the activities involved and the gains in obtaining systematic process and product knowledge.


2018 ◽  
Vol 99 ◽  
pp. 21-40 ◽  
Author(s):  
Muhammad Usman ◽  
Ricardo Britto ◽  
Lars-Ola Damm ◽  
Jürgen Börstler

Author(s):  
Beshoy Morkos ◽  
Shraddha Joshi ◽  
Joshua D. Summers ◽  
Gregory G. Mocko

This paper presents an industrial case study performed on an in-house developed data management system for an automation firm. This data management system has been in use and evolving over a span of fifteen years. To ensure the system is robust to withstand the future growth of the corporation, a study is done to identify deficiencies that may prohibit efficient large scale data management. Specifically, this case study focused on the means in which project requirements are managed and explored the issues of perceived utility in the system. Two major findings are presented: completion metrics are not consistent or expressive of the actual needs and there is no linking between the activities and the original client requirements. Thus, the results of the study were used to depict the potential vulnerability of such deficiencies.


Sign in / Sign up

Export Citation Format

Share Document