Node

Once the business is established, the next element in the organizational diagram is the node. Nodes can be used to group services that share common characteristics. The definition of these intermediate nodes will always depend on the business configuration:

  • If the services do not have shared characteristics, the business does not require intermediate nodes.

  • If the grouping of services is more complex, the business may require multiple intermediate nodes and even add more nesting levels.

The organizational structure of a business is defined by the set of nodes and the hierarchical relationships between them. Within the Organizational Diagram, there is a root node that shares the name with the business and supports the entire structure.

Configuration

Thanks to the CS team, a general configuration for the different nodes is established, defining the following sections:

  • Regulations. A set of legal restrictions applied to a node for a specified period.

  • Users. Each user can access the information of the node they belong to and also that of the descendant nodes.

  • People. Employees associated with a specific node.

  • Tasks. Selection of locations configured at the business level.

  • Contract types. Possible contracts that can be applied to an employee, selected from those configured at the business level.

  • Day types. Used to define service schedules, needs templates, availabilities, etc. They can be defined at the node level, although some are already defined at the system level in Orquest and are available for use: working days, holidays, Monday, Tuesday, etc. Restrictions can be applied by day type.

  • Calendar. Allows assigning predefined day types to specific dates.

  • Reference days for forecast. The day taken as a reference to calculate the forecast. By default, the day of the week (Monday, Tuesday, Wednesday, etc.) from the previous year is taken. However, there is an option to edit this reference day and select another one instead.

  • Shift patterns. Schedules that can be applied to employees.

Anything defined in a higher node is inherited by the lower nodes. However, it is possible to modify the inherited parameters.

Not all nodes are equal; some nodes imply a higher level of complexity: the services.