Integration of the PLM system with other applications

1

Different stages of deployment
• A well prepared development project eliminates risk of failure. • Deployment of PLM project requires time and resources.
– Right people: skills, expertise, knowledge…etc – Sufficient time: projects may take months to years.
>> co’s size, chosen system, approach taken.

• Being a computer-based system, PLM needs to be ‘ready’ for rapid changes after implementation.
2

Factors to consider in a PLM project Scope of the system <-Stages & Features PLM system project-> Co’s size Co’s enterprise character 3 .

Stages of the PLM system project 1 • Understanding the need for change 2 • Choosing a system 3 • Realization stage of the project 4 • Accomplishing change in the organization 4 .

. – Gradual.g..g. Conceived at strategic planning session. – Spontaneous. • Likewise. • E. 5 . Problems have reached their tolerance levels. • E. the understanding and acceptance of the need for change.Understanding the need for change • The need for change may come up in several different ways.

Reasons for the need to change • Taking the steps to effect changes may be decided by several reasons.. Flexible configurations…etc.etc. – To improve after sales market share: • Maintenance. spare parts. customer satisfaction. – To reduce time-to-market: • Design/Parts reuse. 6 .

– The operative level. 7 . • Most important. the management level must: – understands the significance of PLM – provides support throughout the project.Perceiving the need for a change • The need for change can arise from: – The management level.

8 . • It is only a tool that can be used to bring system and discipline to these processes. – An absence of discipline in the process is often a serious problem.Study of present (AS IS) and objective (TO BE) processes • PLM project is a development project for business processes related to the formation and use of product information.

Bringing in discipline to business processes • Sources of the problems: .Alternative ways of performing tasks .No management of different revisions and variations of documentation .Unclear division of responsibilities between different departments .Lack of guidance and documentation for new employees .Unclear understanding of the overall picture and meaning of the process .Lack of instructions for using IT systems .No management of different revisions and variations of items 9 .

‘AS IS’ 10 . >> check existing docs. >> hired consultants to help.AS IS and TO BE processes ~use the PLM maturity model ‘TO BE’ Set clear targets for the project : Understand the present state of product data and LCM.

The PLM processes or basic PLM concepts are not best-of-the-breed. Lifecycle and product management processes have developed to the stage where similar procedures are followed by different people undertaking the same task (i. or communication of standard processes. There is no formal development. there is no end-to-end PLM process supporting IT systems. There is a high degree of reliance on individual knowledge and therefore errors occur. 2 Repeatable but intuitive 3 Defined 4 Managed and measurable 5 Optimal . IT systems support individual parts of processes. However. IT systems support individual parts of processes. the human factor is important. nor are they uniform throughout the corporation. however they are formalized. all lifecycle and product management issues are resolved by individuals on a case-by-case basis. Processes and basic concepts are standardized. documented. 11 however they are formalized. defined. documented. all work is completely or partially manual from the process point of view. nor are they uniform throughout the corporation.e. all work is completely or partially manual from the process point of view. IT systems support individual parts of processes. documented. However. defined. however they are formalized. defined. the human factor is important. definition. Processes and basic concepts are standardized. all work is completely or partially manual from the process point of view. there are no defined approaches concerning lifecycle management. and communicated through manuals and training. However. all responsibility is left to individuals. there is no end-to-end PLM process supporting IT systems. Work must be done to define and develop the PLM concept and standards. Processes and basic concepts are standardized. there is no end-to-end PLM process supporting IT systems. training. However. and communicated through manuals and training. the human factor is important. nor are they uniform throughout the corporation. The PLM processes or basic PLM concepts are not best-of-the-breed. The PLM processes or basic PLM concepts are not best-of-the-breed.PLM maturity model 1 Unstructured The PLM topic has been recognized and its importance agreed. at present. the processes function on ad hoc bases). and communicated through manuals and training.

~different business units.Choosing a system • Immediate PLM implementation is difficult. or locations. 12 . organizations. vary in maturity that require different development paths. – Human resource. – Financial resource. it depends on the co’s: – Extensiveness of operations.

● Visits to companies using the systems. project content and timetables. ● Selecting a system. ● Negotiating commercial terms.The phases involved in choosing a system ● Becoming acquainted with existing systems and their suppliers. ● Choice of systems to pilot. 13 . ● Piloting the systems.

~ requires upgrading (with newer system versions). ~ more expensive.The phases involved in choosing a system Get acquainted with existing systems and their suppliers Visit companies using the systems 2 ways Customize the software to match requirements ~ provide new. ~ operations can be adapted to system welltested features. project content and timetables Choose a system 14 . Do not customize. customized functions. Make direct use of existing features ~ quick deployment. ~ slow deployment. Select systems to pilot Pilot the systems Negotiate commercial terms.

