IFM REPLY
|
|
|
|
|
|
|
|
|
|
· |
|
|
|
|
|||
|
Domni Hello everyone,
The process I would like to change is end users being called by the local analyst once their accounts have been re-enabled. After a local analyst enables their accounts, the user then has twenty-four hours to sign into that account before the account is automatically disabled again. If the user does not contact my office within 7 days of that account being disabled again, they have to restart the process all over again. The current process causes a lot of frustration for the end users due to not being aware that their account has been enabled. The five requirements that will greatly improve this process would be:
1. The system must notify the end user with a message marked important about their account about to be disabled. 2. The system must require the end user to “agree” that they were notified of their account about to be disabled. 3. The system must automatically notify the end user the account was enabled. 4. The system must require the local analyst to call the end user before closing the ticket. 5. The system must give the user forty-eight hours to sign in.
Discussion 2 Eliza The process that I chose to evaluate was that of an associate requesting an availability change at my current place of employment. As it stands, if they wish to change their availability to work, associates must obtain a paper form from HR, fill it out with their desired availability, then present it to their manager for approval. If the manager approves of the change, they will sign the form and return it to the associate, who then returns it to HR. The HR manager then enters the updated availability into the scheduling system so that everyone that has a hand in writing the schedules is able to see when the associate is able to work. The reason I chose to discuss this process is because it is very cumbersome and inefficient, and it definitely needs updating. An improved system to fulfill this process would meet the following user requirements: 1. The system must require the user to enter the times that they are available to work each day. 2. The system must automatically notify the associate’s manager via email when they submit an availability change request. 3. The system must require the manager to approve or reject the request within 72 hours. 4. The system must automatically transmit any approved availability changes to the scheduling program. 5. The system must immediately notify the associate when their request has been actioned.
References UMGC.(2021). Requirements. https://learn.umgc.edu/d2l/le/content/579460/viewContent/21818913/View Discussion 3 Faith The process I choose is the way we send out In-processing checklist for new employees. I am choosing this process, because in my opinion, the first part of the process needs improvement.
As is process a. I send packet to new hire, informing them to complete what they can and then send to their new office b. Employee sends to office where they will work 10% of the time c. New office sends to the office who takes for action
To-be process a. Office where employee will work sends out packet b. Employee returns to his new office c. Employee’s new office forwards to office who will take action
I would like to be taken out of the equation because inevitability, the new employee, in their excitement, sends the checklist back to me instead of sending to their new office as instructed. It would make for a more efficient process, and it would be less confusing for the new employee. As it currently stands, I have to write out the steps for the employee to follow, so they know what to do with the checklist. 1. The system must provide well-written instructions for the checklist 2. The system must make the checklist a fillable PDF document for ease in completing 3. The system must highlight in red important areas for new employee to complete 4. The system must require the user to complete all blocks before proceeding 4. The system must require the user to sign the checklist in the last block of the checklist |
|