Workflow Configuration
This chapter describes the process to create and maintain workflows in Infor MES. The Workflow functionality offers a low-code platform that enables users to design and implement a series of actions to manufacture a product.
This enables you to effectively model and manage comprehensive production processes, ensuring adherence to established procedures and facilitating thorough tracking.
Workflow configuration requires the core model functionality to be pre-defined and configured. Some settings depend on functionalities covered in different chapters, requiring additional configuration as detailed in other sections. The workflow functionality is frequently used alongside both the production and quality functionality.
A workflow is organized in a hierarchical structure that includes:
- : Workflow Routings are based on the Core Model routing concept, and are configured to link to the other workflow concepts below. A Routing consists of one or more Operations.
- : The macro steps required to produce a finished or semi-finished good. An Operation consists of one or more Phases.
- : The operations are divided into distinct phases. An operation is considered completed only after the related phases are completed. A Phase consists of one or more Actions.
- : An action is a function that performs a set transaction. Actions allows you to control the individual activities within a workflow. All actions must be completed to finish a phase. A phase is considered complete only when all related tasks are finished. These are the different types of actions available:
- : These actions are operator-led activities such as scanning a package for consumption and conducting inspections.
- : These actions are machine-based activities such as reading and writing values from the PLC as well as obtaining weight measurements.
- : These actions perform background calculations and assign a values to transition parameters.
- : Transitions are connections between operations, phases, or actions that define the activity flow based on the progress and outcomes of these actions. This facilitates looping between actions and branching, in case of exceptions.