Project Management

The Impact of Implementing an HRIS

ARE YOU READY FOR A CHANGE Integrated HR Information Systems (HRIS) have a profound effect on firms that implement them. Most often these firms are replacing several related systems, such as a personnel database, payroll system and benefits system, with one HRIS that does it all. Many people focus on the improved reporting and processing that will be realized from the new system, and those are the reasons most firms choose to implement a new HRIS. But what many people don’t focus on is that the new HRIS will most likely affect the company much more deeply – it will challenge the operating structure and principles of all the HR-related departments. An integrated HRIS results is a drastically different environment than a cluster of related but separate systems. The core concept of a centralized data store inherent with an HRIS demands integrated work processes for consistently managing that store. The two attributes – centralized data storage and integrated work processes – will affect the company in ways most managers don’t expect. EVALUATING AND PREPARING FOR A NEW HRIS Many companies go through a process of comparing and evaluating several HRIS packages using a team of analysts or managers from the various departments affected – HR, Payroll, Benefits, Employee Relations, Training and so on.

Planning for Phased SAP HR Implementations

INTRODUCTION

When purchasing the SAP/HR system, some important choices have to be made about the implementation schedule. How should the company implement - Big bang or Phased? Which functionality does the company wish to utilize? Often, implementations are hindered by unrealistic expectations and poor implementation methodology, which are direct results of poor planning. This poor planning often results in unrealistic project timelines or budgets. Upper management and module sponsors’ expectations for ‘success’ are then driven more by the timelines or budget than they are the quality of the implementation. Such thinking can result in an over-dependence on consulting organizations, heavy project turnover, and a lack of user buy-in. In an attempt to meet impending deadlines, some companies may feel it necessary to ramp up the consultants on a project to overcome the lifecycle of knowledge transfer. While this is a certain way to advance the project, it can lead to a dependence on consulting, reduced contribution from the company’s project team members, and a slower rate of knowledge transfer. After the go-live period, when the consulting firm has gone, users and team members may not be adequately trained to support the system.

Syndicate content

Copyright © 2001-2010 by Insight Consulting Partners - Contact Information