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.

Let’s talk about some of the roles that you might want to consider for your project.  Depending on the size of the project, you may or may not need all of the roles but someone will have to assume the responsibilities.

Client Executive:  The client executive is responsible for the overall relationship with the customer.  This is the role that would address and resolve issues that cannot be resolved at the  vendor level. They keep the customer aware of new products, services, and software updates as they become available.  They are also the ones who look for opportunities where they can add value to the customer’s business.

Program Manager: The Program Manager may support the Client before and after their software acquisition, especially on large complex projects.  Sometimes called the Enterprise Manager, they would be a part of the Client’s Steering committee and should help shape the project success through the use of best practice, project and business practice.

The Enterprise Manager participates on the Steering Committee, and helps drive the project through to success.  They use industry best business process and practice.  They provide advice that will minimize risk and accelerate the implementation or upgrade.  Many organizations use the engagement manager and project manager interchangeably, however, their responsibilities re significantly different.

Project Manager: The individual in this roles provides the leadership for the project team and produces the status reports, plans, budgets and formal methodology (such as CSC, Compass, Rational) and resourcing.  The Engagement Manager supports the Project Managers both client and consulting in all aspects of project planning and control, and supports the design,development and deployment of a strong quality program.  The Project Manager is responsible for the “care and feeding” of the consulting and client project team members and for supporting the client Project Manager.

Process Specialists (Functional and Technical) Functional specialists are charged with guiding the project team through those steps that require detailed applications functional knowledge and related industry best practices. This consulting-sourced role is usually a full-time member of the project team.

The Technical Specialist executes the technical steps by providing support in the design and management of databases and in tuning the system and architecture. This is a consulting sourced role working in lock step with the client role.

System Engineer The System Engineer designs and creates technology solutions in response to business requirements. They are brought into a project when the solution requires some specific knowledge in the emerging technologies. Skills include: Workflow,  Electronic Commerce; Security including OLAP, Multi-dimensional modeling, compare report decisions, eApplications and solutions to customization requests.

Education Representative This person is responsible for working with the customer to make sure they use the education resources available to them in the most effective manner. This includes executing training plans, setting up on-site classes, and making the customer aware of alternate training formats including stand up training, interactive training, webinars and other venues. It is also the responsibility of this role to have a clear understanding of the business processes used and reflect those processes in User Productivity Kit or Tutor development.

As we move through the discussion on Day 2 and looking at the project scope, constraints will be identified.  Be sure to provide your client and consulting team with examples of what might be a constraint.  A constraint is something that limits your degree of freedom.  Limited development resources might be a constraint.  Constraints might be economic, political, functional, technical and even environmental.  Be sure to document the constraints and work with the project team to ensure they are identified.

Second to constraints would be assumptions.  You make assumptions regarding many aspects of the project.  Assumptions represent opinions that have not or cannot be readily or easily proven; yet they are expected to be true.  An assumption that is often made in organizations is that the executive team is on board and giving total support to the project.  Sometimes an assumption is made that the organization has a specific requirement, only to find out in the fit/gap that the system cannot support the requirement.

So far we have covered many discussion topics in Day 2 and it is important to facilitate interaction and participation by the team.  The one week workshop packs a great deal into the first week that not only sets the stage for the project but also ensures the success of the project.  Think about the deliverables that will be produced as a result of the workshop.

More projects fail because of poor change management than probably any other factor.  People do not like change and it is important to develop a change management and communication plan.  Identify that person in your group who loves to lead the charge on change.  Then develop a group discussion on how this project will impact the organization.  Draw an organizational chart on the board and circle the stakeholders.  Look at how the project will impact end users, customers, managers, executives.  How will that change be communicated to each of those groups.

Identify the leader who will begin to develop the change plan.  How will the team be structured to complete this deliverable.  A draft should be completed by the end of the week and a group will need to work on the content and strategy for that deliverable.  You can facilitate discussion in the large group and then assign a small group to work on the deliverable.  Or you can have several groups assigned to change and communication items for the plan.  Don’t hesitate to assign homework so this is completed and ready for presentation by the end of the week.

What are some of the creative ways to communicate to the organization?  Do you want to develop a web page? a newsletter, tweet program, blog, regular program for sending emails?  Will the communication look different for each group?  Let the group help stimulate this discussion and get a feel for the culture of the organization and how it communicates.  My experience in organizations demonstrates how communication differs, a small organization may communicate only by email, others may have formal presentations and still others may have comprehensive web sites.  Stimulate the group to come up with all the venues that they think will work for their organization and then assign a small group to incorporate the ideas into the plan.

One more step in the starting week of implementation/upgrade planning.

So what should you have completed at the end of the Workshop on the first day.  A Goal of the workshop has been established and there is a solid understanding of how to implement or upgrade “right the first time”.

A template with a rough draft of some of the Charter information will be complete with time for review.  It is also important that team members understand they may have homework such as reading through draft documents and making comments or edits.

So what do you think should be included in a project charter?  I would suggest the following:

1. A mission statement for the project

2. Project Objectives and measuresments to establish when those objectives have been met.

3. A strategy for the project

4. A critical element is the Scope statement.  More projects fail from scope creep than probably any other factor.

5. An Issue Resolution methodology with initial issues identified

6. A Risk Resolution methodology with initial risks and level of risk identified.

7. The resource plan with roles, responsibilities and rules.

8. Constraints, Assumptions and a plan for next steps

9. An initial project plan at a high level which identifies critical milestones.

So at the end of the first day the team has started to develop the deliverables and resolve some of the issues that are open.  This is the time when the Project Manager should schedule a time for a presentation to the steering committee or management team.

Communication with the team and leadership is critical and the fourth day should be used for that communication with a sold presentation in place.  We have discussed the first day and what will be addressed. The timeline for the workshops may vary depending on how extensive in terms of modules and functionality the implementation or upgrade is determined to encompass.

Please make additional suggestions or comments to enhance this program.

Consultantshave called this week with questions regarding how to respond to RFP’s when they ask for specifics about conversion.  At a high level, the critical data elements are determined, mapped, converison scripts written, conversion run and tested.  So what would be each individual step?  Next time you run through conversion document the steps and post them as a comment for all of us.

The second question was around variable comp and formulas.  If you have any standard formulas that you may be using on an implementation, I know a consultant who would appreciate some help.

So what projects are back in play and what old standards continue.  I’ve heard DIMHRS is into testing and continues to continue.  Lot’s of organizations looking at upgrades to 9.0 but making a decision to move forward is often a slow process.

Please feel free to comment and watch as we add eBooks and other interesting information to the blog. 

This may not be a complete list but I thought it might be a valuable list for those of you working on 8.9 to 9 upgrades.  It is a nice summary of some of the enhancements to PeopleSoft.  I am trying to keep the blog posts on this site simple, with simple functional information that may be valuable for consultants working on upgrades or implementations.

Human Resources Enhancements

Talent Management Enhancements

Self-Service Enhancements