Structure of the Organizational Unit (OU)
In Avendoo, an Organizational Unit (OU) serves to map teams, departments, or other groups within an organization. An Organizational Unit can be assigned when creating a user or author account in Avendoo. This allows the OU to be used as a filter value for various functions such as participant rules, the Cockpit for Team Leaders, or reporting.
Variants
The following presents three possible variants for structuring the OU.
Variant 1
- Hierarchical (the longer the OU, the smaller or more precise the group of people)
- with components of fixed length (e.g., 3 or 4 characters)
- with a uniform separator between the levels/components (e.g., “-“)
Example: EHR-KMU-PB1-TL1
Explanation of the Abbreviations
EHR: The Company Division (HR, Development, Research, Sales …)
KMU: Sub-area (Call center, Customer Service…)
PB1: Location (Region or city code with branch number)
TL1: Team Abbreviation (e.g., there are several teams at one location)
Variant 2
- Hierarchical
- with components that can be of different lengths
- with separator “:” prefix for the meaning of the individual sections. This is necessary when the components are of different lengths, allowing different components to appear at the same character position.
- Examples of separators and prefixes:
- :co=
- :vg=
Example: re=Europe:co=DE:bu=Development Office:tu=IT MGMT SERVICE:vg=12345678
Explanation of the Abbreviations
re= Region (Geographical Classification)
co= Country/Land
bu= Business Unit / Company Division
tu= Technical Unit / Sub-area or technical classification
vg= Abbreviation of the supervisor who leads a team
Variant 3
- Non-hierarchical; the OU directly designates a team with the same direct supervisor
- The OU consists only of the supervisor’s username (e.g., personnel number, branch number, cost center, branch designation)
Example: 6890230
Entering OUs in Report Filters or Participant Rules
In report filters or participant rules, you can filter by OUs. To do this, you either enter the complete OU you are searching for, or you enter parts of the OU, using wildcards % or _.
EHR-KMU-PB1-%
An OU participant rule based on this character string would consider all users whose OU starts with “EHR-KMU-PB1-“.
%KMU-PB1%
This character string must appear somewhere in the OU.
EHR-KMU-PB_
All OUs that start with “EHR-KMU-PB” and contain exactly one additional, arbitrary character are displayed.
______ (6 Underscores)
You want all OUs with a length of at least 6 characters to be displayed.