Riordan Human Resources AnalysisEssay Preview: Riordan Human Resources AnalysisReport this essayRiordan Human Resources AnalysisUpon the request of Hugh McCauley, COO, we were asked to complete an analysis of the HR system to integrate existing tools in use today into a single integrated application. Also, the request is to be completed within the next six months so utilization in second quarter of next year is feasible.
All testing and debugging of system must be completed within the six months timeframe as well. We want the system to be fully functional after the end of the project time.
Information Gathering TechniquesThe best information gathering techniques for this particular project would be interviewing employees within the Human Resources department as well as the head of the department so that we may have a better vision of what each side wants the new system to accomplish. Also, interviewing would allow for more in depth conversations regarding things that currently work within the system versus things that do not work within the system.
Also, review of the intranet gives an invaluable insight to the current state of things within the current system. The system is both archaic and out of date with users still having to submit paper forms.
Proposed Design MethodI would design a waterfall approach to this task. This is a large task encompassing the entire company because the Human Resources Department touches every employee within the company. With such a large task we want to make sure we are covering all of our bases as well as attending to the needs of those who are requesting this overhaul of the system.
Key FactorsThe key factors in this task will be making sure we research all aspects of the Human Resources Department and each system they are currently using. After reviewing each system, we can then look at what improvements we can make to each system without a complete overhaul as well as identifying those systems that will require a complete overhaul to perform up to the specifications and requirement of shareholders.
We will be required to make sure both the shareholders as well as ourselves are aware of the requirements and the deliverables. We will only waste time backtracking over parts of the project we have already completed.
Project ScopeThis project is to create a successful Human Resources Department system that can be implemented and utilized across the entire company of Riordan Manufacturing. This project should be completed within the next six (6) calendar months in order to increase the efficiency and utilization of the system companywide while improving upon some current systems and overhauling others.
FeasibilityAfter completion of a feasibility study, this project is one that is very feasible with a high success rate. Options explored were: 1) Complete overhaul of entire system, 2) Update of certain systems, while overhauling others, 3) Leave systems as is, 4) Only focusing on systems that are currently in need of dire repair and completing a cyclic overhaul.
It has been decided our best course of action, as well as the most financially feasible, is going to be updating some and overhauling others while maintaining the vision of a better system to be utilize.
Application Architecture and Process DesignThe overall system will include the following:Complete management of all employee informationPhone numberAddressHire DateSalary HistoryPosition History (ex. How long in position, when eligible for transfer or promotion)Company-related documentsEmployee handbooksEmergency evacuation proceduresSafety guidelinesBenefits administrationEnrollmentStatus changesPersonal information updatingComplete integration with payroll and other company financial software and accounting systemsApplicant trackingResume managementThe system will also track the following:Attendance and PTO usePay raises and historyPay grades and positions heldPerformance development plansTraining receivedDisciplinary action receivedManagement and key employee succession plansHigh Potential Employee identificationApplicant tracking, interviewing, selection, and notification.Each piece of the program will act both independently and dependently of each other. They will also eliminate the need to use paper; instead, records will be created, updated, and stored electronically. The program will be housed in a specified room located at company headquarters and be managed by Human Resources personnel. Each individual site will upload all information on designated days which will allow for centralized storage. Managers and employees will each have access to certain parts of the system to allow for self service. Those items will be discussed with Managers and Human Resource personnel so that all who need access will have it.
SecurityTo protect the integrity of the system as well as the information, the following security measures will be implemented immediately. Each individual will be assigned a level of authorization. There will be four (4) levels: Human Resource (full access to any level), Human Resource Limited (limited access to certain levels), Management (access to be determined by Human Resources), and User (anyone not falling within other categories. They will only be allowed access to self-service areas). Each user will then be asked to create a username and password for the system to validate them each time they are gaining entry into the system. Upon either successful or unsuccessful entry, the system will keep a log of those attempts as well as the user that was granted
The credentials of the systems will be stored in a .csv file. They will be encrypted (encrypted and stored as a .txt file) and will not have any human readable content. When necessary, a password is stored and a user account will be created to have them logged into the system as well. For information on how to use the system, see the User manual for all of the steps outlined above. The following is a general overview of how you will be able to log into a virtual machine:
Hello World
A Virtual Box
If anyone has any questions, you:
I would like to invite the staff to speak with an expert witness about: the security of my virtual machine I create, the use of My Account and the security of our customer’s account on BitVault
• What I am using the virtual machine for but why?
• How has bitcoin enabled your security since you created your account on my virtual machine? If you did not create an account on BitVault, how did it work? What are any of the security concerns that have been identified among all the users logged into BitVault? Any updates to the current implementation or future bitcoin updates?
• How and why is the virtual machine secure? A good way to understand this is to examine the user logs from my local account. On this website, you find information from the various accounts of my local virtual machine. These logs are usually of my account and are provided to people who need access to my personal data. These logs can be viewed using any of the public and mail addresses that I find on the Exchange site. Most of the other accounts on the Site are private and I find they are kept private and protected. However, I believe it would be highly unethical if I could only allow or deny access to their personal information. That said, I will continue to provide a detailed guide to creating a secure virtual machine that would not be run by your computer but that would allow me to protect it from tampering.
• What are the security characteristics of the virtual machine and have I followed them since I create or have created My Account? In what ways has the virtual machine protected against unauthorized access? Have I also failed to enforce the security criteria, or am I protecting the confidentiality of the customer’s identity and personal information? If so how has the virtual machine made it into My Account to ensure I do not inadvertently access their personal data? Are I abiding by the guidelines established by the Security Team?
• What is the reason for failing to enforce security measures on our customers who have created their accounts on the Site? As I’ve mentioned in the past, not all organizations adhere to the requirements laid out in