The level of integration. Ease and comfort of use 7. architecture and scalability 3. The software’s functional and technical features. such as user conferences 8. Ease of maintenance 6. 15 . The amount of implementation work and the time required. reference visits 10. the software product’s roadmap or development plan.g. Total price: work. and the software company’s vision for the future 2. The principal market (industrial sector) of the PLM software in question. Available support and other supplier services. opportunities for use of standard technologies (e. Interface language versions.Points to consider when choosing a system 1. acquisition of expertise. own versus outside work 5. Existing implémentations. licenses. XML) 4. maintenance. The PLM program’s support for multilingual item and documentation management 11. hardware 9. new third-party software. its limitations .

Realization stage of the project Subproject Divide the project into several subprojects ~ system start-ups are usually in several different locations. ~ introducing all functionalities of the system in all offices at the same time is difficult. Subproject Subproject PLM project Subproject 16 . ~ different areas require different expertise.

Project stages Start of the project Visit companies using the systems Preparation and planning of the project Start up phase of the system Feedback and action 17 .

Definitions of interfaces to other systems .Definitions of item groups. attributes and other property data .Advanced PLM training for the project group .Survey of resource requirements .Creation of an IT system map . such as projects.Study of present and target processes .Possible improvement plans for data .Definition of the desired product information/data model . and products . choice of transfer tools .Implementation of system interfaces.Functionalities of the PLM system in the processes of the company . translations.Definitions of document types.Tasks arising in the project plan .Different statuses and their handling .Creation of databases .Training for the project group . customers.Item transfers .Cleaning and harmonization of data .Definition of objectives .Document transfers .Creation of work instructions for training .Installation of the production environment .Testing.Creation of document templates . approvals .Basic parameters of the system . item descriptions.End user training .Work flows and their definitions . groups.Creation of the project organization .System interfaces 18 .Definition of the intended PLM system .Basic PLM training for the project group . testing . descriptions.Preparation for the transfer of old data.Other data model objects.Installation of test environment .System administrator training . and other property data .

■ Life cycle status handling of the product related to the documentation. ■ Significance of the product related to the documentation.) ■ Availability of item information from other systems ■ Possible use of the items in other departments 19 . etc. ■ Number of documents. case by case.The transfer of items and documents ~from old systems or even from outside the old systems to the PLM system must be considered. • estimating documentation: ■ Life cycle status handling of the document. • estimating items: ■ Life cycle status handling of items (activity: is the item used in production/ in spare part use/not used anymore.

■ Management of item structures. 20 . sector by sector. ■ Management of product documentation. ■ Management of project documentation. ■ Management of item information. ■ Management of other documentation entities. ■ CAD models.Start up • The beginning of production use can be handled. Phasing examples: ■ Management of CAD drawings. The features and properties of the software are so complex that everything cannot be used at once. and is often best handled thru’ phase by phase.

■ To support the project managers. ■ To be responsible for project schedule. ■ To be responsible for the costs of the project.Steering group • The steering group needs to: ■ To co-ordinate the progress of the project. ■ To make decisions that are related to the project and which affect the modes of action of company. ■ To prepare the project’s enterprise level decisions for presentation to the company’s management team. • The membership of the steering group (cross- discipline) R&D manager ■ Production manager ■ IT manager ■ Development manager ■ Marketing manager ■ Sales manager ■ Quality manager ■ Business unit manager ■ Managing Director/President ■ 21 . ■ To motivate employees in favour of the project.

• The group will perform all the tasks and take responsibility for all technical problems and business process issues. knowledge and expertise drawn from several disciplines. ■ CAD development persons ■ R&D personnel ■ Mechanical engineers ■ Electrical engineers ■ System engineers ■ Software engineers ■ Factory managers ■ Production engineers ■ IT personnel ■ System administrators ■ Marketing and sales personnel ■ Technical support engineers ■ Spare part managers ■ Logistic managers ■ Order handlers ■ Documentation engineers ■ Quality managers ■ Business controllers 22 .Project group • The project group consists of individuals with specific skills.

■ To co-ordinate the internal meetings required for the project. An organization model for a PLM project 23 . ■ To organize the work to be done in the project.Project manager • The project manager’s central tasks are among other things: ■ To maintain contact with the system suppliers. ■ To solve problems appearing in the project. ■ To provide information about the progress of the project.

– The operating problems/technical errors in the software 24 . – The definition and deployment of system integration.Anticipated problems • Potential risks in: – The creation of uniform modes of action. – The division on the use of the system between people and departments.

Accomplishing change in the organization Organizational change ~Information has become the most important success factor for some companies. New way of sharing information and expertise PLM: “Change Project” New ways of working New way of thinking 25 .

The basic elements required for accomplishing change 26 .