I recently engaged a new prospective customer who is interested in upgrading PeopleTools to version 8.5. One of the primary reasons for this client to undertake the PeopleTools upgrade is to preempt an inevitable upgrade to HCM v9.1, as they are currently on v 9.0 MP3. What’s motivating them to upgrade HCM? It’s a story we’ve all heard (and maybe told): their current version won’t be supported by Oracle past the end of next year.
With this in mind, it’s obvious that the client is starting to look at their overall PeopleSoft environment on a global scale, the implications associated with an upgrade, and is giving serious consideration to long-term approach from an implementation standpoint.
This view was the catalyst for me to present flexible options for the PeopleTools upgrade. Without knowing how the client might respond, I recommended the possibility of using a “lab” approach to complete the project. In other words, an off-site implementation methodology where they might realize some cost savings as opposed to an in-house development effort.
It turns out that the client used this approach the last time they upgraded and responded that they would like to see this as an option in the proposal. More importantly however, the client views this method as a “knowledge transfer project that will help us gain the skills to better augment the next upgrade project.” And it’s not the first time I’ve heard that, especially as it relates to PeopleTools and companies not having the resource bandwidth or expertise to do a PeopleTools upgrade internally. In fact, it’s why we offer an affordable, high-value PeopleTools upgrade packaged service [PDF] that has been a success with quite a few clients.
Regardless, more and more folks are looking at upgrading PeopleTools, usually as a sub-consideration for a larger PeopleSoft upgrade project. If this sort of thing is on your roadmap and you want to talk about it, don’t hesitate to drop me an email. I’d be happy to chat.
###
More links:
MIPRO Consulting main website.