Upcoming Seminars:
Management of Change "MOC"
Best Practices
Houston, TX November 4 - 5, 2010
Marriott - West Loop South Galleria
Details and RegistrationChem NEP Readiness
Houston, TX November 3, 2010
Marriott - West Loop South Galleria
Details and RegistrationLatest Whitepaper
Quantifying the Effectiveness
of Interventions in Workflows
of Interventions in Workflows
Latest NewsLetter
Management of Change (MOC)
Best Practices
Download Now
Gateway Consulting Group, Inc.
8610 Transit Rd. Suite 100
East Amherst, New York, 14051
Email: info@gatewaygroup.com
Call: 800-668-2334
Fax : 716-204-3378
PLM and ECM Project Methodology
The design and implementation of either a PLM or ECM system are two specific examples of ways to achieve business process improvements using information technology. Volumes have been written about how to successfully deploy computer systems, and those lessons apply to PLM/ECM as well. Most authors recommend the use of a methodology.
A methodology is a set of guidelines which can be tailored to both the people and circumstances involved in a situation. Gateway's PLM/ECM project methodology is illustrated below. The arrows indicate the sequencing of the phases, whereas the numbers are simply used to identify the phases.
Methodologies are normally organized into phases, and the phases are divided into steps and activities. One could draw the conclusion that a methodology is like a high school chemistry experiment method which describes everything that a novice would need to do in order to successfully deploy a PLM/ECM system. Unfortunately, that's not the case. We've found that a methodology provides a framework for an experienced person to conduct the project, and allows an inexperienced person to have the appropriate expectations and to measure progress.
Alternative Methodologies
Proprietary methodologies have been developed by most of the large system integration firms. They are comprehensive and
cover a large spectrum of potential applications. However, there are a number of characteristics of typical PLM/ECM
projects which allow the phases to be reduced to those described in this document.
- Commercial Off-The-Shelf "COTS" Software:
PLM/ECM system implementation is based on the installation, integration and configuration of Commercial Off-The-Shelf (COTS) software. Therefore the project must be approached as an implementation effort, rather than a programming effort. - Strategic Planning:
It is expected that the strategic planning exercise will have been completed before the PLM/ECM project begins. - Natural Scale of PLM/ECM:
The size of an initial PLM/ECM implementation is balanced by two opposing forces. The initial system must be large enough that the dollar benefits can be realized, but it can't be too large or the project will be overwhelmed by technical and managerial complexity.
What about a Pilot Project?
A pilot project (though a vaguely defined term) can be useful to:
- Help educate your team about PLM/ECM in general.
- Learn what capabilities certain PLM/ECM software has in order to take maximum advantage of it.
- Learn what requirements are difficult to implement and try to eliminate or refine these requirements.
- Build demos to raise awareness within the organization.
You will note that none of the pilot benefits leads to the conclusion that a methodology is not needed. On the contrary, a pilot can easily be used within the context of the overall methodology.