MOVE-FLOW is a research work in WfMS whose targets to solve the scenarios mentioned in the overview section.
SaaS-Flow Targets:

1. SME (Small Medium Enterprises) that want to build the process using standard tool and host it to the engine and use it without any development efforts.  Also to be able to pay for hosted processes only.
2. SME (Small Medium Enterprises) that wants to build workflow applications and don’t want to pay for full engine license.
3. Supply chain process that needs to be executed over several applications and work environment.
4. E-governmental process as in scenario 2

MOVE-FLOW works with concept of Software as a Service SaaS. SaaS is a model of software deployment where an application is hosted as a service provided to customers across the Internet without the need to install and run the application on the customer's own computer.

MOVE-FLOW architecture is based on component based and service oriented architecture.  SaaS-Flow is a WfMS that works with the concept of SaaS.  Clients don’t need to host the engine to be able to use it in their applications.  They host their processes at the engine without the need to host the engine itself.

The system is client/server architecture.  It is based on three major components: engine, Task Manager and pluggable agents.
MOVE-FLOW architecture executes process activities as a set of pluggable services.  It considers human tasks as remote services executed by human.  Task Manager is called as a remote service using pluggable agent.  This separation provides great flexibility for portability and interoperability between workflow engines.

The use of XML webservice enabled exposing engine's functions to external systems independent of their location or working environment.  The use of Component architecture facilitates extending system functionality without the need to rebuild the whole system. 

MOVE-FLOW engine supports separation of concerns.  Where the application developer can build and test their application without the need to communicate with the engine.  At the same time Business Process Designers can build their processes and test it without the need to communicate with the application.  That is done through the separation of process execution from application execution.  Furthermore, this SaaS-Flow workflow engine architecture can also be used as a general reference for workflow management system architecture because of its generic design, flexibility and generality.