All shifts are planned for Locations. Manage locations under the ‘Locations’ heading.
Locations are set up for those units for which planning is done. Locations are created and managed for each unit independently. Employees can be attached to the locations of their own units, so that shifts to these locations can be planned for them. Work shift planners have visibility of the planning in their own unit.
Mandatory fields when creating a location are name and calculation unit. Calculation unit is the identifier for the location and it is inputted as string.
Locations are a nested hierarchy. If location is defined with category, then the location is a child for another location.
Valid from and valid until - fields prevent planning to the location outside these dates. Planning cannot be done to a location to those dates that are earlier than valid from, or to dates that are later than valid until. If the field is empty then planning can be done.
Creating a Project
The service automatically creates projects corresponding to the locations. Changes made to locations are automatically updated to the corresponding projects. Termination of the location terminates the project. Deleting a location deletes the project. Changes to projects related to locations must be made to the locations, as the data of the corresponding location directly overrides the changes made to the projects. Editing this type of projects is blocked in the Projects menu in the Worktime -section.
The project code will be the unit code that connects the project to the location. Project name will be the location name. Projects are attached to parent project which consists of the data of the unit for which the location are created. The top project is a project with the name of the unit and the project code is the unit code.
A project created in Location can be a person's default project, same as projects created through Projects. If you want to assign a project manager to a project created through a Location, you can do so from the Worktime> Administration> Persons> Projects Managed by person settings.
Proposal of calculation unit
The bottom of the page shows the next available planning unit. This functionality advertises automatically the next unused planning code. This helps the person editing the data to prevent situations where planning unit is already used on a location in some other unit. Next available code is identified by finding the biggest number used as planning unit in any of the units and this value is incremented with one. Those calculation units that cannot be interpreted as number are ignored.
The next available planning unit shows five levels. Planning units can be set up as a string so that these levels are split by / - character. It is possible to use this to distinguish business identifiers. For example planning unit 50/200 could mean business unit '50' and location '200'. The location creates the worktime project, with project having the planning unit used as the project code. Events that are targeted to projects having project code splitted by sepator character, like '/', can in the data export be targeted to all of these levels. For example salary export could contain work costs that are targeted to a specific customer and to specific location at the same time.