Increase CA Gen flexibillity

How can flexibility be increased?

Jumar-Flex-smallJumar FLEX is an automated approach to isolating functional areas of a tightly-coupled CA Gen system allows a range of future strategies to me more easily executed.  

Functional area isolation is a measured and proportionate way of approaching the problem of a CA Gen system where high levels of interdependency between models severely limits the ability to modernise that system. It opens up the option to replace discrete components with a COTS package, migrate them to native code or safely discontinue the component, as well as other options.FLEXytthumbnews

<< Watch our 2 minute Jumar FLEX video

Unlike a ‘big bang’ componentisation exercise, Jumar FLEX considers each functional area separately, and applies the isolation approach only to those where the business will derive a benefit.

Jumar uses world-class automation tooling and the approach is based upon sound CBD principles.  Its ultimate aim is to transform and future-proof a CA Gen portfolio, delivering cost-savings, risk-reduction and greater technical flexibility.

This approach is only possible and practical with the help of Jumar’s unique automation

Who can benefit?

Regardless of whether your organisation is

  • actively developing its applications in CA Gen
  • continuing to use CA Gen in ‘maintenance mode’
  • actively investigating a move away from CA Gen
  • even mid-way through a migration

… Jumar FLEX can deliver cost, time and risk-saving benefits.  The approach is designed such that, whatever your strategy for the technology, Jumar provides automated solutions for all scenarios. 

What does it achieve?

The biggest barriers to the replacement or modernisation of CA Gen applications are typically their size, complexity and tight-coupled, highly interdependent construction.
Many CA Gen users have such systems which comprise:

  • A single, large database serving multiple applications
  • Many shared entity types
  • Applications scoped by ‘menu-based’ functionality rather than data usage
  • Tightly-coupled functionality that is difficult to maintain
  • Heavily integrated functionality that is seemingly very difficult to define and replace (for example with a software package)

 

FI1

Such tightly coupled systems often result in various problems;

  • Application interdependencies are poorly understood
  • Any form of significant change is perceived as difficult, time consuming and risky – particularly any attempt to untangle the system and break it up into manageable units for replacement or modernisation
  • ‘Big bang approaches’ tend to be viewed as the only viable option
  • It is perceived that projects will be huge with long timescales and high risk
  • The system lacks flexibility – meaning only one implementation option must be applied to all business areas

However, organisations can significantly mitigate these issues by adopting the Jumar FLEX approach, which assesses the entire CA Gen implementation, identifies functional areas and boundaries, and then uses automation tooling to ‘break down’ the system into individual functional areas. 

Different strategies can then be adopted for each isolated area.

Unlike a full, “heavyweight” componentisation exercise, functional isolation is a proportionate and targeted exercise which can be implemented in part or in full across the estate. One organisation saved over $4M USD by using functional isolation to break up their estate (when compared to their previously identified plan of carrying out the exercise manually) – dramatically improving the maintainability of the system, allowing for parallel development (and so accelerating time to market) and reducing the total cost of ownership.

A hybrid strategy

Jumar FLEX is a hybrid strategy which recognises the need for different modernisation/replacement strategies specific for each functional area.  The immediately removes the constraint to undertake a ‘big bang’ implementation and allows for a phased implementation driven by business need.  In the example below, the green functional area could be identified for isolation first:


FI2


This allows the generation of an individual roadmap for the newly isolated business area – as it is highly likely that each area will require a different approach. Rarely is there a “one size fits all” in terms of end state. 
Such approaches may include:

  • Implement a COTS package
  • Automatically migrate to native code
  • Modernise the User Interface
  • Re-write manually
  • Implement SOA principles
  • Re-platform
  • Introduce Web services
  • Move to the cloud
  • Outsource the Support and Maintenance of the component
  • Leave it as it is, while transforming other isolated functional areas

Once the components begin to be isolated, the organisation will already have increased the number and feasibility of its modernisation options.  At the same time, application maintainability and business agility will be improved.  This process can then be repeated for each in-scope functional area – with different strategies for each.

FI3


By adopting the pragmatic, hybrid Jumar FLEX approach, the project:

  • delivers tangible results to the business early
  • is driven by business priorities
  • starts new implementation as soon as initial separation is achieved
  • can benefit from other functional areas being separated in turn or in parallel
  • may have some functional areas which might never be separated if there is no business case or requirement to do so

 For more information Jumar FLEX, please contact us for an informal discussion to explore the options open to you