Introduction to the Orchestrator Module
The module Orchestrator automatically runs workflows created by the Engineering module.
Workflows are used to exchange information between the module, station and machine and can be created in the Engineering module. The support of the Information Router module allows the workflows to be executed on different machines.
A workflow consists of the incoming information (argument) of a station or machine and multiple work steps that contain the outbound of the requested information.
Example of a workflow process:
| Type of information | Description | |
|---|---|---|
1. |
Argument (not a work step because the Orchestrator module is not yet active) |
Trimming machine sends a request to Orchestrator: How many working hours can drill 001 be used before it needs to be replaced? |
2. |
Orchestrator receives the request. |
|
3. |
Work step |
Orchestrator sends the request to Tool Management. |
4. |
Orchestrator receives the response to the request from Tool Management : Drill 001 may be used for 5.6 working hours from the current point in time before it has to be replaced. |
|
5. |
Argument and work step |
Orchestrator sends the response information to the trimming machine. |
Workflows that are running or have already been executed can be viewed in Orchestrator , along with their details.
Main Function
-
Monitor workflows
-
Run workflows automatically
Roles and permissions
All modules of the Nexeed Industrial Application System are based on permissions. Depending on the permissions, different functions are available in a module.
To enable functions, the user is assigned a role based on the desired permission. Permissions are managed in the Multitenant Access Control module.
The standard configuration of the module includes the following roles:
| Authorization | Monitoring Reader | Orchestrator Admin |
|---|---|---|
Read rights for monitoring |
x |
x |
Access to all interfaces |
x |