Super Time Clock - *Challenge* hahah

[harleyskater]

** suggestions and open conversation would be helpful **
Attached - Database Model for the Timeclock

I built a Time-Clock as part of an Access project a couple months ago. It's not 100% in use at the moment and my Access projects tentative release date is set somewhere in July This particular timeclock is not just a simple timeclock, it allows employees not only to Clock In but to Clock In on specific processes of defined projects that are going on throughout the business. Those processes have a large amount of ways they can be grouped for reporting purposes. That part of the project is working great.

Ok so this is what has been asked of me. I need to take the timeclock that allows for an employee to Clock In on one process and make it so the employee can Clock In on multiple processes. These processes then have to be given a ratio or percentage so they can be split properly. The reason for this is if you are clocking in on multiple processes and working them concurrently, they might have different workloads.
IE. Process 1, 2, 3 are different instances of a process. This process has to be defined indepently for reporting purposes. Being able to ClockIn on process 1, 2, 3 at the same time and work them at the same time will save a tremendous amount of time end the end but they have to be reported seperately. If process 1 is 20 units, process 2 is 4 units and process 3 is 100 units- that has to be represented.

I know this is a big post - I will be by the computer working on this. I have a lot of ideas but I think it would be very helpful to get some professional opinions Thank you !

 

[georgedwilkinson]

Just an idea. Store a "timed event" or "timing event" or "session" in its own table and utilize a junction table with the % for the event's relationship to the processes being timed.

So what happens if the employee starts a new process while still being timed on the old process(es)? What happens if the employee finishes a timed session and the percentages he had originally indicated were wrong? Will he be able to reconcile? Will he even care enough to reconcile? Will he even have time? etc.

This sounds like a pretty slick project. Your stakeholders are very brave.

 

[harleyskater]

To answer your questions,

"So what happens if the employee starts a new process while still being timed on the old process(es)? "
The goal is to have 1 ClockIn for multiple processes. They will have to ClockOut and then ClockIn again for the Next Set of Process(es).

"What happens if the employee finishes a timed session and the percentages he had originally indicated were wrong?"
They can be changed through a form for minipulating the employee time information, we already have an employee works with the times

Will he even care enough to reconcile? The management will be the ones clocking in on multiple processes

Will he even have time? hahah doubtful

I am going to think about your idea for a little bit I will be posting again soon

Thank You

Just an idea. Store a "timed event" or "timing event" or "session" in its own table and utilize a junction table with the % for the event's relationship to the processes being timed.

So what happens if the employee starts a new process while still being timed on the old process(es)? What happens if the employee finishes a timed session and the percentages he had originally indicated were wrong? Will he be able to reconcile? Will he even care enough to reconcile? Will he even have time? etc.

This sounds like a pretty slick project. Your stakeholders are very brave.