MARIFLOW A WORKFLOW MANAGEMENT SYSTEM FOR MARITIME INDUSTRY

The aim of MARIFlow Project is to provide a prototype of an architecture for automating and monitoring the flow of control and data over the Internet among different organisations. This "electronic medium", capable of delivering value-added services to the participants, encompasses many different technological areas: from communication to security, databases, transaction support and agents. The project will make use of these technologies to produce a workflow management system. In particular, the goal of the project is to develop an adaptable workflow engine through which the activities of the different participants in the maritime industry can be harmonised, combined, and expanded through better tracking of functional dependencies and documents, improved data access and handling, and lower administrative overheads. The MARIFlow system is based on data-centric approach, that is, execution of activities on a host machine is triggered by arrival of data, and generates further data that is sent to participants in the process, where upon arrival may trigger further activities. Nevertheless, the important characteristic of such processes is distribution, not just in terms of geography, but also in terms of ownership, responsibility and autonomy. This paper also addresses the important issues such as security of the documents as well as the tracking of data and documents, for monitoring purposes.

[1]  Gustavo Alonso,et al.  Flexible exception handling in the OPERA process support system , 1998, Proceedings. 18th International Conference on Distributed Computing Systems (Cat. No.98CB36183).

[2]  Amit P. Sheth,et al.  Specifying and Enforcing Intertask Dependencies , 1993, VLDB.

[3]  Weimin Du,et al.  HP Workflow Research: Past, Present, and Future , 1998 .

[4]  Amit P. Sheth,et al.  An overview of workflow management: From process modeling to workflow automation infrastructure , 1995, Distributed and Parallel Databases.

[5]  Nesime Tatbul,et al.  Design and Implementation of a Distributed Workflow Management System: METUFlow , 1998 .

[6]  Gustavo Alonso,et al.  Towards a Platform for Distributed Application Development , 1998 .

[7]  Munindar P. Singh Synthesizing distributed constrained events from transactional workflow specifications , 1996, Proceedings of the Twelfth International Conference on Data Engineering.

[8]  Umeshwar Dayal,et al.  A Transactional Model for Long-Running Activities , 1991, VLDB.

[9]  Amit P. Sheth,et al.  Scalable and Dynamic Work Coordination and Collaboration Systems , 1995 .

[10]  Mathias Weske,et al.  The WASA Approach to Workflow Management for Scientific Applications , 1998 .

[11]  Gerhard Weikum,et al.  Enterprise-wide workflow management based on state and activity charts , 1998 .

[12]  Gustavo Alonso,et al.  Exotica/FMDC: A workflow management system for mobile and disconnected clients , 2004, Distributed and Parallel Databases.

[13]  Report from the NSF workshop on workflow and process automation in information systems , 1996, SGMD.

[14]  Amit P. Sheth,et al.  WebWork: METEOR2's Web-Based Workflow Management System , 1998, Journal of Intelligent Information Systems.

[15]  D. Hollingsworth The workflow Reference Model , 1994 .

[16]  Umeshwar Dayal,et al.  Workflow Technologies Meet the Internet , 1998 .