Service

Services represent the physical locations of the business, such as shops, restaurants, workshops, etc. These services also are used as terminal nodes, as they group products that share a common configuration.

All services are nodes, but not all nodes are services.

Some of the data defined at the service level are as follows:

  • Time zone. Establishes the time zone of the physical store and is crucial to configure it correctly so that Orquest can manage the received data.

  • Name. It is established according to the business needs.

  • External identifier. It will be used to make API requests, so it is highly recommended to configure it for integration.

  • First day of the week. Determines the first working day of the week.

  • Location. Physical store location used, for example, to control those clockings that must be linked to a specific location.

Store configuration

The graphical user interface (GUI) of Orquest allows for specific configuration for each service or store within the business. Some data included in this section are as follows:

  • Store times. Service hours or the physical store hours. Various schedules can be configured according to the needs of the service. For example, a general schedule and one for the summer months with intensive workdays.

  • Store params. Allow configuring all kinds of behaviors at the service level: planning management, report generation, global settings, etc. Once they are activated in the business configuration (Defined parameters), they can be selected and configured in the store configuration.

  • Employee roles. These roles are assigned to employees and allow the engine to plan at a certain time considering certain roles. Are optional and are created according to business needs. In a specific period of a given day, an employee may or may not be present in the planning depending on the role.

At this point, it is essential to make a distinction between employee role, employee category and user role:

  • Employee role

  • Employee category

  • User role

Establishes the function for the employee and allows planning according to previously defined criteria for the role. Defined at the service level, it is optional and is related to planning.

Establishes the position that an employee can occupy within the business. Defined at the business level, it is mandatory and is related to the contract.

Establishes the permissions and restrictions that a user will have within Orquest. Defined at the business level, it is related to the use of the application.

Once the service is defined, the next element in the hierarchical tree of a business would be the product, considered the standard planning unit.