StaffPlanner : for you
Is StaffPlanner for you ?
You have many shifts (days, evenings, nights...)
In each team, there are many shifts covering all moments of the day and night. the workers come and leave at any moment... and HR management becomes awkward.
StaffPlanner is operational in hospitals having more than 2000 people, in services as complex as operation quarters. You can build your planning in manual mode, with help of cycles or the automatic planning, decentralised upon field services. The workload of HR departement becomes lighter and more effective based on a work by exceptions...
You want to see clear...
You have not enough time to get involved at field planification and the number of people to manage is large.
You wonder if the rules are respected as far as worktime, arrivals, departures, recoveries, guards... are concerned.
StaffPlanner is a tool dedicated to clarity and standardisation, but indirectly promoting equity between workers and teams. At any moment you know what is in process in services and workshops.
Data can be compared, deviations observed and statistics computed...
Administrative shifts are versatile
The number of parttimes is increasing and their variety too. For example : a 50% would work from Monday to Wednesday during the first week and the following week from Thursday to Friday. This kind of shift complicates the follow-up of balances, holidays, illnesses...
But this kind of shift is frequent in administrative teams, that StaffPlanner can manage easily.
Our customers choose StaffPlanner first for the management of their operational teams and then extend its use to the administrative services.
You recompute manually the "overtime" (for the payroll)
Each month, some of your colleagues analyse manually all the shifts made during the period in order to extract overtime (night shifts, sunday shifts, "cut" shifts, guards...) and then re-encode this data in the payroll system.
The STPPay module automates the overtime process as far as the extraction or the injection of this results in the payroll system are concerned.
The holidays follow-up is infernal...
Your colleagues have various work schemes. They take their holidays in the next year. When they work on a bankholiday, they may recover it on a other day, but in a specific delay. They take half-time holliday, even hours of holidays at a time. How to compute holidays for half-timers ?
This is a basic topic of StaffPlanner, justifying the acquisition of the tool. StaffPlanner has rules helping the initialisation of holiday cards at years begin, based on function, length of service, individual data or other specific rules...
I have punching machines, but...
Your punching system is working, but it delivers no real management advantage. Yes, you see arrival and departure times, and anomalies... But you are not helped for your planning, nor for statistics...
Wouldn't it be more interesting to inverse the problematic ? What comes first is the planning and field activity, with shifts and absences planned weeks before, and not the checking. The "D" day, the worker punches and his checkings will be compared with the shift programmed on planning. This shift will be "smoothed" according to a specific ruleset, producing an adapted shift, including overtimes, bonuses (STPTime module)...
The shifts, smoothed or not, will then be interpreted for the payroll, according to specific extraction rules (STPPay module).
Checking and smoothing are functionalities dedicated to correct planning according to reality. All planning functionalities remain available, independantly from punching system (holiday management, absences, illnesses, payroll extractions). And you can migrate progressively your teams to punching phylosophy, services by services or worker by workers. No matter.
In brief, if you have a punching system, we import the checkings in StaffPlanner. If you have no punching system yet, we offer to deliver and install our punching devices (from Pyrescom), totally integrated in the StaffPlanner software suite.
My organisation has 50 people only
Yes, but shift combination is complex, as in the large organisations. What's different is the number of teams.
We have a licence for small sites (lower than 100 people), compatible with the free relational database "Firebird" (efficient and ideal for cost limitation).