PLM moet met versies

Geen samenvattin

Met PLM kan constructeur ontwerpen veel beter afstemmen op de actuele klantenwensen

Henk Jan Pels : 'Met PLM kan constructeur ontwerpen veel beter afstemmen op de actuele klantenwensen' - In zekere zin is PLM de volgende stap in een evolutie van uitdijende databases, waarbij Engineering Data Management (EDM) het beginpunt markeert en Product Data Management (PDM) een belangrijke tussenfase is. Dr.ir. Henk Jan Pels van de TU-Eindhoven stelt dat de strategische waarde van PLM niet licht kan worden onderschat. Een PLM-systeem vormt bijvoorbeeld het IT-antwoord op de trend om producten beter af te stemmen op de wensen van de klant en biedt daarmee een adequaat antwoord op de vraag naar flexibilisering in het productaanbod. 'Over dertig jaar werkt geen enkel productiebedrijf meer zonder PLM' is een van zijn stellingen

PLM : hoe volwassen is uw bedrijf daarin?

Geen samenvatting

De electronische archivaris

No abstract

PLM maturity assessment

Implementing Product Lifecycle Management (PLM) is a strategic issue in high-tech and electronic industry. Because PLM is an approach supported by an enterprise IT-system, it is difficult to assess how far a particular company has proceeded on the road to full implementation or what the relative position is compared to other companies in the branch. Maturity assessment methods have been developed and applied in other IT areas seem attractive for PLM too. This paper describes how a PLM Maturity assessment method has been applied in some 20 companies by students, who also added an open interview to the assessment questionnaire, such that the assessment scores can be related to background information of the company. This leads to some critical notes on the idea of maturity assessment

Rivalry between the collective use of IT tools and working methods of design teams

Nowadays a high variety of IT tools is available for communication purposes in design processes on individual and group level. Despite this, the exchange and sharing of design documents collectively in design and engineering teams might be limited mainly, due to habits, preferences, working methods and rivalry between the collective use of IT tools in such product development. Changes in habits and preferences for collective use of IT tools might be realized by training and management power. However, adoption of collectively to be used tools, like project websites, is depending heavenly on the attractiveness for users in daily work. Based on empirical research outcomes it is indicated that rivalry between collective used tools and differences in working methods of users might be main barriers for attractiveness of these tools in daily work. Applying a framework for analyzing and categorizing of the frequency of use of IT tools for team communication, the authors explain the appearance of rivalry between tools, limiting the effectiveness in daily work and not affecting team communication and performance. By comparison of working methods in different sectors authors explain the necessity of changes in working methods in design and engineering in the building & construction industry on organizational and inter-organizational level for successful adoption of collectively to be used IT tools in team communication