PPO has a sophisticated planning model that calculates the planned hours per resource per project per day which is then rolled up into weekly/monthly/quarterly/yearly views across the planning reports & dashboards.
Due to the above, it can be difficult for users to recognize and validate planning hours/costs when a resource allocation record or task is planned over multiple months. As an example when a user plans a resource to work on a project for 30 hours over a 3-month period, the user might expect to see 10 hours per month but will see Jan (10.65 Hours), Feb (10.16 Hours), Mar(9.19 Hours) which could differ due to the number of working days not being the same for each month in a year. The above can also be applied when viewing planning costs for resources or when comparing to actual hours/cost for billability % target.
Some companies are moving to a model that allows employees/contractors to work less than the standard 5 days a week which often adds in a billability % target if there isn't one already and we need a simple way to keep track of this, a mechanism to apply to our already existing planning model and the necessary calculations & views to support PMs & Billing processes when planning out project work and validating the planned project work against actual time.
A suggestion would be:
- An employee work calendar that allows one to specify working days and hours
- A global working day value per month for an instance (e.g. every month has 20 days)
