1. Paychex Alexa Deuschle, Michael Cuddahee, Kayla Hahn,
John Northrup and Reid Tirums

2. Agenda Background Current Process New Process ERD
Database outline/Presentation
Conclusion – Business Value
Alexa: id like to thank you all for coming, and considering our database proposal. We would like to start off with a brief background about your company and why we chose to create a new, user friendly database to ensure efficiency. We will then go into your current database process, as well as our new proposal database. After, we will show you what is called an Entity relationship diagram, the basis for our database. Reid will do a brief walkthrough of the database and we will then conclude.

3. Company Background Founded by Tom Golisano in 1971
Headquarters in Rochester, NY
Services: Payroll, tax filing and tax credit services, 401(k) and employee benefits, insurance solutions, HR administration and compliance
Alexa’s background with the company
Alexa – We chose to create a database for Paychex, Inc. Paychex, as you know, is a company founded in Rochester NY, in 1971 by a man named Tom Golisano. He started this company with a mere$3,000 and it has now expanded to a multi-million dollar revenue earning business. It’s services include Payroll, tax filing and credit services, 401(k) and employee benefits, insurance solutions and HR administration and compliance. I interned at Paychex this summer and winter break specifically in their 401(k) investments department. We have chosen to narrow our database strictly to Paychex’s 401k clients and their needs to increase business value within the company. We feel that after we implement our database, the Client service representatives will more adequately and efficiently have the opportunity to serve the its 401(k) clients.

4. Current database process
Three different database systems
Difficult to navigate through
Hard to find who is a “Plan Administrator”
Kayla: currently, Paychex is using 3 different database systems to accommodate clients 401k information. Client service representatives are often finding themselves clicking throughout the systems to try and find the information that they are looking for – this can get confusing. This also requires the representatives to have all 3 databases open at the same time, as well as their s and anything else necessary to carry out daily tasks. As you know, Paychex fosters very important client information (including social security numbers, and 401k account information). One of the most important tasks while talking to a client is to ensure that they are the authorized individual to speak with about they account. This individual is coded as the “plan administrator”. With the current databases, it is sometimes difficult to find the employee code, and this is something we propose on changing. While each of these 3 systems are error free, we feel that we can speed up and consolidate the process.

5. New Process Efficiency One consolidated database Ensures security
User friendly
Michael: Our proposed database consolidates what Paychex’s 3 current databases do, all in one. Its user friendly interface enables client service representatives to do everything from enter new clients into the system, check individual’s 401k account balance, deferral rates into their 401k, overall company balances and much more. It provides a report that pulls who the Plan Administrator/authorized contact is associated with each of the clients to more quickly enforce security of information. It has a client billing information feature when the end of the month comes, and Paychex is ready to send out their monthly statements, and a calling list for each client if they need to be reached after any additional follow up research about their account inquires. This database encompasses all of the features that your 3 current databases have – but is a one-stop-shop in finding all of the information that is needed for 401k client questions/concerns.

6. ERD
John: talk about the ERD and the information that each of the tables contain

7. Database outline/Presentation
Reid – didn’t know what to put on this slide (or if we needed it) but I figured you could do the brief run through of the database since you made the final corrections

8. Conclusion/Business Value
We have converted what three databases could do, into one more efficient database
More user friendly and easier to find information
Increased customer service
Decreased time waiting for answers
Kayla: just say how this adds business value, lemme know if you need help coming up with things to say
Emphasize that it will increase customer service by reducing time spent on finding information and availability to generate important reports about their accounts

9. Any Questions?