Omnibus Integration Benefits


Significantly Simpler Development

A point-to-point integration between every pair of n tools, we need n x (n-1) / 2 number of integrations. Accordingly, for a simple case of 5 tools, this amounts to 10 integrations and just by doubling the number of tools to 10 will result in a 4.5 fold increase in number of integrations to 45. On the contrary, Kovair Omnibus is based on the ESB architecture which needs 5 and 10 adapters, just one per tool! Moreover, replacement of one of 5 and 10 tools needs replacement of just one adapter, a far cry from the redevelopment of 4 and 9 integration codes respectively.

Traceability with Change Impact Analysis

Kovair Omnibus’s central framework allows creating and managing Traceability relationships between artifacts from multiple (more than a pair of) tools. This is not possible with Point-to-point integration where without a central framework only two tools are integrated at a time. Moreover, due to its flexibility in relationship management, Kovair Omnibus promotes multi-tool proactive and reactive change impact analysis, which is impossible in the case of both point-to-point and single-vendor integration solutions.

Protects Investments

Kovair Omnibus is based on a standard set of web service based APIs. Without any special requirement on the tools, Omnibus can integrate tools from different vendors, including internally developed tools. This means all the tool investments by a development organization are protected and enhanced with integrations and the training and familiarity of people using these tools is also protected from an investment perspective.

Process Automation without Boundary

Through its built-in process automation capability (Omniprocess Workflow Automation engine), Kovair Omnibus creates a cross-tools process and automates it for a transparent no-overhead implementation with a much larger success potential. The typical example is that of a Requirement that starts life in a Requirements Management tool, is reviewed and approved by stakeholders in a Project Management tool, is implemented by a developer in an IDE, and tested by testers in a Test Management tool. Kovair Omnibus automates the whole process for all these users irrespective of the difference in tools and locations.

Best-of-breed Tools for Best Functions

Kovair Omnibus allows integration of multiple third party tools from different vendors (for eg. VSTS Designer, Rational, Eclipse, Subversion, TFS, ANT, JUnit, Quick Test Pro, Clarity etc.) for the same function. What is even better, it can support simultaneous usage of multiple tools from multiple vendors in a single tool ecosystem. This allows organizations to select best-of-breed tools available in the market without locking themselves into a single-vendor solution.

Flexibility of Integration Business Rules

Kovair Omnibus allows creation and management of integration business rules independent of the individual tool adapters. Unlike point-to-point and single-vendor integrations where the logic is hard coded in the integration codes, platform adapters do not have any hard coded embedded business rules and are configurable with mouse clicks.

Analytics and Dashboards

Once Kovair Omnibus has all the artifacts and Meta information about the artifacts (e.g. not just the Requirement but the information about the Requestor, Type, Priority, Approval status, Approver, Lifecycle status, etc.) in its repository either by replication or federation, you can create all sorts of dashboard metrics and reports for those data in real-time. These reports provide valuable insights about the whole cross-tool process, which is often impossible or difficult to get.