Horus Private Community
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. It is part of a company infrastructure and it underlies the respective 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.
Customer-specific build-up of Private Communities
A Horus Private Community is never a completed software product that is simply installed “out of the box”. Much more it is a best practice solution that is configured customer-specifically and then integrated into the customer’s IT infrastructure. In some cases an access to Horus Public Communities is set up. The implementation of a Private Community is done by specialists from Horus software GmbH or by an authorized Horus Alliance Partner. Also interesting: The possibility to use Private Communities as On Demand Service (SaaS).
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: It can be used the world of Oracle Beehive or WebCenters, each in interaction with Oracle BPEL. But also Open Source-, Microsoft- and IBM Websphere platforms are possible. The important basic functions for a Horus Private Community are:
- Wikis, blogs, individual web publication sites
- Discussion forums, chats, presence & instant messaging
- Tagging and linking of models, creation of Enterprise Mashups
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. This takes place in line with a Rapid Implementation Procedure by using Horus Best Practice solutions. 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
