PLM and ECM Project Methodology
The design and implementation of either a Product Lifecycle Management (PLM) or Enterprise Content Management (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 or principles which in any specific instance can be tailored both to the
characteristics of the situation in which it is to be applied and to the people using the approach. 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.
Is this a Cookbook Approach?
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, and 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 allows the reduction of the universe of potential phases to the ones 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 it 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 capabilities are difficult to implement, in order to eliminate or refine these requirements.
- Build demos to raise awareness in 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.
