Abhyarth assists solution providers in creating a reusable delivery mechanism. It consists of common technology framework based on industry standards, covering development, testing and implementation processes. Abhyarth also assists solution providers by providing relevant domain knowledge. This consists of explaining the changing business models the banks are adopting, changing customer preferences, quality expectations and their implications in a 24x7 world, etc.

Associative Expectation Shift

Banks need to meet growing user expectations by continuously enhancing their product and service offerings. They expect a back-to-back support from the solution providers by way of continuous supply of high-quality feature-rich products, reliable delivery mechanisms, prompt delivery capability, consistently high quality and sufficient support bandwidth to shorten occasional system downtimes.
To meet this expectation, solution providers need a nimble footed delivery mechanism. Increased solution complexity leads to an increase in solution turnaround time, once the requirements become clear. This delay is not be acceptable to the banks, as a delayed product launch may put them in league with market followers rather than market leaders.

Delivery Challenges

Considering that the scope is never frozen, solution complexity is already high, delivery timelines are unrealistically stringent, uptime expectations are near 100%, online upgrades on running systems are risky, Technology and business model changes are unpredictable, skilled development / implementation manpower supply is swinging in tandemwith industry buoyancy perception, and

lack of development standards bring in higher individual resource dependence, vendors have a tough time keeping their delivery promises, to say the least.
Internally, vendors want to make their individual project efforts reusable, and create a homogenous product line out of multiple projects. This is easier said than done, considering the architecture, technology and functionality of each of these projects is similar but not the same. The challenge is in terms of carving out the commonalities from projects, conceptualizing a common framework, and implementing and testing it early so that more and more projects can benefit from it, before its technology platform and functional appeal become outdated. For the product line to be meaningful, it needs to be driven more by the futuristic vision, rather than by making the best use of old project assets.

The only way out for the vendors is to have

• The ability to predict the future ahead of their competition, so as to be at the right place at the right time, and
• A reliable, tried and trusted, flexible, generic, extendable and person independent delivery mechanism, to provide extensions to existing systems

This is possible if they have both a deep and a wide view of the direction and pace of industry movement, the ability to convert this vision into business potential, and the ability to convert the business potential into deliverable products.