Human Resources Info Systems 2-2 Case Study
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
667
Subject
Information Systems
Date
Apr 3, 2024
Type
docx
Pages
4
Uploaded by ConstableAlpacaMaster1040
1
2-2 CASE STUDY
2-2 Case Study
Corey Scott
Southern New Hampshire University Graduate College OL-667 Human Resources Information Systems
Professor Allissa Baxter 3/16/24
2
2-2 CASE STUDY
Major/Minor Issues Throughout the project, there were several issues that the team ran into that were significant enough to affect the time and scope of the whole project. These issues ranged in severity and detail and included problems related to data migration and cleaning, user adoption and training, and system integration (Ungashick, 2023). Part of these challenges were faced due to having to convert the Europeans processes over to U.S. processes. One such issue that directly
affected the timing of the project involved communication between the U.S. design analyst and the U.S. support team. At times, the analyst, who would be in London, would have to clarify certain details of the project with the support team, who were in the U.S. Because of the time difference between London and the United States, this communication often caused a one-to-
two-day delay. Senior design analysts would also make recommendations that certain processes be reviewed such as payroll, reporting, and interfaces. However, project team managers didn’t feel that these areas needed reviewed. The reasoning was that things such as reporting was already discussed monthly at other meetings and that payroll was outsourced so project leaders didn’t need to worry about it. However, it was later discovered that reporting should have been discussed as many of the codes used in reporting were not usable or transferable (Bartlett, 2008). For instance, the way employees on leave were classified was completely different between the two countries. This presented a problem with integration as the two systems were different and incompatible. When determining which coding would be used for global integration, the project team lead would plan project meetings when senior leaders were unable to attend. If they were able to attend, the ideas were presented in a way that reflected what the project team wanted
3
2-2 CASE STUDY
accomplished versus what was obtainable. Many of these decisions resulted in cases that were unable to be accomplished due to being unworkable (Bartlett, 2008). Some decisions were being made on the basis that they were legally required, but upon further review this would end up not being the case.
The company also faced minor issues with language as sometimes the same term had different meanings between areas. Other issues involved figuring out which data they were going
to allow employees to edit themselves. Certain changes would have benefits and tax implications
for employees (Bartlett, 2008). For example, an employee who wanted to update their address because they had moved from California to Texas may not have been able to find their heath care
provider in their new state. To make some of these changes it would require a system change that
needed to be created and evaluated before it could be implemented, and this could potentially have to be done with every employee.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
4
2-2 CASE STUDY
References
Bartlett, J., & Bartlett, M. (2008). Integrating a Human Resource Information System: A Module With Case
. https://web.archive.org/web/20171019132551/https://www.shrm.org/academicinitiatives/
universities/teachingresources/documents/08-0882_integrating_hr_info_sys.pdf
Ungashick, B. (2023, July 4). Common challenges during HRIS implementation and how to overcome them
. https://www.outsail.co/post/common-challenges-during-hris-
implementation-and-how-to-overcome-them