Federated database systems for managing distributed, heterogeneous, and autonomous databases
ACM Computing Surveys (CSUR) - Special issue on heterogeneous databases
The action workflow approach to workflow management technology
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
Workflow support across organisational boundaries
ISCNZ '96 Proceedings of the 1996 Information Systems Conference of New Zealand (ISCNZ '96)
Establishment of Virtual Enterprise Contracts
DEXA '02 Proceedings of the 13th International Conference on Database and Expert Systems Applications
Managing inter-organisational workflows in eGovernment services
ICEC '04 Proceedings of the 6th international conference on Electronic commerce
VirtuE: a formal model of virtual enterprises for information markets
Journal of Intelligent Information Systems
Deploying and managing Web services: issues, solutions, and directions
The VLDB Journal — The International Journal on Very Large Data Bases
A virtual enterprise design method based on business process simulation
International Journal of Computer Integrated Manufacturing
International Journal of Agent-Oriented Software Engineering
A case-based framework for workflow model management
BPM'03 Proceedings of the 2003 international conference on Business process management
Ensuring reliability in B2B services: Fault tolerant inter-organizational workflows
Information Systems Frontiers
| Hi-index | 0.00 |
Because of the many forms a Virtual Enterprise (VE) can take, there is no single model of what type of approach to workflow management is most appropriate. This paper is based on an analysis of the different types of business practice that lead to the formation of VEs. A number of different workflow scenarios are depicted, and four specific issues are then discussed. The first is the recognition of the different life cycle stages of a Virtual Enterprise. The second is the problem of workflow case identifiers across organizational boundaries. The third is the need or otherwise for shared databases to support the different scenarios. The fourth is the question of the protocol for passing work in loosely-coupled workflows. Some ideas for future work are finally proposed.