Horus Private Space
Collaborative Business Process Engineering in Private Business Communities
Collaboration in Business Process Engineering YES – Access to project results from public social nets NO! This is the typical use case for a Horus Private Community, meeting in a specially designated Private Space. It lies either in the Horus Cloud or is part of a corporate infrastructure and is subject to applicable safety regulations. Access to the collaboration platform is only granted to internal users or external users that are seen as part of the business community.
Setting up Private Spaces
Private Spaces on Demand are available for customers wishing to apply a best practice solution. Private Spaces lie in the Horus Cloud and are readily available after a few configuration steps. The Horus software GmbH specialists or an authorized Horus Alliance partner will take over the customer-specific implementation of a Private Space for customers who have very specific requirements and enhanced safety rules.
The Basis: Collaboration in Web 2.0
Collaborative Business Process Engineering first of all means using Web 2.0 collaboration and communication technologies. Both, the tools of Horus Freeware- and the Enterprise product line are prepared for the interaction with Web 2.0 technologies. Insofar Horus does not have any special technical requirements towards the underlying collaboration platform: In the Oracle world the WebCenter Suite can be used in interaction with Oracle BPEL. But also Open Source-, Microsoft- and IBM Websphere platforms are possible. The important basic functions for a Horus Private Space are:
- Wikis, blogs, individual web publication sites
- Discussion forums, chats, presence & instant messaging
- Tagging and linking of models, creation of Enterprise Mashups
- Integration of Horus Public Space
Support for Collaborative Modeling
The Best Practice solutions for Horus Private Communities stipulate so-called collaboration transactions. These are tasks that are fulfilled by numerous members of the community in line with modeling and simulation. The Horus tools are already pre-configured for these transactions. The transactions are then realized directly on the underlying collaboration platform. The most important transactions can be classified as follows:
- Review and approval of models
- Exchange of models and model fragments
- Extreme Modeling: collaborative modeling and simulating
- (Incremental) integration of models
