BPIS Evaluation

Jenz & Partner BPIS product suite evaluations are based on a structured schema. This makes it very easy to obtain an impression about strengths and weaknesses of specific products.

Our evaluation methodology is based on three pillars:

Product features
Integration with the technical environment
Productivity

Very often, product evaluations just consider product features. In reality, this is of little practical value, since the enormous costs incurred by integrating the product suite with the existing technical environment are not taken into account.

Moreover, we evaluate how the product suite supports critical processes, such as modeling and development processes. During the life cycle of a product suite, such processes are performed over and over again. Shrinking time-to-market is not just a buzzword. If a product suite provides nice features, but does not support labour-intensive processes well, the product will turn into a burden. Human resources are a valuable factor and productivity-enhancing features are a “must have”.

We do not ask vendors to complete a questionnaire. This has proven to be inadequate, since vendors often provide insufficient or ambiguous information. Instead, we consult the product documentation and discuss remaining issues directly with vendor specialists. Additionally, hands-on experiences with products in-house or at client sites contribute to our product evaluations.

Our Technology Briefing provides valuable information about BPIS concepts, services, APIs and protocols. It is designed to complement BPIS Evaluations and should be consulted before and during evaluations.

The following BPIS Product Evaluation Profiles are available:

We look at other vendors and their product offerings, too. Here, you will find brief descriptions of other BPIS product suites. Currently, the following “What-it-is” descriptions are available:

Microsoft BizTalk Server 2000