A plan may appear sustainable until closures and absences are considered. The availability of people is an operational data to be verified before assigning work and comparing loads.
Users, roles and availability
- Account management requires authorized profile. Before creating or modifying a person, check whether the account already exists.
- Check profile data, EDU, privilege level and daily availability. Availability is an operational data to be agreed upon, not a value to be maximized.
- Assign only the necessary role. Changes to privileged profiles and the assignment of SuperAdmin or Key-user are reserved for the SuperAdmin.
- Complete the activation through the provided password setting flow. Then check access and visibility with the profile concerned.
Calendar of closures and absences
- Open the Closing Calendar from the settings to consult the scheduled non-working days. Don’t confuse them with the absence of a single person.
- For individual unavailability, use Planned Absence Management. Managers can consult user absences according to available permissions.
- Check period, person and context before saving or editing an absence. Use a demo range and verify that it is the one required.
- Re-read workload and planning in the relevant period. An incorrect calendar or availability can alter the interpretation of the capacity.
Putting this into practice
When a delivery falls near a deadline, check the schedule and resources involved. The date on the Gantt must be read together with the time actually available.
Learn more about Orchestris.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.