What have you heard about PeopleSoft 9.1?

Some information that has been gathered includes some facts:

It is the third release since the acquisition

It has 1350 new features approximately

It has 28,000 or more page enhancements

It has Web 2.0 Capabilities

Approximately 300 new web services

And a large number of industry specific enhancements

Like many new releases, there is a new look and feel to the product. You still have the My Favorites area and in addition there is a recently used area on the menu.  In addition the navigation menu is only visible when pulled down.

9.1 also includes mouse over functionality on the menus.  In going through some of the changes and talking with clients one of the features they seem very happy with is the ability to use zoom grids for more working space with drag and drop, grid scrolling and column locking capability.  The grids are also sortable.

Some of the other items include an updated style sheet, a rich text editor, mouse-over pop ups as mentioned previously and an instant message capability with Yahoo and Beehive.

Some other features include out of the box role-based dashboards and reports.  The fact that it uses PeopleSoft  security is not a change.

There are some nice HR analytics dashboards including: workforce profile, Recruitment, Leave and Absence, Learning Management (a favorite mine), HR Performance, Compensation, Retention and Workforce Development.  Some of these are new and some enhanced.

So why would you want to upgrade?  Well, if you are on 8.8 you are going to have to get extended support which certainly is a financial reason to upgrade.  Others are increasing the effectiveness of your workforce by ensuring compensation rewards top performers and you have pay for performance capabilities.  Making sure that you have a strong pipeline for key talent is critical to any organization and maintaining this internally is a cost saving for recruitment.  Nine one will provide executives with the ability to make better informed decisions with metrics available.    Eliminating interfaces could reduce IT expenses and eliminating customizations during the upgrade usually results in cost savings and additional efficiency.

Some links that will provide additional information include:

http://www.oracle.com/education

Http://www.oracle.com/pls/psft/homepage

http://www.oracle.com/applications/peoplesoft-information-portal.html

If you are interested in some great decision trees, read this article from Gartner, it is packed with good information and would be helpful in deciding if you want to go to 9.1.

When customers are planning a new installation of PeopleSoft, Gartner suggest to implement version 9.0. “Gartner believes that v.9.1 will be released during 2H09, but most customers will not want to be the first to take on a new release. If you need the newest functionality right away (such as compensation management or succession management in HCM), then implement v.9.1 as soon as is practical for your organization. If you don’t need the new functionality, then implement v.9.0 until v.9.1 has more market traction and proof points, which Gartner expects within 12 to 18 months of release.”

Read the full article.

Source: Gartner (July 2009)

This year Oracle released new versions of PeopleSoft (8.50) and Applications (9.1). Will customers start upgrading to 9.1 in 2010? If customers follow Gartner they will wait. My opinion is that the evolution steps between the PeopleSoft versions aren’t that big. Loads of fixes, patches, bundles and maintenance packs from previous versions have been included in this new release. Big functional changes haven’t been made in 9.1. The risk between upgrading to 9.0 or upgrading to 9.1 isn’t that big. If your customers are multi language users, you might want to consider the upgrade to 9.1 as it is unclear when the language pack will become available.

Do you have the Deltas?  Have you started implementing 9.1?  Add Comments or follow RSS.

Planning is so critical for a project and what makes a project successful is in the way you approach the first few weeks.  I have conducted these strategy and implementation workshops in a week but the work of the team goes well beyond that.  The first few weeks, however, are what can determine success or failure for a project.  So far we have discussed how important it is to get a project right the first time, the importance of scope, and organizational impact or change.  Another important factor that needs to be addressed in the first week is how you will handle issues that arise during the project and what the process will be for resolving those issues.

If you are working with a standard implementation methodology there is probably a process for issue resolution.  If not, develop a database, excel spreadsheet or similar method for tracking issues.  It is important that you establish what an acceptable time frame is for resolution and what will be done if the issues are not resolved in a timely manner.  What are the roles involved in the resolution process, who identifies, who assigns, who tracks, how high up in the organization will you have to go to find a solution, and finally who determines if an issue is closed.

Issues should be addressed on a weekly basis at meetings.  If critical you might have a process in place to identify them on your project website, or even use twitter to get information out to your team in a timely fashion.

Of course, there is a deliverable that would be associated with this part of the workshop which would be a template for tracking issues.

So we have now addressed one more small part of what would happen in Day 2 of your implementation/upgrade workshop.

Looking forward to any additions you might provide via comments.