This research focuses on the use and implementation of Tecnomatix Plant Simulation (TX) at project and organizational level. The primary goal of this research was to develop a referable and holistic implementation strategy for TX software. Company A and Siemens for giving me permission to conduct an evaluative case study following the implementation of the Tecnomatix Plant Simulation software.
INTRODUCTION
- Background to the Research
- DES Software Evaluation & Selection
- Motivation for the Study
- Research Aim and Objectives
- Research Aim
- Primary Research Question and Objectives
- Importance of the Research
- Overview for the Research Study
In the second phase, a detailed evaluation and analysis is carried out for packages that meet the requirements in the first phase, and within this hybrid selection – industry case the extent of requirements and motivation. 2 References on strategy and application at the organizational level, include development and evaluation of utilization and incorporation of TX into corporate structures. Furthermore, a parallel leg will focus on the business case underlying all the projects.
LITERATURE REVIEW
Introduction
Discrete-Event Simulations (DES)
The system is further simulated by conducting experiments using computer implementation of the model and analyzed to conclude the model outputs that can help in the decision making process. DES remains one of the most effective decision support tools, but much needs to be done to address new challenges (Babulak, 2010). The strength of the handbook is the focus on operational and organizational issues that reflect different roles in connection with simulation.
Software and Technology Integration Strategies
- Information Technology (IT)
- Enterprise Resource Planning (ERP) Systems
- Project Management Office (PMO)
- Software Defined Networking (SDN)
- Overview of Strategies
One of the strategies for the successful implementation of large software projects is the establishment of a project management office. The return on investment for DES-type software is a CSF that requires quantification in parallel with the implementation of the software. Some of the PMO components will thus add advantages to strategy development at a modular project level.
Tecnomatix Plant Simulation (TX)
- Project Components
- Organisational Components
The simulation expert must formulate the requirements for the simulation together with the customer of the simulation. Depending on the objectives of the simulation study, the experiments based on a test plan will be realized. It is also important to define a period for the simulation experiments, based on the results of the test runs.
Feasibility Studies
- Business Process Models
- Traditional Requirements Engineering (RE)
- Pre-implementation Packaged Software (PS)
- TELOS
- Feasibility Study Process
- Need for Feasibility Studies
This incorporates all the other business components to integrate TX more effectively and successfully at the project and business level. In addition to this, other operational areas include determining the usability of the product, determining whether the proposed solution by the software development team is acceptable or not, etc. Feasibility studies are an important step in the Software Project Management Process because it provides a conclusion as to whether to proceed further with a proposed project (Jena, 2020).
Theoretical Framework Development
- Project Components
- Organisational Components
- Feasibility Model
- Strategy Development
The third component is the required training to meet resource capacity and project requirements. The last component consists of a phasing strategy as part of the overall strategy development, to achieve the most feasible and viable results. It should be noted that all of these components, as well as the project level components, will be an inherent part of overall strategy development.
Conclusion
METHOD
Introduction
Methodology
- Study Design
- Research Approach
- Study Context
In Kumar's view, 'the qualitative-quantitative-qualitative approach to research is comprehensive and worth considering'. The advantages of the case study methodology, which originates from Zainal (2007), include the examination of data carried out within the context of their use (Yin, 1984). The research study follows the selection method at case level and forms part of a generalized case study on the development of an implementation strategy for TX following the ADR approach.
Method
- Stage 1: Problem Formulation
- Stage 2: Building, Intervention, and Evaluation
- Stage 3: Reflection and Learning
- Stage 4: Formalisation of Learning
Project background – The applicant should provide a brief description of the project to give a relative idea of the project as a whole. Support Request – The requester should provide a brief description of the simulation requirement, and potential deliverables they would like to see. The case study database is compiled as part of the chain of evidence required on the basis of the research study.
Case Study Generalisation, Rigour / Validity & Reliability
Generalization is challenging due to the highly localized nature of ARS outcomes, which involve organizational change along with the implementation of an IT artifact. This shift from the specific and unique to the general and abstract is a critical component of ADR. 2011) suggest three levels for this conceptual move: (1) problem case generalization, (2) solution case generalization, and (3) derivation of design principles from design research results.
The subsequent section on generalizability, rigor/validity and reliability of case studies describes the associated tests that will be subjected to this research case study. External validity – Covered in the replication of the methodology in project samples, external reviews and case study protocol.
Conclusion
The chosen ADR method contains the stages and principles described in the chapter (see Figure 8 for an overview), together with the implementation components of the method in relation to this research case study. The method used included identification of the research setting and sampling requirements, data collection and analysis, and case study observations. The research population included Division A as the main stakeholder and Siemens Digital Solutions as external reference stakeholders.
The research study consisted of five different project samples, including small, medium and large design/site support type projects. The data collection includes secondary sources (reference documents and templates) and primary sources (observations, interviews, questionnaires). Three key principles of data collection were included in the research protocol, including triangulation, construction of a case study database, and a chain of evidence.
To comply with the generalizability, rigor/validity and reliability requirements of the case study, the following components formed part of the research method. Internal validity was achieved through internal project sample reviews, including unstructured project participant interviews and questionnaires. External validity was achieved through a constructed case study protocol and external feasibility and strategy reviews, including unstructured expert interviews and questionnaires.
The reliability of the research was achieved through the compilation of a revised case study database, which can be obtained on request.
RESULTS AND ANALYSIS
Introduction
Secondary Sources
Project Level (Samples)
- Project#1
- Project#2
- Project#3
- Project#4
- Project#5
- Comparative Analysis
Organisational Level
- Selection & Evaluation
- Components
- Feasibility Studies
Internal Reviews
- Unstructured Interview
External Reviews
- Unstructured Interview
Strategy Development
- TX Phasing Strategy
- Future Resource Capacity
- Software Licensing Strategy
- Training Strategy
- Return-on-Investment
- Plant Simulation Strategy
- Organisational Strategy
- Strategy Validation
The project level samples were also submitted as part of a commercial case study for the work of the 2021 Winter Simulation Conference (Wesch, 2021). This is a major design support project that consists of modeling and simulating a complete loading, assembly and packaging facility. As part of the project level strategy development, a project application template was developed subject to all project examples (see Appendix B).
As part of the development of the project-level strategy, a process data entry form was developed and subjected to all project samples (see Appendix C). The above results represent a basic reference that can be used in the development of the project. This should provide motivational support and potential effects for upgrading the line and optimizing potential throughput and utilization.”
This is a small support project involving the modeling and simulation of a modernized phosphating line in the company's existing paint shop. This is done for each component at the project level to jointly analyze all project patterns as part of developing the overall strategy. The training strategy is part of the overall implementation strategy and defined requirements defined by section A.
This is to provide motivational support and potential effects for upgrading the line and optimize the potential throughput and utilization. As part of the Division A support function, basic TX training will be provided to potential users based on licensing and phasing strategy. Internal reviews and evaluation across multiple phases of the modeling and simulation process will follow with 'requester' and/or persons associated with the project.
DISCUSSION
- Research Question & Objectives Alignment
- Literature Review
- Significance & Implications of the Study
- Limitations of the Study
- Validity, Reliability & Verification of the Study
- Artefact Review
- Secondary Sources
- Project Samples
- Organisational Components
- Internal Reviews
- External Reviews
- Strategy Development
We achieved this through internal and external reviews, taking into account all phases of the implemented strategy. The alignment of the research objectives and the developed artifact is also mentioned in the artifact overview chapter. Reference samples of projects provide evidence of the feasibility of the implemented strategy and provide a starting point for further evaluation and development.
This is mainly due to the development and implementation of the strategy completed at one company (Company A). Further limitations included the verification and reliability analysis of the organizational options referred to in Chapter 4. The average feedback score on the content and format of the initially compiled template was good to very good.
The average feedback rating for the content and format of the initial template compiled was average. Project #5 was the only project sample that could be validated against concurrent process data with real system implementation. The average rating of the comments regarding the reporting of the various samples was good to very good.
This is a very important evaluator tool to analyze benefits and ROI simultaneously per project type, as part of the implementation strategy going forward.
CONCLUSION, RECOMMENDATIONS AND GENERAL OBSERVATIONS . 111
Recommendations & General Observations
For future studies, it is suggested to implement multiple project requirements of the same type. This will potentially eliminate variance and provide a clearer picture of project step implications and comparable value. Because of the scale and scope of the research, and with the focus on developing an appropriate and effective implementation strategy.
PLM systems and Tecnomatix Plant Simulation, a description of the environment, control elements, creation simulations and models. Analysis of the production process in the selected company and proposal of a possible model optimization through PLM software module. A more descriptive section on the use of the document and responsibility would help to understand the form.
I think it would be better to have a section at the top before technical data, which allows you to capture the desired outputs (measurable variables) of the model. It will be useful to keep track of the model (in case of loss of the actual model). The participants were introduced to the research study and the informed consent forms were reviewed and signed before the start of the interview.
Participant C: Participant most exposed to TX as a client and involved in three sample projects. Participant C: The output of the study should contain the main tools that TX can be used for and provide points of benefit for different projects. It also depends on the functions of the company and the department (production vs. design).
UNSTRUCTURED INTERVIEW (EXTERNAL REVIEW)
Participant G: The most important factor to keep in mind is the People-Process-Technology barrier. The best practice is to ensure that strategic decisions are included as a process from implementation to integration. Participant F: The best identified resource requirement for TX in a company is to have at least one simulation engineer, who will be a dedicated individual who implements the software at a project level.
Mature companies with an implementation strategy in place can benefit from a simulation team of 2-5 people. Initially, the capabilities of the standard TX license are sufficient, with development and maturity professional integration can be included. Participant G: The value of TX for operations depends on the team for simulations and successful implementation at the project level.
The best software strategy to follow is with a top-down initiative for production and design support, with quantification of simulations to review the potential measurable success of projects. Building a library of models and incorporating a modular design approach, with object templates, will provide the most efficient work practice as more projects are completed. An important aspect to be included in all simulation projects is the review of data, models and simulations.
Additional value for manufacturing and design support simulation projects lies in having building models available that can be maintained and used for future decision support.
