|
Architecture Overview
The area on the left two-thirds of the diagram is the BPM Centric Application Management core. It provides a standardized workflow environment for all Process Automation application suites which are represented on the right side of the diagram.
All transactional operations are by definition an extension of specifically designed process workflows. The core provides a common Application Bus Interface which allows multiple Process Automation Suites and their components access to the core and any other suite component.
 Process Management Layer
Central to the core is the Process Management Layer which is a BPM workflow
engine. There is a Visibility Layer above and a standardized task processing
layer below called the User Application Screens Layer. The interface between
the BPM workflow layer and the processing layer is a standardized Work Queue.
Process States, Waits, Boxes and Arrows
There are two important concepts in workflow, States and Waits. States are
points along the process flow where the process must pause or wait for the
completion of a task (or set of tasks) before continuing to follow the flow.
Tasks within a state can require their own pause or wait.
Workflow activities which require no wait states can execute task actions
directly, while tasks requiring manual screen operation or other automated
systems would “Push” the work to the Work Queue and pause. User workstation
management screens then Pull work from the Work Queue and process it through
application suite screens. Once the work step is complete, the workflow is
“signaled” to continue as designed.
Process Workflows are best understood as graphically represented boxes and
arrows showing the transition from one box or state on another. LIT requires
graphical representation of workflow.
|
