| Key 4: Put SAP in the Center |
|
|
| Written by Berthold Kastel | |||||
Page 3 of 3
Lastly, Primavera or MS Project are not comprehensively enough covering critical processes like purchasing, HR, controlling, costing, or accounts payable. While they often are considered "best of breed", they are not "real" enterprise software in the sense that they cover an "enterprise range" of business functionality. They are narrow in their focus and reach limitations almost immediately when going out of the realm of scheduling or resource management. For example, Primavera's cost management capabilities are limited compared to SAP's, and in MS Project they are even less available. Purchasing functions and time and expense (T&E) transactions are project focused and not integrated into other functions. SAP on the other hand has all of that. This is then the reason why it simply seems more complicated - because it adds capabilities and so changes the job profile of project managers.
All in all, there is little reason to not at least integrate some of SAP's project management capabilities into the overall process and system, definitely on the enterprise and project layer. It will allow to reap the benefits of integration into critical supporting areas and functions and improve productivity in the big picture. While the individual job profile may be changing (widening in some areas, being reduced in others), the overall effect certainly is positive. SAP needs to be the centerpiece of any solution, even if some important project management functions may be performed by other tools.
Copyright © 2007 Competitive Edge International, Inc. |
|||||
| < Prev | Next > |
|---|
| Polls |
|---|
| Related Items |
|---|





