Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complying with regulations #448

Open
mimischi opened this issue Nov 26, 2017 · 5 comments
Open

Complying with regulations #448

mimischi opened this issue Nov 26, 2017 · 5 comments

Comments

@mimischi
Copy link
Owner

mimischi commented Nov 26, 2017

Note: This issue is work in progress and will list different aspects of what we need to consider.

Clock does not do any checks when exporting finished shifts, thus a user can export all worked hours they have done during a month. For example, a user may have worked more hours than specified in their contract -- this would get exported into one sheet, without considerations of the actual overtime.

Regulations

  1. Allow users to work 150% of their contractual work hours in a given month (accumulate overtime).
  2. Allow users to work 80% of their contractual work hours in a given month (reduce overtime).
  3. The user may accumulate a total of 200 overtime work hours, which were not exported yet.
  4. During long shifts, an automatic pause time is subtracted from the total work time:
    • up to 30 minutes after working for 6 hours
    • up to 45 minutes after working for 9 hours
    • Examples can be seen at the bottom.
  5. A shift must not be longer than 10 hours.
  6. Overtime from one month should be transferable to another month.
  7. Accumulated overtime at latest must be exported 12 months after being generated.
  8. Users may define a shift as vacation or sick leave. This shift will be displayed with all other shifts and the work time will be part of the total sum for that month.
  9. Export of different variations:
    • On a per-contract basis
    • Per project basis
    • Total worked time

Examples for pauses

  1. Work time: 6h15min
    • Pause: 15min
    • Total work time: 6h00min
  2. Work time: 6h45min
    • Pause: 30min
    • Total work time: 6h15min
  3. Work time: 8h50min
    • Pause: 30min
    • Total work time: 8h20min
  4. Work time: 9h30min
    • Pause: 30min
    • Total work time: 9h00min
  5. Work time: 9h50min
    • Pause: 45min
    • Total work time: 9h05min
@mimischi
Copy link
Owner Author

mimischi commented Mar 1, 2018

@sheepyhollow Im Bezug auf Punkt 5: A shift must not be longer than 10 hours. Nachdem Gespräch mit Kathi wurde ja irgendwie klar, dass solche Dinge eventuell nicht explizit vom System verboten werden sollten. Wir sollten die User beim Speichern warnen und gerade beim Export erneut drauf hinweisen.
Allerdings sollte die Aufzeichnung der Schichten auch die Wahrheit widerspiegeln. Wenn HiWis Nachts arbeiten/Überstunden schieben/sonstiges, dann sollten wir diese Aufzeichnung auch erlauben.

Oder?

@sheepyhollow
Copy link
Contributor

ja, sehe ich auch so.

@sheepyhollow
Copy link
Contributor

Es gibt auch das Szenario, dass HiWis einen Vertrag über z.B. 2 Monate haben, aber in einem kürzeren Zeitraum alles abarbeiten. Solche Konstruktionen werden oft auch von Dienststellenseite vorgeschlagen, da man anders nicht gescheit vergüten kann. Fragt sich, wie da das AZK mit umgeht.

@chgad
Copy link
Collaborator

chgad commented May 30, 2018

Considering point 4: The User should be informed about this at least as soon as the shifts duration (while actively clocking) reaches the 6/9th hour and preferrably again when clocking-out.

@sheepyhollow
Copy link
Contributor

iirc we do not have anything active to remind users - at least at the time being.
I think we agreed that all user information and current status will be updated when the user logs on/opens the website. But currently we have the counter (shift duration) and that would be the place to show information like automated pauses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants